Could you please backport the [55504] patch to the 6.1 branch?

[hassy6thsense]

This is the first core bug I've ever reported so apologies if I don't quite follow correct protocol.

I'm using WordPress 6.1.x with PHP 8.2.5 on Windows Server 2019.
I still need to use 6.1 because some of the plugins I use have not yet announced support for 6.2.

Due to a bug reported in #57218, a 500 error is displayed when entering maintenance mode on plugin updates.
I know to be fixed in patch [55504] for 6.2, but has not been backported to 6.1.
I had manually backported the fixes made in 6.2 to 6.1.1, but recently 6.1.2 was released and the backports were rolled back.
I re-did the backport, but not long after, 6.1.3 was released and reset again...
There is no function to turn off automatic maintenance update for WordPress, and I don't want to turn it off for security reasons.

#57218 was closed due to "no plans for 6.1.2, so the milestone has been moved to 6.2", but there have been two maintenance releases since then.
And from past release history, I think there will be some maintenance releases for 6.1 in the future.
So, could you please backport the [55504] patch to the next maintenance release (6.1.4)?

[audrasjb]

Hello and welcome to WordPress Core Trac, thanks for opening this ticket,

Sorry but only security fixes are backported to previous releases. Previous branches should not really be considered as “maintained”.

"Officially WordPress only provides support for the latest version of the software. The Security team historically has a practice of backporting security fixes as a courtesy to sites on older versions in the expectation the sites will be automatically updated"
​(source)

Also we can not backport fixes based on individual requests, it would quickly get impossible to manage, and we would probably end up maintaining several branches of the CMS :)

There is no function to turn off automatic maintenance update for WordPress, and I don't want to turn it off for security reasons.

Actually, ​there is an option to turn off auto-updates for minor releases, but I wouldn't recommend it either.

I still need to use 6.1 because some of the plugins I use have not yet announced support for 6.2.

I think the point is that these plugin authors probably forgot to update their readme to indicate compatibility. This happens frequently. The best would be to contact them via each plugin's support forum and ask them to confirm the compatibility of their plugin.

Let's close this ticket as wontfix, since there is no plan to backport maintenance fixes to older branches.
Thank you for understanding!

[hassy6thsense]

Replying to audrasjb:

Thank you for your reply. And sorry for the lack of understanding of the backport policy.

I think the point is that these plugin authors probably forgot to update their readme to indicate compatibility.This happens frequently.The best would be to contact them via each plugin's support forum and ask them to confirm the compatibility of their plugin.

I see. Certainly I occasionally forget to update the README. I will ask the developer of each plugin on the forums or see if someone has already asked.

[audrasjb]

Yes, I think it would be your best bet :)
Thank you for the follow-up reply!