Skip to content

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

Merged
merged 1 commit into from
Dec 20, 2023
Merged

Drop support of symfony 4 #301

merged 1 commit into from
Dec 20, 2023

Conversation

Chris53897
Copy link
Contributor

@Chris53897 Chris53897 commented Nov 3, 2023

Blocked by

please see
#265 (comment)
and #300

Copy link
Member

@curquiza curquiza left a 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

@Chris53897
Copy link
Contributor Author

Thanks for the reminder. I forgot it again :(
I have added it now.

@Chris53897
Copy link
Contributor Author

Testruns for PHP 8.3 are blocked by shivammathur/setup-php#789

@norkunas
Copy link
Collaborator

This is missing Symfony 6.4

@Chris53897
Copy link
Contributor Author

I have added tests for Symfony 6.4 now.
Now waiting for the blocking PR. (see on top of page)

@norkunas
Copy link
Collaborator

Instead of Empty-Commit just do git commit --amend --no-edit 🙂

@Chris53897
Copy link
Contributor Author

Ok, will do. I saved it to my snippets.

@Chris53897
Copy link
Contributor Author

@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.
But on the other side the test-config is for symfony 5 and 6.
https://github.com/meilisearch/meilisearch-symfony/pull/301/files#diff-a875c960177021258e97cd9e7b3989ff28a6c851d04a2ebb15ccc41c14889a55R17

a) Make different config-files for 5.4, 6.0, 6.1 ? At best include a basic config-file and just change one line.
b) Add it dynamic in php conditionally fo config
c) Ignore the deprecation
d) ...

@norkunas
Copy link
Collaborator

I'd conditionally require var-exporter when it is needed, like when we conditionally remove doctrine/annotations

@norkunas
Copy link
Collaborator

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

@Chris53897
Copy link
Contributor Author

@norkunas I added a new PR. But i am on holidays starting from friday (until 19.12). And not much time tomorrow.
Feel free to finish it.

@norkunas norkunas changed the title feat: drop support for symfony 4, add support of symfony 7 (WIP) Drop support of symfony 4 Dec 20, 2023
@norkunas
Copy link
Collaborator

bors merge

@norkunas norkunas merged commit b202995 into meilisearch:main Dec 20, 2023
@curquiza curquiza added the breaking-change The related changes are breaking for the users label Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change The related changes are breaking for the users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants