3.5.4 contains deprecation warnings planned for 3.6.0 #7574

Closed
opened 2026-01-22 15:53:41 +01:00 by admin · 5 comments
Owner

Originally created by @W0rma on GitHub (Nov 11, 2025).

Bug Report

I noticed the following deprecation warnings when switching from 3.5.3 to 3.5.4:

Specifying the "nullable" attribute for join columns in to-one associations that are part of the identifier is a no-op. The ORM will always set it to false. Doing so is deprecated and will be an error in 4.0. (ToOneOwningSideMapping.php:136 called by ClassMetadata.php:1421, https://github.com/doctrine/orm/pull/12126, package doctrine/orm)

Using WITH for the join condition of arbitrary joins is deprecated. Use ON instead. (Parser.php:1665 called by Parser.php:1544, https://github.com/doctrine/orm/issues/12192, package doctrine/orm)

I'm not sure if it is really intended that they are added in a bugfix release.

Q A
Version 3.5.4
Previous Version if the bug is a regression 3.5.3

Summary

3.5.4 introduced new deprecation warnings which were obviously planned for 3.6.0.

Seems like https://github.com/doctrine/orm/pull/12244 merged 3.6.x into 3.5.x which may have caused this.

Current behavior

Deprecation warnings occur in 3.5.4

Expected behavior

No deprecation warnings should have been added

How to reproduce

Originally created by @W0rma on GitHub (Nov 11, 2025). ### Bug Report I noticed the following deprecation warnings when switching from `3.5.3` to `3.5.4`: > Specifying the "nullable" attribute for join columns in to-one associations that are part of the identifier is a no-op. The ORM will always set it to false. Doing so is deprecated and will be an error in 4.0. (ToOneOwningSideMapping.php:136 called by ClassMetadata.php:1421, `https://github.com/doctrine/orm/pull/12126`, package doctrine/orm) > > Using WITH for the join condition of arbitrary joins is deprecated. Use ON instead. (Parser.php:1665 called by Parser.php:1544, `https://github.com/doctrine/orm/issues/12192`, package doctrine/orm) I'm not sure if it is really intended that they are added in a bugfix release. | Q | A |-------------------------------------------- | ------ | Version | 3.5.4 | Previous Version if the bug is a regression | 3.5.3 #### Summary `3.5.4` introduced new deprecation warnings which were obviously planned for `3.6.0`. Seems like https://github.com/doctrine/orm/pull/12244 merged `3.6.x` into `3.5.x` which may have caused this. #### Current behavior Deprecation warnings occur in `3.5.4` #### Expected behavior No deprecation warnings should have been added #### How to reproduce
admin closed this issue 2026-01-22 15:53:41 +01:00
Author
Owner

@derrabus commented on GitHub (Nov 11, 2025):

cc @greg0ire

@derrabus commented on GitHub (Nov 11, 2025): cc @greg0ire
Author
Owner

@greg0ire commented on GitHub (Nov 11, 2025):

Oh shit 😧 I will try to fix it.

@greg0ire commented on GitHub (Nov 11, 2025): Oh shit 😧 I will try to fix it.
Author
Owner

@greg0ire commented on GitHub (Nov 11, 2025):

3.6.x is currently up to date with 3.5.x, so the right thing to do after merging https://github.com/doctrine/orm/pull/12269 is a git merge -s ours origin/3.5.x

@greg0ire commented on GitHub (Nov 11, 2025): 3.6.x is currently up to date with 3.5.x, so the right thing to do after merging https://github.com/doctrine/orm/pull/12269 is a `git merge -s ours origin/3.5.x`
Author
Owner

@greg0ire commented on GitHub (Nov 11, 2025):

Fixed in 3.5.7 Thanks for reporting this @W0rma 🙏

@greg0ire commented on GitHub (Nov 11, 2025): Fixed in 3.5.7 Thanks for reporting this @W0rma 🙏
Author
Owner

@W0rma commented on GitHub (Nov 12, 2025):

@greg0ire Thank you for the quick fix and for all your effort you put into the Doctrine projects 👍

@W0rma commented on GitHub (Nov 12, 2025): @greg0ire Thank you for the quick fix and for all your effort you put into the Doctrine projects 👍
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#7574