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

fix: add conflict for doctrine/orm >= 2.16.0 #2661

Conversation

Chris53897
Copy link
Contributor

#2659

This helps to get the ci green.
But does not prevent the installation on userside of older versions with 3.12.0 and doctrine-orm >= 2.16.0

@codecov-commenter
Copy link

codecov-commenter commented Aug 2, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (ef277c9) 79.22% compared to head (e8d0a6f) 79.22%.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2661   +/-   ##
=======================================
  Coverage   79.22%   79.22%           
=======================================
  Files         161      161           
  Lines        8415     8415           
=======================================
  Hits         6667     6667           
  Misses       1748     1748           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Collaborator

@franmomu franmomu left a comment

Choose a reason for hiding this comment

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

We should probably update several things to make it work, I think we can go with this for now and try to see if these bugs are in our code.

@Chris53897
Copy link
Contributor Author

There are ongoing new issues if these latest changes in 2.16 are BC breaks or not.
https://github.com/doctrine/orm/issues/

Maybe they will revert some changes? But this repo needs to change some code.

@Chris53897 Chris53897 force-pushed the fix-add-conflict-with-doctrine-rom-2-16 branch from 716a22d to e8d0a6f Compare August 3, 2023 07:04
@franmomu franmomu requested a review from phansys August 6, 2023 14:27
@franmomu franmomu merged commit 31ed28b into doctrine-extensions:main Aug 11, 2023
18 checks passed
@franmomu
Copy link
Collaborator

franmomu commented Aug 11, 2023

Let's merge this since it would unblock other PRs and leave #2659 open since I don't think it would be easy to fix.

thanks @Chris53897!

@franmomu franmomu added the Bug A confirmed bug in Extensions that needs fixing. label Aug 14, 2023
@Chris53897 Chris53897 deleted the fix-add-conflict-with-doctrine-rom-2-16 branch February 19, 2024 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug A confirmed bug in Extensions that needs fixing.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants