Allow symfony/yaml ^5.4 and ^6.0#2
Merged
Merged
Conversation
The only usage of Yaml in this fork is Symfony\Component\Yaml\Yaml::parse() (src/DataSet/SymfonyYamlParser.php), an API stable across all these majors. Needed to unblock newer packages that require symfony/yaml >=5.4.
mmenozzi
force-pushed
the
widen-symfony-yaml-constraint
branch
from
July 21, 2026 10:38
7c3798d to
3b006ad
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
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.
Context
A downstream project needs to update
openmage/magento-ltsto a version that requiressymfony/validator ^6.4, which in turn requiressymfony/yaml >=5.4. That's incompatible with this fork's current constraint (^3.0 || ^4.0), blockingcomposer update.Change
Widen the constraint to
^3.0 || ^4.0 || ^5.4 || ^6.0.The only usage of Yaml in this fork is
Symfony\Component\Yaml\Yaml::parse()(src/DataSet/SymfonyYamlParser.php), a stable API across all these majors.The branch history shows two earlier attempts to raise this constraint (to
^5.0and^6.0), later reverted back to^3.0 || ^4.0(commits 1fa1a5e, 5d48fcb, November 2022) — likely due to a conflict with other dependencies at the time. That conflict does not appear to apply anymore in current downstream usage.