-
-
Notifications
You must be signed in to change notification settings - Fork 84
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
Dropping support for symfony < 3.4 #272
Dropping support for symfony < 3.4 #272
Conversation
67663bb
to
39dc43d
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.
IMO, from a strict perspective, removing classes or public services are not BC changes.
I'll revisit when I finish with the other ones and mark them as deprecated. They are not supposed to be used, but you're right. |
39dc43d
to
09253b6
Compare
09253b6
to
278cee7
Compare
I just fixed the cs issue |
The remaining failure is due to user 3 require sf 2.8. We should remove that line from the build matrix in dev-kit |
Blocked by sonata-project/dev-kit#516 |
278cee7
to
ce130fe
Compare
ce130fe
to
2fd0183
Compare
This is not blocking the PR anymore.
|
9da9b2b
to
cefb953
Compare
cefb953
to
5a3ad84
Compare
Apparently is because of symfony/symfony#33148, with the |
acd91c8
to
e66b234
Compare
e66b234
to
97f0866
Compare
Thanks @franmomu ! |
Subject
This is the same thing as sonata-project/SonataAdminBundle#5733, dropping support of Symfony < 3.4 and >= 4, < 4.2
I am targeting this branch, because these changes respect BC.
Changelog