From 54e16ff822bf923e3f3a3f861adf2ced0b378acf Mon Sep 17 00:00:00 2001 From: DataBoost Devs Date: Tue, 12 May 2026 19:47:20 -0700 Subject: [PATCH] composer: switch to upstream adodb/adodb-php from stale reportico/adodb-php fork MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The current `reportico/adodb-php: ^8.1` dependency is a long-stale snapshot of an older ADOdb release. It has not received any of the upstream security or PHP 8.x compatibility fixes that have shipped since. Switching to the actively maintained upstream package brings in: - Multiple security advisories fixed in 5.22.10 / 5.22.11 (PKSA-rfc1-gnmf-7kkz, PKSA-jm5q-b4t5-4pm4, etc.); previous ADOdb versions are flagged by composer audit. - PHP 8.5 source compatibility — the `(integer)` cast deprecations that originally required custom patches against the reportico fork were already addressed upstream (see ADOdb commits replacing `(integer)` with `(int)` in 5.22.10 / 5.22.11). - PDO/oci8/postgres driver bug fixes accumulated since the fork. No source changes are required in Reportico itself: the existing code uses the standard `ADODB_*` global-namespace classes/constants and the `ADODB_DIR` constant, all of which are identical between the two packages. Tested on PHP 8.5.1 (MacPorts) with adodb/adodb-php v5.22.11 against a PostgreSQL backend: report run, criteria selection, HTML output and TCPDF PDF generation all behave identically to the previous build. Co-authored-by: Cursor --- composer.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/composer.json b/composer.json index 1d74b1d..7e8e636 100644 --- a/composer.json +++ b/composer.json @@ -14,7 +14,7 @@ ], "require": { "php": ">=8.0", - "reportico/adodb-php": "^8.1", + "adodb/adodb-php": "^5.22.11", "twig/twig": "^3.0", "tecnickcom/tcpdf": "^6.2", "szymach/c-pchart": "^3.0",