-
Notifications
You must be signed in to change notification settings - Fork 170
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
Add support for symfony 6 #566
Add support for symfony 6 #566
Conversation
279811c
to
e8e33f9
Compare
e8e33f9
to
5cf35ac
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.
Code LGTM 👍
Can you add a changelog entry?
Also, I would like to add a CI job to test this, but I think we will need to require the newer Symfony version in some special way?
You can test again dev dependencies using before running
|
Co-authored-by: Stefano Arlandini <[email protected]>
@alexander-schranz do you plan to keep working on this? Otherwise, I would be happy to take over your work and finish it |
@ste93cry sorry for the late response. I pushed an update to use a different UserStub, still feel free to take it over as a maintainer you should have permissions to directly push here into my branch. |
d96c581
to
d1c9aea
Compare
d1c9aea
to
37c2b82
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.
Just a small nitpick, the rest LGTM 👍
@ste93cry do we want to wait for the official tag to merge?
Co-authored-by: Alessandro Lai <[email protected]>
I would prefer so, so that we can test the CI on the stable version before merging. It should be a matter of a couple of days, so it doesn't really change anything |
Hi, Symfony 6.0 has been released :) |
Yup, I'm aware of it. Unfortunately now that we can test the stable version more deprecations than expected popped out, plus some of our dependencies are still not compatible with the |
Main blocker seems PHP-CS-Fixer/PHP-CS-Fixer#6095; but since it's the CS fixer, we could manually remove it in the main jobs to avoid the failures. |
Actually we have also some issues with PHPStan, Psalm, and PHP-CS-Fixer is hiding some deprecations/incompatibilities with Symfony 6. I don't want to wait forever, just to be clear, but I don't see any need to rush a release. Upgrading immediatly to something entirely new is discouraged anyway in most environments, so waiting a few days/a week is not that bad after all |
I see that quality checks currently running under php 8.1? Symfony 6 requires 8.0.2. So those deprecations should be fixed in php 8.1 but from my point of view this should be done in a separate pull request right? |
Just a quick update: PHP-CS-Fixer merged the support for PHP |
d6a6392
to
0e589d6
Compare
Not sure how the test matrix need to be changed locally tests running when doing:
Fixes #564
Not sure how to fix the psalm error. Feel free to push into my branch.