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

Move doctrine/persistence to dev dependencies #269

Merged

Conversation

MidnightDesign
Copy link
Contributor

The dependency is not used in production code, only in DoctrineMongoODMModuleTest\Assets\CustomRepositoryFactory.

The dependency is not used in production code, only in DoctrineMongoODMModuleTest\Assets\CustomRepositoryFactory.
Copy link
Member

@driehle driehle left a comment

Choose a reason for hiding this comment

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

By moving persistence to require-dev, we will automatically allow persistence v3 for this module, as upstream DoctrineModule allows either v2 or v3. Therefore, could you please change it to ^2.4.0 || ^3.0.0? We will have to ensure that our unit tests run v3, otherwise this change could be harmful for users.

composer.json Outdated Show resolved Hide resolved
Co-authored-by: Dennis Riehle <webmaster@riehle-web.com>
@driehle driehle added this to the 4.2.0 milestone Nov 7, 2022
@driehle driehle added the Enhancement New feature or request label Nov 7, 2022
The parameter cannot be typed here, to ensure compatibility of the test with both persistence v2 and v3. The typed parameters were only introduced with persistence v3.
@driehle driehle self-assigned this Nov 7, 2022
@driehle driehle merged commit 124c9e3 into doctrine:4.2.x Nov 7, 2022
@MidnightDesign MidnightDesign deleted the move-doctrine-persistence-to-dev-deps branch November 7, 2022 09:45
@driehle
Copy link
Member

driehle commented Nov 7, 2022

I have fixed the issue with PhpStan, which was still present in this PR. Since this PR effectively adds a new feature, i.e. the support for persistence v3, we have to release it as a new minor release, i.e. 4.2.0 and not 4.1.2.

Thank you, @MidnightDesign, for your time and contribution!

@MidnightDesign
Copy link
Contributor Author

@driehle Would it be possible to release 4.2? We're waiting for this change. Thanks!

@driehle
Copy link
Member

driehle commented Nov 8, 2022

I am planning to first get #270 merged before releasing 4.2.0. However, I expect to make a release today or tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants