fix: pin composer lock to php 8.2 compatible symfony clock#115
Merged
Conversation
Contributor
Author
Member
|
ups sorry |
marandaneto
approved these changes
Apr 1, 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.
Summary
Fix CI after composer.lock was checked into master with
symfony/clock v8.0.0, which requires PHP 8.4 and breakscomposer installon the 8.2/8.3 jobs.This keeps
composer.jsonunchanged, so downstream consumers on PHP 8.4+ can still resolve Clock 8 if they want to. Only the checked-in lockfile changes for this repo.Changes
symfony/clockfromv8.0.0tov7.4.8symfony/polyfill-php83as required by that resolutioncomposer.jsonconstraints aloneVerification
composer install --prefer-dist --no-progress