3.5.4 contains deprecation warnings planned for 3.6.0 #12267
Description
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 #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