Skip to content
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

Merge 3.4.x up into 4.0.x #589

Merged
merged 6 commits into from
Jan 27, 2025
Merged

Merge 3.4.x up into 4.0.x #589

merged 6 commits into from
Jan 27, 2025

Conversation

greg0ire
Copy link
Member

No description provided.

- We can stop maintenance on 2.x, nobody seems to be using it now.
- 3.3.x is no longer maintained
- 3.4.x is the new current branch
- 4.0.x is the new latest branch, and is upcoming

No 3.5.x, because I think we could release 4.0.0 quite soon.
There is only one call to it.
It is more careful, since there seems to be a lot of situations where we
do not want to apply the filter.
Let us take the opposite approach and:
- Have the filter disabled by default, instead of enabled by default.
- Enable it for precise commands where we know we need it.
@greg0ire greg0ire merged commit 185159e into doctrine:4.0.x Jan 27, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant