-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Symfony 6 Support #1675
Comments
Can you add |
I think there was an issue about sf 5. |
@franmomu do you have time for help with DoctrineMongoDBAdminBundle? |
SonataSeoBundle is ready too, @Kocal if you want to help with it |
Gonna give it a try this evening! |
We are stuck because of the panther 🐈⬛ ... Persistence bundles require it: sonata-project/SonataDoctrineORMAdminBundle#1562 Options:
What should we do? @sonata-project/contributors |
The final step is cleanup composer.json and make sure all builds pass without requiring unstable dependencies. I have started with exporter and form-extensions, any help welcome @sonata-project/contributors |
Symfony Security Acl is blocking the update to Symfony 6 , we might take a look and help them with that, otherwise our users cant update. symfony/security-acl#99 |
Will be solved by symfony/security-acl#100 :) |
We are still blocked by the symfony acl :( |
We are unblocked, tomorrow will try to check and fix SonataAdminBundle build. We need to check all builds and remove the usage of unstable dependencies. |
So all bundles are cleaned up, we just need a dev-kit PR. |
Active Bundles
Bundles that are used as dependencies
Bundles that do not support SF 5
Bundles with only Symfony dependencies on require-dev section
Final cleanup
The final step is cleanup composer.json and make sure all builds pass without requiring unstable dependencies
The text was updated successfully, but these errors were encountered: