-
Notifications
You must be signed in to change notification settings - Fork 3
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
Cannot install with doctrine/collections 1.0 #52
Comments
Are you sure doctrine/collections 2.x will be enough to fix this? Or will we need ORM 3.x support as well? |
I think we need to support all maintained versions, which for doctrine is
now a bit broad. There's a way in github actions to set up a matrix, but
I'm not sure exactly how to do that.
…On Fri, Apr 5, 2024, 1:43 PM Matthias Pigulla ***@***.***> wrote:
Are you sure doctrine/collections 2.x will be enough to fix this? Or will
we need ORM 3.x support as well?
—
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEXIQMIXNJ2OBK2FIROGRDY33PEVAVCNFSM6AAAAABFZEEF6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBQGMZDGNJSGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
At a short-term solution, we could simply use "*" for doctrine packages, and let composer figure it out. Obviously, we need to be explicit eventually, but right now I can't install it at all in my Symfony 7 projects. I guess I could remove doctrine, add this bundle, then add doctrine back, and hope that composer picks the right versions? |
Could you please re-check whether this is fixed with the 4.0.1 release of this bundle? |
No, because of psr/log
|
Merged #55. |
Wahoo, it installs! Can you publish 4.0.2 please? |
Released as 4.1.0 🚀 Thanks for bringing this forward! |
The text was updated successfully, but these errors were encountered: