Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Require doctrine/persistence ^1.3 #34955

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 12, 2019

Conversation

nicolas-grekas
Copy link
Member

Q A
Branch? 4.3
Bug fix? yes
New feature? no
Deprecations? no
Tickets -
License MIT
Doc PR -

This is the only way to remove direct deprecations triggered by doctrine/persistence ^1.3.
Requires v1.3.0 to be tagged before the next bug fix release.
/cc @alcaeus

The only deprecations that remain are triggered by the ORM now.

@@ -19,7 +19,7 @@
"php": "^7.1.3",
"ext-xml": "*",
"doctrine/event-manager": "~1.0",
"doctrine/persistence": "~1.0",
"doctrine/persistence": "^1.3",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be ^1.3 || ^2.0 - we're looking for absolute parity between the two versions.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that would prevent testing with 1.3 for now
OK in a later PR

@nicolas-grekas nicolas-grekas force-pushed the doctrine-persistence-13 branch from 7af8eda to f2edc7b Compare December 12, 2019 14:43
Copy link
Contributor

@alcaeus alcaeus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - we can add 2.0 later. We'll release 1.3 in time for an early Christmas :)

@nicolas-grekas nicolas-grekas force-pushed the doctrine-persistence-13 branch from f2edc7b to ce5dcb9 Compare December 12, 2019 14:53
nicolas-grekas added a commit that referenced this pull request Dec 12, 2019
This PR was merged into the 4.3 branch.

Discussion
----------

Require doctrine/persistence ^1.3

| Q             | A
| ------------- | ---
| Branch?       | 4.3
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Tickets       | -
| License       | MIT
| Doc PR        | -

This is the only way to remove direct deprecations triggered by doctrine/persistence ^1.3.
Requires v1.3.0 to be tagged before the next bug fix release.
/cc @alcaeus

The only deprecations that remain are triggered by the ORM now.

Commits
-------

ce5dcb9 Require doctrine/persistence ^1.3
@nicolas-grekas nicolas-grekas merged commit ce5dcb9 into symfony:4.3 Dec 12, 2019
@nicolas-grekas nicolas-grekas deleted the doctrine-persistence-13 branch December 12, 2019 15:11
@ro0NL
Copy link
Contributor

ro0NL commented Dec 13, 2019

@nicolas-grekas maybe this breaks stuff :D

 - Updating doctrine/persistence (1.2.0 => 1.3.2): Loading from cache

Argument 1 passed to Doctrine\ORM\Configuration::setMetadataDriverImpl() must be an instance of Doctrine\Common\Persistence\Mapping\Driver\MappingDriver, instance of Doctrine\Persistence\Mapping\Driver\MappingDriverChain given 

@ro0NL
Copy link
Contributor

ro0NL commented Dec 13, 2019

sorry, this is unreleased. So a BC break on Doctrine's side.

@nicolas-grekas
Copy link
Member Author

@ro0NL this PR did not introduce the issue, but here is the fix anyway: doctrine/persistence#82

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants