Bug introduced in #56467 / [54335] in a @worpdress package update during 6.1.0 Beta 2 cycle (back in September 2022).
With 6.2 in the RC phase, RC guidelines limit commits to only bugs and regressions introduced in 6.2 https://make.wordpress.org/core/2023/03/09/wordpress-6-2-release-candidate-phase/.
For the remainder of the cycle, only two types of tickets may be placed on/remain on the 6.2 milestone:
- Regressions: bugs that have been introduced during the WordPress 6.2 development cycle, either to existing or new features.
- Test suite expansion: tests can be committed at any time without regard to code or string freezes. This can cover either new or existing features.
That said, this is a fatal error. Since it's a fatal error, let's discuss if it should be fixed during RC or punted to 6.2.1.
Some thoughts:
- The code change is minor with little to no risk.
- But why hasn't been reported sooner? This makes me think it's a highly specific use case, meaning it could be okay to punt it to 6.2.1.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
