Repository navigation
feat(php): require a minimal patch version of PHP - #460
Merged
Merged
Conversation
Bumping it after a security release invalidates the build cache of the PHP packages, which would keep the vulnerable version otherwise, and the build fails until Sury publishes the fixed version.
Member
Author
lyrixx
force-pushed
the
php-min-versions
branch
from
October 21, 2026 08:39
75315de to
603dd33
Compare
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.

The PHP packages layer is cached (locally and in the registry), so after a PHP security release a rebuild keeps the vulnerable version. Bumping
PHP_MIN_VERSIONSinvalidates this cache, and the build fails until Sury publishes the fixed version.The current versions are the ones Sury ships today: nothing changes until the next bump (the security release of 21 October, 14:00 UTC).