-
-
Notifications
You must be signed in to change notification settings - Fork 388
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
Remove unmaintained symfony libraries #1368
Conversation
This should be submitted in the 3.7.x branch to remove support for Symfony 4.4 in the next minor version rather than in the next patch version IMO. |
Good Idea. Maybe drop support for Versions 5.* also? Because if you update symfony to latest (6.3) Version, you will get some deprecation warnings. |
I don't understand your proposal. Why wanting to drop support for 5.x (where 5.4 is still maintained for 1 year plus an extra year of security fixes) ? you're saying that you get some deprecation warnings when updating to 6.3, but I don't understand how this relates to the support of 5.x |
How to get rid of the deprecation warnings then? |
Did you check if this allows us to drop any compat code? |
…so it works with old and new symfony/console Versions
…so it works with old and new symfony/console Versions
Ok I just updated the PR to use setName Function instead of $defaultName. This works for old and new symfony/console Versions. Maybe this is better? Then 5.4 is still supported. |
the AsCommand attribute is supported starting in Symfony 5.3. So you don't need to drop support for 5.4. |
Yes with my latest changes 5.4 does not need to be dropped and there is no deprecation warning anymore. |
Dropping Symfony 4 was done in #1352 already. The changes you've made to the commands should not be necessary since the |
Closing in favor of #1370. |
Summary
Drop unmaintained symfony 4.4 libraries