-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Doctrine][DoctrineBridge] Compatibility with ORM 3 and DBAL 4 #51997
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
Conversation
e6602a9
to
a18116a
Compare
a18116a
to
e1808da
Compare
Thanks for the PR, I used it while merging 5.4 into 6.3 see b691c31 |
Please note that I pushed 913a317 to fix such messages. Please double-check I did no mistakes. |
That change does not look correct. My PR introduces dedicates |
I merged everything up to 7.0 but I'm pretty sure I made mistakes - at least this one. I need your help to double check + fix 🙏 |
Let's cross fingers for #52022. 🤞🏻 |
…n tests with ORM 3 and DBAL 4 (derrabus) This PR was merged into the 6.3 branch. Discussion ---------- [Doctrine][DoctrineBridge][HttpFoundation][VarDumper] Run tests with ORM 3 and DBAL 4 | Q | A | ------------- | --- | Branch? | 6.3 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | Follow-up to #51997 | License | MIT Everything that got lost in the merge-up + a fix for the VarDumper testsuite. 😇 Commits ------- 81c40be Run tests with ORM 3 and DBAL 4
This PR was merged into the 5.4 branch. Discussion ---------- [DoctrineBridge] Fix DBAL 4 compatibility | Q | A | ------------- | --- | Branch? | 5.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Tickets | N/A | License | MIT This PR backports DBAL 4 compatibility changes from #51997 that were not in #51947. Sorry for messing this up. Commits ------- 50c0fbc Fix DBAL 4 compatibility
This PR makes the 6.3 branch compatible with Doctrine DBAL 4 and ORM 3. It contains all changes from #51947 which does the same on the 5.4 branch.
Please note that I intentionally did not allow DBAL 4 in the dependencies of the monorepo's composer.json. If I did that, we would lose coverage for DBAL 3 completely which would be very unfortunate.
Right now, we should get the following test matrix: