-
Notifications
You must be signed in to change notification settings - Fork 33
Drop support of symfony 4 #301
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 of symfony 4 #301
Conversation
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.
Hello @Chris53897
Don't forget to update the bors file accordingly, if you add or remove jobs in the CI 😊
https://github.com/meilisearch/meilisearch-symfony/blob/main/bors.toml
Thanks for the reminder. I forgot it again :( |
Testruns for PHP 8.3 are blocked by shivammathur/setup-php#789 |
This is missing Symfony 6.4 |
I have added tests for Symfony 6.4 now. |
Instead of Empty-Commit just do |
Ok, will do. I saved it to my snippets. |
@norkunas Any tip how to solve the problems with the run for symfony 5.4 and 6.0? The problem, ist that we get a deprecation wanring, if we do not set the entry. a) Make different config-files for 5.4, 6.0, 6.1 ? At best include a basic config-file and just change one line. |
I'd conditionally require |
As we all want to release Symfony 7 support faster, then we should currently avoid dropping 4.4 support as two blocker issues popped up that needs to be fixed before |
@norkunas I added a new PR. But i am on holidays starting from friday (until 19.12). And not much time tomorrow. |
bors merge |
Blocked by
please see
#265 (comment)
and #300