Skip to content

Conversation

@mpdude
Copy link
Contributor

@mpdude mpdude commented Oct 26, 2025

This updates the code to avoid triggering the deprecation introduced in doctrine/collections#472.

Closes #12237.

@mpdude
Copy link
Contributor Author

mpdude commented Oct 26, 2025

@greg0ire Please advise: Should I bump requirements for doctrine/collections in composer.json here?

I guess I cannot, since we're still compatible with ^1.5 || ^2.1, and I cannot drop 1.x support?

@mpdude mpdude force-pushed the fix-collections-deprecation branch 2 times, most recently from 60148e0 to 0060f4d Compare October 26, 2025 22:12
This updates the code to avoid triggering the deprecation introduced in doctrine/collections#472.
@mpdude mpdude force-pushed the fix-collections-deprecation branch from 0060f4d to 1865717 Compare October 26, 2025 22:20
@greg0ire
Copy link
Member

That's right, you shouldn't. Not in a patch release anyway.

@mpdude
Copy link
Contributor Author

mpdude commented Oct 26, 2025

Found doctrine/doctrine-website#485. I knew we discussed that before.

So, how to make PHPStan happy when I cannot tell for sure if checking against doctrine/collections >= 2.4.0 or below that?

@greg0ire
Copy link
Member

What do you mean?

The CI job is installing doctrine/collections 2.4.0: https://github.com/doctrine/orm/actions/runs/18824547984/job/53705136455?pr=12238#step:6:102

@mpdude mpdude force-pushed the fix-collections-deprecation branch from f87e380 to da67f32 Compare October 27, 2025 18:51
@greg0ire greg0ire added this to the 2.20.7 milestone Oct 27, 2025
@greg0ire greg0ire merged commit 59938ca into doctrine:2.20.x Oct 27, 2025
91 checks passed
@greg0ire
Copy link
Member

Thanks @mpdude !

@mpdude mpdude deleted the fix-collections-deprecation branch October 27, 2025 22:58
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