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
Drop support for PHP < 7.1 and Symfony < 3.4 #892
Conversation
3f3cd95
to
166b85e
Compare
@doctrine/team-symfony-integration Anyone know where the deprecation in https://travis-ci.org/doctrine/DoctrineBundle/jobs/466345293 is coming from? It only happens in the Symfony 3.4 build where we lock all our explicit dependencies to Symfony 3.4 (but allow newer versions of other dependencies). I can't quite figure it out what's triggering it... |
@alcaeus you could try getting a stack trace by using |
Thanks for the hint! I traced it to the service container but I'm not sure what the root cause is:
|
Thanks @ostrolucky for finding the cause of the deprecation. For now, I changed the deprecation helper config to report all deprecations without failing the build - this solves the issue regardless of whether it's fixed upstream. |
ff2f830
to
09f1955
Compare
How about setting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please remove argument for HttpKernelExtension in setUp method of ProfilerTest? It seems it's no longer needed. I think it was for older versions too
Will do 👍
I'd rather not have the build fail on deprecations in older builds to prevent regressions like the one before (where a newer version of a peer dependency triggers a deprecation). The tests against the latest version should fail when deprecations arise, so we should spot them soon enough 👍 |
95d104b
to
a80af45
Compare
@ostrolucky apparently that argument is still required, the build against the lowest set of dependencies fails without it. |
Yeah, it installed TwigBridge 2.8 heh |
Not worth doing job of cs fixers manually |
Is there a fixer for this? |
@greg0ire I'll work on the todo, completely forgot about that, sorry. As for CS, I'd like to avoid style changes in this PR. doctrine/coding-standard also doesn't have any line-length rules, so I'd like to direct discussion about that to https://github.com/doctrine/coding-standard so we can come up with consistent rules on that. Thanks! |
a80af45
to
33393db
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Waiting for the todo then
This configures the deprecation helper to not fail builds on all Symfony versions except the latest stable one. We always expect no deprecations when running against the latest versions of Symfony.
33393db
to
7f7d10d
Compare
7f7d10d
to
2279d8a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should look into the CS afterwards
I'm AFK for a week so cannot create the cs discussion, especially since it seems to mean creating a PR, but feel free to |
Fixes an issue reported in doctrine#976, previously introduced in doctrine#892.
As per discussion in Slack and #885, this PR removes support for PHP < 7.1 (as they are no longer supported) as well as Symfony < 3.4 (since they are in security support only). This will target the 1.11 minor release.
The remaining build failure is due to a deprecation which isn't ignored in the Symfony 3.4 build. I have no idea which dependency combination causes that, so if anyone would have a few pointers for me, they'd be very much appreciated.