fix(composer): allow brick/math 0.20 - #718
Merged
Merged
Conversation
brick/math ships a new minor release every few weeks, and every package of the stack has to be bumped in lockstep because the one lagging behind caps brick/math for the whole dependency tree. Declaring the next minor ahead of time removes one round of that churn. The range only gains 0.20.x. Every version accepted before is still accepted, and 0.21 and above stay excluded so a breaking release cannot slip in unnoticed.
Spomky
force-pushed
the
fix/brick-math-open-constraint
branch
from
August 30, 2026 13:26
41d4719 to
ae457df
Compare
Spomky
changed the title
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
1 participant
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.
Problem
brick/mathpublished six minor releases in seven months (0.15, 0.16, 0.17, 0.18, 0.19 and 0.20). Each one means adding a new^0.xalternative to the constraint, cutting a release, and repeating the operation in every package of the stack (spomky-labs/cbor-php, spomky-labs/pki-framework, web-auth/cose-lib, web-token/jwt-library). Whichever package lags behind capsbrick/mathfor the whole dependency tree of the applications that install them.Change
^0.20is added to the chain in bothcomposer.jsonandsrc/Library/composer.json, which must stay in sync.The explicit chain is kept on purpose instead of an open range such as
>=0.12 <1.0.brick/mathis still a 0.x package, where a minor release is allowed to break the API, so every version has to be opted into deliberately.Backward compatibility
Checked with
composer/semver:Intervals::isSubsetOf(old, new)returnstrue, so no accepted version is lostWhich version is actually resolved
brick/math0.20.0 was released on 2026-08-28, so this range is not speculative. The tree here still resolves 0.19.1 for now, because the releasedspomky-labs/pki-frameworkstill capsbrick/mathat^0.19. It will pick 0.20.0 up once that one is released, which is precisely the lockstep effect this change is meant to shorten.