From fa8496b31c32a722ba7631430ec808f7aea4754a Mon Sep 17 00:00:00 2001 From: loks0n <22452787+loks0n@users.noreply.github.com> Date: Fri, 31 Jul 2026 10:06:21 +0100 Subject: [PATCH 1/2] chore: allow client 0.3 in fastly, messaging and storage MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit pools 2.0.0 changed how a pool is constructed, and client's Pool takes one, so client shipped that bump as 0.3.0. Every client consumer in the monorepo pinned inside 0.2, which left messaging unbuildable from the registry: it requires pools ^2.0 and client ^0.2, and no released 0.2.x allows pools 2. messaging moves to ^0.3 outright, since its pools ^2.0 requirement rules out the 0.2 line anyway. fastly and storage widen rather than move — they never touch pools, so both client majors work for them and pinning would force their consumers to upgrade in lockstep. Verified registry-resolved against the published client/0.3.0 and pools/2.0.0: messaging 19 tests, storage 27, fastly 4, all green. --- packages/fastly/composer.json | 2 +- packages/messaging/composer.json | 2 +- packages/storage/composer.json | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/packages/fastly/composer.json b/packages/fastly/composer.json index 9ca3c8c78..11efd3874 100644 --- a/packages/fastly/composer.json +++ b/packages/fastly/composer.json @@ -27,7 +27,7 @@ "require": { "php": ">=8.4", "psr/http-client": "^1.0", - "utopia-php/client": "^0.1.1 || ^0.2", + "utopia-php/client": "^0.1.1 || ^0.2 || ^0.3", "utopia-php/psr7": "^0.2" } } diff --git a/packages/messaging/composer.json b/packages/messaging/composer.json index c25767159..e882a5ea0 100644 --- a/packages/messaging/composer.json +++ b/packages/messaging/composer.json @@ -35,7 +35,7 @@ "phpmailer/phpmailer": "^6.9", "psr/http-client": "^1.0", "psr/http-message": "^1.1 || ^2.0", - "utopia-php/client": "^0.2", + "utopia-php/client": "^0.3", "utopia-php/pools": "^2.0", "utopia-php/telemetry": "^0.4" }, diff --git a/packages/storage/composer.json b/packages/storage/composer.json index cf019f1b4..bb7a57342 100644 --- a/packages/storage/composer.json +++ b/packages/storage/composer.json @@ -35,7 +35,7 @@ "utopia-php/validators": "0.3.*", "psr/http-client": "^1.0", "psr/http-message": "^1.1 || ^2.0", - "utopia-php/client": "0.2.*", + "utopia-php/client": "0.2.* || 0.3.*", "utopia-php/psr7": "0.2.*" }, "config": { From 9df79284bc821f0fa99360fa65e72ca03ba2ed4c Mon Sep 17 00:00:00 2001 From: loks0n <22452787+loks0n@users.noreply.github.com> Date: Fri, 31 Jul 2026 10:10:27 +0100 Subject: [PATCH 2/2] chore: allow queue 0.23 and 0.24 in platform MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit platform still required queue ^0.22, so it could not see queue/0.23.0 — the fix that keeps a consumer alive when the broker fails. That fix matters here specifically because pools 1.x reconnect delays were the accidental backoff standing in for the missing guard, so a platform pinned to 0.22 turns a broker outage into a crash loop the moment it picks up pools 2. queue/0.24.0 carries the pools ^2.0 bump. Both majors are allowed rather than just the newest: platform constructs Swoole($consumer, $workersNum, $queueName) and Server($adapter), neither of which changed across 0.23 or 0.24, and platform never touches the pooled broker, so nothing forces its consumers to move in lockstep. Verified registry-resolved against queue/0.24.0 (pools 2.0.0 transitively): 9 tests green, check and validate clean. --- packages/platform/composer.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/platform/composer.json b/packages/platform/composer.json index 7775e6a7c..8d3016e8c 100644 --- a/packages/platform/composer.json +++ b/packages/platform/composer.json @@ -28,7 +28,7 @@ "ext-redis": "*", "utopia-php/cli": "^0.24", "utopia-php/http": "^2.0@RC", - "utopia-php/queue": "^0.22", + "utopia-php/queue": "^0.23 || ^0.24", "utopia-php/servers": "^0.4" }, "scripts": {