Support Doctrine ORM 3.0 #180
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
|
@chalasr Allow me to tag you here. Could you enable the workflows to run? |
|
The package Fixed the errors thrown by psalm and php-cs-fixer. |
|
When to expect the new release? I've saw that all tests are passed. |
chalasr
force-pushed
the
doctrine-orm-v3
branch
from
f7e7244 to
0cd73a8
Compare
|
Thank you @wmouwen. |
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.
Doctrine ORM v3.0.0 has been released.
https://github.com/doctrine/orm/releases/tag/3.0.0
Upgrade the minimal version of the ORM to v2.14, allow v3.0 as well. This matches the version requirement as used by doctrine/doctrine-fixtures-bundle.
Update the GitHub workflows to test against v2.14, v2.18 and v3.0.