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

Add an UPGRADE notice about the potential changes in commit order #10866

Merged
merged 1 commit into from
Aug 2, 2023

Conversation

mpdude
Copy link
Contributor

@mpdude mpdude commented Aug 2, 2023

No description provided.

@mpdude mpdude force-pushed the upgrade-notice-commit-order branch from aaa0e06 to c64fd0b Compare August 2, 2023 11:41
@derrabus derrabus added this to the 2.16.1 milestone Aug 2, 2023
@derrabus derrabus merged commit eeefc6b into doctrine:2.16.x Aug 2, 2023
@mpdude mpdude deleted the upgrade-notice-commit-order branch August 2, 2023 11:55
derrabus added a commit that referenced this pull request Aug 7, 2023
* 2.16.x:
  Turn identity map collisions from exception to deprecation notice (#10878)
  Add possibility to set reportFieldsWhereDeclared to true in ORMSetup (#10865)
  Fix UnitOfWork->originalEntityData is missing not-modified collections after computeChangeSet  (#9301)
  Add an UPGRADE notice about the potential changes in commit order (#10866)
  Update branch metadata (#10862)
nicolas-grekas pushed a commit to nicolas-grekas/doctrine-orm that referenced this pull request Aug 7, 2023
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.

2 participants