Requirements page: Bump recommended versions of MySQL and MariaDB #226
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket: https://meta.trac.wordpress.org/ticket/7236
It is planned to update the Rosetta site to the new version in the following issue, and the new version is already enabled in some locales.
WordPress/wporg-main-2022#266
My understanding is that if the new version is enabled, the Requirements page will load the following pattern:
https://github.com/WordPress/wporg-main-2022/blob/trunk/source/wp-content/themes/wporg-main-2022/patterns/about-requirements.php
The recommended version of this pattern is output via a shortcode and has been updated by the PRs below.
However, if a Rosetta site is not yet a new version, the page template below is loaded.
https://github.com/WordPress/wordpress.org/blob/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-main/page-about-requirements.php
Therefore, it is necessary to update the recommended version of MySQL/MariaDB even in locales where the new version has not yet been applied.
Below is the current Requirements page for the Japanese locale, which is not yet a new version.