Add conflict with doctrine/orm <2.14 #2697
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #2697 +/- ##
=======================================
Coverage 79.60% 79.60%
=======================================
Files 161 161
Lines 8415 8415
=======================================
Hits 6699 6699
Misses 1716 1716 ☔ View full report in Codecov by Sentry. 📢 Have feedback on the report? Share it here. |
stof
approved these changes
Sep 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up #2669
Since we have
^2.14inrequire-devDoctrineExtensions/composer.json
Line 59 in 512695c
it makes sense to add this conflict because we are not testing
doctrine/orm< 2.14 anymore