-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Translation] fix support for nikic/php-parser 5.0 #53453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
edited by nicolas-grekas
Q | A |
---|---|
Branch? | 6.3 |
Bug fix? | yes |
New feature? | no |
Deprecations? | no |
Issues | |
License | MIT |
What about merging this on 5.4? This would reduce the pressure on deps constraints. |
Not sure, this is not a bugfix to me. |
We also merge deps-related changed to 5.4: support for latest Doctrine, latest PHP, etc. This is similar to me. This makes Symfony a low contributor to deps-hell (aka makes upgrading easier) |
If it's compatible with 5.4, I don't see any reason to not allowing this new version. |
fair enough, rebased on |
src/Symfony/Component/Translation/Extractor/PhpAstExtractor.php
Outdated
Show resolved
Hide resolved
src/Symfony/Component/Translation/Extractor/PhpAstExtractor.php
Outdated
Show resolved
Hide resolved
src/Symfony/Component/Translation/Extractor/PhpAstExtractor.php
Outdated
Show resolved
Hide resolved
Note that currently, we explicitly say that this is not allowed as a bug fix in the maintenance docs:
|
@wouterj we have some contradiction on the topic, because we also have this "seamless deps" rule that makes us fix compat with Doctrine / PHP / Windows / infra-level stuff on lower branches, the reason being that wider deps ranges makes it easier to upgrade for end users. |
Yes, "Newer versions of PHP" and "Newer versions of popular OSes" are mentioned in the "allowed on a case by case basis" section :) Btw, not saying I'm against this change, especially as we don't set version ranges explicitly for this optional dep. But I think we should then update our policy on this (and find the reason why we set the current policy like this, is there something non-obvious that bit us in the past and we shouldn't forget now?) |
48ccd5e
to
3025d5a
Compare
tests pass, ready to be reviewed |
Thank you @xabbuh. |
This PR was merged into the 6.3 branch. Discussion ---------- [Translation] simplify the parser factory creation | Q | A | ------------- | --- | Branch? | 6.3 | Bug fix? | no | New feature? | no | Deprecations? | no | Issues | continuation of #53453 | License | MIT Commits ------- 509ca9b simplify the parser factory creation