Unpin utopia-php/http and move to 2.0.0-rc32 - #254
Merged
Merged
Conversation
The exact rc pin was the ceiling for every consumer of the executor. A caret range lets downstream resolve newer release candidates without a coordinated bump here, and rc32 pulls validators 1.0 which the rest of the utopia stack has already moved to. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
|
loks0n
approved these changes
Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Moves
utopia-php/httpfrom an exact2.0.0-rc23@RCpin to^2.0@RC, currently resolving to2.0.0-rc32.Why
The exact pin is the ceiling for every consumer of the executor. A caret range lets downstream resolve newer release candidates without a coordinated bump here.
What moves
httprc23 → rc32, and with itvalidators0.5.0 → 1.0.1,servers0.4.8 → 0.4.11,storage4.0.4 → 4.1.0,pools2.0.2 → 2.1.2,span4.1.0 → 4.2.0,client0.3.0 → 0.4.4, plus patch bumps ofsystem,di,telemetry,compression.servers0.4.11 andstorage4.1.0 are required because they are the first releases that acceptvalidators1.0.rc23 → rc32 changes
Request::setTrustedIpHeaders()removed. Replaced by aTrustedHeadersvalue object passed to the server adapter constructor, so trusted forwarded headers are fixed at construction. The executor never calledsetTrustedIpHeaders, so no migration is needed here.getProtocol()reads only trusted proto headers. The default trustsx-forwarded-proto, so behaviour is unchanged for the executor.Rangeparsing treatsstart === endas a valid single-byte range per RFC 9110.Modepresets setmax_requestto 10,000 to recycle workers. The executor uses theSwooleCoroutineadapter, which does not useMode, so this does not apply.validators ^1.0,system ^0.10 || ^0.11.validators0.5 → 1.0 changes onlyAssoc::getType()andisArray()(now reported as object). That affects spec generation, not validation, so the executor'sAssocparams validate exactly as before.Testing
composer analyze,format:check,refactor:checkandtest:unit(35/35) pass.E2E run locally against the rc32 image: 30/31 pass. The one failure was
testCustomRuntimesfor PHP, where the test function's owncomposer installhit a GitHub 504 downloading guzzle. Unrelated to this change.🤖 Generated with Claude Code