Your WordPress Site's End-of-Year Upgrade Calendar: 7.2, PHP 8.2 and MySQL 8.0 in One Plan
Dated plan for WordPress 7.2 (8 Dec), PHP 8.2 support ending 31 Dec and MySQL 8.0 end of life: week-by-week staging steps, commands and rollbacks.

If you run WordPress sites, the dates that matter this winter are: WordPress 7.2 on 8 December 2026, the end of PHP 8.2 security support on 31 December 2026, and a database that is already past its date if it is MySQL 8.0 (end of life in April 2026). The order we use is database and PHP first, on staging, then the 7.2 release candidates on a second copy, then PHP on production before the core release, and WordPress 7.2 itself on production last. The calendar below starts today, 15 November, and runs to the first week of January.
This is operational guidance for people who look after one site or a fleet. Your host, plugins and theme decide what is safe, so every step is tested on a copy first. We checked every date on 15 November 2026 against the sources named under each heading.
In this guide
- The three dates, and what each one does and does not mean
- Which database action applies to you (MySQL 8.0, MySQL 8.4, MariaDB)
- The dated calendar from 16 November 2026 to 4 January 2027
- Inventory: what each site runs today
- Staging, the fixed test pass, and the order of upgrades
- Go or no-go after RC 3, cut-over day and rollbacks
- Common mistakes people report
- Questions people ask
When is WordPress 7.2 released, and which dates matter?
Three layers of the stack reach a date, and each is a different kind of event. Dates were read on 15 November 2026.
WordPress core: 7.2 is scheduled for 8 December 2026
The official WordPress 7.2 release party schedule lists the remaining milestones, all at 15:00 UTC. Beta 3 shipped early, on 28 October, together with the 7.1.4 security release, and Beta 5 went out on 10 November. The Beta 5 announcement repeats 8 December as the scheduled final release date.
Milestone | Date (UTC) | Status on 15 Nov |
|---|---|---|
Beta 4 | 3 November 2026 | Released |
Beta 5 | 10 November 2026 | Released |
Release candidate 1 (RC 1) | 17 November 2026, 15:00 | Next |
RC 2 | 24 November 2026, 15:00 | Scheduled |
RC 3 | 1 December 2026, 15:00 | Scheduled |
Dry run and 24-hour code freeze | 7 December 2026, 15:00 | Scheduled |
General release | 8 December 2026, 15:00 | Scheduled |
The schedule post says there may be last-minute adjustments and that it is the canonical reference, so re-read it before you promise a client a date. The current stable release is WordPress 7.1.4, published on 28 October as a security release.
PHP: 8.2 security support ends 31 December 2026
The php.net supported versions page shows these dates:
PHP version | Active support ends | Security support ends |
|---|---|---|
8.2 | 31 Dec 2024 | 31 Dec 2026 |
8.3 | 31 Dec 2025 | 31 Dec 2027 |
8.4 | 31 Dec 2026 | 31 Dec 2028 |
8.5 | 31 Dec 2027 | 31 Dec 2029 |
After 31 December a site on 8.2 runs a version that no longer gets fixes from the PHP project. Nothing breaks on 1 January; the risk is that the next PHP security flaw has no upstream patch for you. PHP 8.1 is already off the supported table.
The WordPress.org requirements page recommends PHP 8.3 or greater, and MariaDB 10.11 or greater or MySQL 8.4 or greater. It also says WordPress still works on PHP 7.4+ and MySQL 5.5.5+, but those have reached end of life and may expose your site to security vulnerabilities. Our 8 October version of this post quoted that page as saying MySQL 8.0 or greater, so the wording has moved. One more forward date: the Beta 5 post says WordPress 7.2 aims to fully support PHP 8.6, which is scheduled for release on 19 November 2026, and that all known compatibility issues in core were resolved as of Beta 5. It adds that you must check your own plugins and themes before moving. We would not put 8.6 on a production site in the first weeks.
Database: MySQL 8.0 is past its date, MariaDB has its own calendar
MySQL and MariaDB are separate products with different version numbers. 8.0 and 8.4 are MySQL. 10.11 and 11.8 are MariaDB. A MariaDB date tells you nothing about MySQL, and the reverse.
For MySQL, Oracle’s end-of-life notices page says 8.0 binaries continue until EOL in April 2026, and that as of 21 April 2026 MySQL 8.0 is covered under Oracle Sustaining Support. It encourages users to upgrade to MySQL 8.4 LTS or 9.7 LTS. The tracker endoflife.date lists 30 April 2026 as the 8.0 end-of-life day and 30 April 2032 for 8.4 LTS, with premier support to 30 April 2029. That tracker is a third-party summary, so read Oracle’s lifetime support policy before you quote those later dates to a client.
For MariaDB, the maintenance policy gives these community end-of-life dates:
MariaDB release | Community end of maintenance | Meaning for a WordPress site |
|---|---|---|
10.6 | 6 July 2026 | Already past; plan the move now |
10.11 | 16 February 2028 | Meets the WordPress recommendation; time to plan |
11.4 | 29 May 2029 | Supported |
11.8 | 4 June 2028 | Supported |
12.3 | 12 June 2029 | Newest long-term release, generally available since 28 May 2026 |
If you want the Site Health side of this, our post on the Site Health outdated SQL server notice explains what the warning checks.
WooCommerce stores: a PHP 8.1 minimum arrives in February
The WooCommerce developer blog says WooCommerce 11.6, planned for February 2027, will require PHP 8.1 or newer. Stores on PHP 7.4 or 8.0 can keep updating up to 11.5, and WooCommerce recommends PHP 8.3 or newer. A store that moves to 8.3 for the 8.2 deadline meets this too.
Which database action applies to your site?
Run the inventory in the next sections first, then pick the row that matches what SELECT VERSION() returns. If only your host can change the database, your action is to ask for a date and a staging copy on the new version.
What you run | Action | When |
|---|---|---|
MySQL 8.0 | Move to MySQL 8.4 LTS on staging, test, then production. Check database users for the native password plugin first (see mistakes below). | Staging this week, production before RC 3 if the host allows it |
MySQL 8.4 or newer | Nothing for the calendar. Confirm the WordPress database user logs in cleanly. | None |
MariaDB 10.6 | Move to 10.11 or newer. 10.6 passed its community end date on 6 July 2026. | Staging this week |
MariaDB 10.11 or newer | No deadline in this calendar. 10.11 runs to February 2028. | Plan next year |
Managed host, version unknown | Ask the host which version you are on and when they move accounts. | Ask before 20 November |
What is the dated calendar, from 16 November to 4 January?
Each row starts on a Monday. The upstream column is what the sources say happens that week. The “You do” column is our recommendation, so shift it to fit your sites. If you started the plan earlier, catch up from the first row you have not done.
Week of | Upstream | You do |
|---|---|---|
16 Nov | Beta 5 is out. RC 1 on 17 Nov. PHP 8.6 due 19 Nov. | Inventory every site. Build the staging copy. Run the test pass on today’s stack as a baseline. Ask hosts for database and PHP dates. |
23 Nov | RC 2 on 24 Nov. Black Friday is 27 Nov, Cyber Monday 30 Nov. | Stores: no production changes from 25 Nov to 1 Dec. On staging, move the database and PHP (8.3 target). Debug log on. Start the soak. |
30 Nov | RC 3 on 1 Dec. | Install RC 3 on a second staging copy. Full test pass. Report plugin problems to authors. Go or no-go meeting on 2 or 3 Dec. |
7 Dec | Dry run on 7 Dec. WordPress 7.2 on 8 Dec. | Backups first. Read the release post. Production PHP change early in the week for sites that passed, then core from 8 Dec, one group at a time. |
14 Dec | Nothing scheduled in these sources. | Monitoring week. Read logs daily, check orders, forms and mail. Update the rest of the fleet. |
21 Dec | Holiday period. | No production changes except security fixes. Spot-check the busiest sites. |
28 Dec | PHP 8.2 security support ends 31 Dec. | Confirm no site is on 8.2. Get any exception approved in writing. |
4 Jan 2027 | Nothing scheduled in these sources. | Wrap-up: update the sheet, send the client summary, delete the beta copy, note WooCommerce 11.6 for February. |
Two choices in that table are ours, not upstream rules. First, PHP goes to production before the core release, so a PHP problem is not confused with a 7.2 problem. Second, the store freeze around Black Friday is common sense for shops, not a WordPress requirement. Our companion post, Update the Same Day or Wait?, explains how to decide the core step for each site.
What does each site run today?
You need a table of what each environment runs. Fill one row per environment (production, staging, local), because they often differ and a staging copy that does not match production proves little. Run these from the WordPress root. Checked on 15 November 2026.
# WordPress version
wp core version
# PHP used by WP-CLI (the command line), plus WP-CLI details
wp cli info
php -v
# Database engine and version (the string says MariaDB if it is MariaDB)
wp db query "SELECT VERSION();"
# Plugins, with status and version
wp plugin list --fields=name,status,version,update_versionThere is a trap in the PHP line. The command line and the web server can run different PHP versions. wp cli info and php -v report the command line. Visitors get the web version, and that is the one the deadline is about. Read it in the admin under Tools, Site Health, Info, Server. Write down both. If they differ, that is a finding: system cron runs on the CLI version while page loads use the web version, so a mismatch can hide a bug on one side.
Environment | WordPress | PHP (web) | PHP (CLI) | Database and version | Who can change it |
|---|---|---|---|---|---|
Production | |||||
Staging | |||||
Local |
For a fleet, run the same commands in a loop with --path or WP-CLI aliases and collect the output in one sheet. Our post on WordPress auto-updates at fleet scale covers the fleet setup, so we skip it here.
How do you build a staging copy that cannot email or charge customers?
Staging is a full duplicate of files and database that visitors never reach and that cannot send real email or take real payments. It must be close to production: same plugins, similar data, and ideally the same server type.
- Back up production: database export plus a files archive.
- Create the copy on a server as close to production as you can. Many hosts have one-click staging.
- Import the database and replace the production domain with the staging domain.
- Make it safe: discourage search engines, mark the environment as staging, stop real email, and put payment gateways in test mode with sandbox keys.
# On production: export the database (store the file outside the web root)
wp db export ../backups/pre-upgrade-$(date +%F).sql
# On staging: import it, then swap the domain (dry run first)
wp db import ../backups/pre-upgrade-2026-11-16.sql
wp search-replace 'https://www.example.com' 'https://staging.example.com' --all-tables --dry-run
wp search-replace 'https://www.example.com' 'https://staging.example.com' --all-tables
# Make staging safe
wp option update blog_public 0
wp config set WP_ENVIRONMENT_TYPE stagingTurn on logging on staging with WP_DEBUG, WP_DEBUG_LOG and WP_DEBUG_DISPLAY set to false. Our post on reading WordPress error logs explains Fatal, Warning, Notice and Deprecated. Deprecated warns of future breakage; Fatal is failure now.
What is the fixed test pass to run after every change?
Run the same list in the same order and write down the result, so you can compare run to run. Add site-specific steps at the end; never remove steps.
- Login as an administrator and as your lowest-privilege role. Request a password reset email.
- The editor: open an existing post and a new one, add a paragraph, an image, a heading and a block from your most used block plugin, save, preview, publish. A blank editor or endless spinner usually means a script error.
- Forms: submit every form type once and confirm the entry is stored and the notification arrives.
- The money path: for a store, add to cart, coupon, shipping and a test-mode checkout, then open the order. For membership or donations, signup and renewal. For lead sites, the quote form to CRM hand-off.
- Scheduled tasks: list events, run the due ones, watch for errors.
- Email: send a test message and confirm delivery.
- The log: read the debug log after steps 1 to 6 and note every Fatal and every new Deprecated line with the plugin or theme file it names.
# Step 5: scheduled tasks
wp cron event list
wp cron event run --due-now
# Step 6: email test (replace the address)
wp eval 'var_dump( wp_mail( "you@example.com", "Staging mail test", "Test body" ) );'
# Step 7: the log (path depends on your WP_DEBUG_LOG setting)
tail -n 100 wp-content/debug.logOur hands-on companion, See What a PHP Upgrade Will Break Before Your Host Does It, goes deeper on one job inside this plan: finding which plugin or theme file will start throwing errors, including a static scan with PHPCompatibilityWP.
In what order should you upgrade the layers?
Database and PHP on staging first, then the core release candidates on a separate staging copy, then PHP on production, then core on production after the release. The reasons:
- One variable at a time. If PHP changes a week or more before core, a bug in between belongs to PHP.
- The deadline layers have fixed dates. PHP 8.2 support ends on 31 December and cannot be negotiated. You pick your own day for 7.2, so take it last.
- The database is the hardest to undo. Going back to an older engine version is not something to count on. Plan the rollback as a restore from backup and leave the longest gap between the database change and the core release.
- Never put a beta or RC on production. The Beta 5 announcement says not to install or test it on production or mission-critical sites.
To test a release candidate on the second staging copy, the Beta 5 post gives the WP-CLI form of the command; swap in the RC version string once it exists. Checked on 15 November 2026.
# Install a pre-release on the second staging copy (use the exact version string from the release post)
wp core update --version=7.2-beta5
# Step back to the stable release on staging if you need to reset
wp core update --version=7.1.4 --forceThe --force flag lets WP-CLI update even when the installed version is newer than the requested one, which is what a step back needs. Restore the matching database backup as well, because a newer core can change tables and restoring files alone does not undo that.
Our default PHP target is 8.3: WordPress.org and WooCommerce both recommend it, and php.net gives it security support to 31 December 2027. Treat 8.4 as a stretch goal.
How do you decide go or no-go after RC 3?
RC 3 is scheduled for 1 December, a week before release. Hold the decision meeting on 2 or 3 December with the RC 3 test pass in front of you. The question is per site, not for the whole fleet. A site is a go when:
- It passed the full test pass on RC 3 with no new Fatal lines in the log.
- It already runs the target PHP and database on production and has done so for at least a week without new errors (two weeks if the calendar allows).
- Every plugin and the theme is updated or confirmed compatible by its vendor, or tested by you on RC 3.
- A fresh backup is planned and a named person can run the rollback.
A site is a no-go for now when a money-path step fails on RC 3, when a needed plugin has no update and breaks, or when the release lands in a bad week for the business. No-go means the site stays on 7.1.x until you have a fix. What is not reasonable is staying on PHP 8.2 past 31 December because nothing looks broken.
What does cut-over day look like, with a rollback for each layer?
You will have up to three cut-overs: the database (if you control it), PHP and WordPress core. Each follows the same shape: backup, change, test pass, watch. Test each rollback on staging before you need it.
# Pre-change backup of the database
wp db export ../backups/pre-change-$(date +%F-%H%M).sql
# Verify the file exists and has size
ls -lh ../backups/Layer 1: database
On a host you control, follow the vendor upgrade guide (for MySQL, 8.0 to 8.4 LTS). On managed hosting, ask for the date, a staging copy on the new version and a backup before the change. Rollback: restore the pre-change backup into the previous engine version. In-place downgrades are not something to rely on, so keep the old server or a snapshot until the monitoring week ends.
Layer 2: PHP
Switch the version in the host panel, the FPM pool or the server configuration, keep the old version installed, then confirm the web version in Site Health. Change the CLI version too if it differs. Rollback: switch the setting back. It is the fastest rollback of the three because nothing in the database changes, which is why PHP is the right production change to make early.
Layer 3: WordPress core
Read the release post, take a backup immediately before, then update.
wp core update --version=7.2
wp core update-db
wp plugin list --fields=name,status,version,update_version
wp core versionRollback: restore the files and database taken just before. wp core update --version=7.1.4 --force puts the old core files back, but a major release can change tables, so the database restore is what completes the rollback. If a store took orders between the update and the rollback you need a plan for them, which is the best reason to update in a quiet window and run the test pass straight away.
What happens in the monitoring week?
The week of 14 December is for watching, not for new changes. Check each updated site on a fixed rhythm: the log on day one and day two, then every second day. Look for new Fatal errors, new Deprecated lines, failed scheduled events and queued mail that never leaves.
wp cron event list
wp plugin list --fields=name,status,version,update_version
tail -n 200 wp-content/debug.logThen update the rest of the fleet in groups: sites already on target first, the others after their fixes. In the holiday week make no production changes except security fixes. On the week of 28 December confirm no site is still on PHP 8.2 and record the client’s written decision for any exception.
What should you tell clients, and when?
Clients need the date, the effect on them and what you need from them, not version numbers.
- Now (mid November): a heads-up that three parts of the site’s technology reach support dates by the end of the year, that you test on a copy first, and that they need to do nothing yet. If a bought plugin or theme may need a paid update, say so now, not in December.
- Late November: the change window and the dates to avoid.
- The day after: done, tested, being watched this week.
- Early January: a summary of what changed and what is supported until when. Stores also get the PHP 8.1 minimum coming in February.
If you must delay a site, tell the client why in plain language: staying on PHP 8.2 after 31 December means running a version without upstream security fixes. Keep a written record of every exception. This is operational advice, not legal advice; if your contracts promise a specific security standard, check the wording.
Common mistakes people report
These recur in public plugin issue trackers, forums and vendor write-ups. We paraphrase them and link each source. Checked on 15 November 2026.
- Moving PHP and reading only the front end. After a move to 8.3, sites often keep working while the error log fills with deprecation notices from bundled libraries. A user of AMP for WP on WordPress 7.1.4 and PHP 8.3.36 reported repeated warnings (dynamic properties and incompatible return types) from a vendor folder inside the plugin, filed 5 November 2026. Read the log, do not just look at the homepage.
- Notices that appear on screens that have nothing to do with the plugin. A GetPaid issue opened on 2 November 2026 describes a save handler that runs on every post type save and triggers PHP 8.3 “passing null” deprecations when an unrelated listing is saved. Test saving every post type you use, not only the plugin’s own screens.
- Dozens of dynamic-property notices after the version bump. A WordPress.org forum thread (older, from early 2024, but the same pattern is still reported) counts more than 35 deprecation lines from one plugin after a move to PHP 8.3. Count and group the log lines per plugin and send each author the exact lines.
- Database connection errors after moving to MySQL 8.4. MySQL 8.4 no longer loads the
mysql_native_passwordplugin by default, so an account that still uses it fails with “Plugin ‘mysql_native_password’ is not loaded”. PHP.Watch explains the error and the fix (published 15 May 2024), and WordPress core tracked its own 8.4 preparation in Trac ticket 61218. Switch the WordPress database user tocaching_sha2_passwordon staging before you move production. - Testing a pre-release where customers can see it. The Beta 5 post is blunt that betas are for test environments only. Keep betas and RCs on a staging copy that cannot send mail or take payments.
Here is the query for the database mistake, run on a MySQL server before the move. Checked on 15 November 2026. Replace the names, run it as an administrator, and test the login on staging first.
-- Which accounts still use the old plugin?
SELECT user, host, plugin FROM mysql.user WHERE plugin = 'mysql_native_password';
-- Move the WordPress database user to the current plugin (set a new password)
ALTER USER 'wp_user'@'localhost' IDENTIFIED WITH caching_sha2_password BY 'a-new-strong-password';After the change, update DB_PASSWORD in wp-config.php to match, and test a page load on staging.
Questions people ask
When does WordPress 7.2 come out?
It is scheduled for 8 December 2026 at 15:00 UTC, with RC 1 on 17 November, RC 2 on 24 November and RC 3 on 1 December. The Beta 5 announcement of 10 November repeats the date.
Do we have to leave PHP 8.2 before 31 December?
PHP security support for 8.2 ends on 31 December 2026 per php.net. Nothing breaks on 1 January, but upstream stops shipping security fixes. We plan to be off it before the date, so the move is a planned change with a rollback and not an emergency.
Is MySQL 8.0 end of life?
Oracle’s notice says 8.0 reaches end of life in April 2026 and that from 21 April 2026 it is under Sustaining Support. The WordPress.org requirements page now recommends MySQL 8.4 or greater. Moving to 8.4 LTS is the conservative step.
Is MariaDB affected by the MySQL 8.0 change?
No. MariaDB has its own policy. Check your engine first: SELECT VERSION() includes the word MariaDB if it is MariaDB. Then check your release: 10.6 passed its community end date on 6 July 2026, and 10.11 runs to 16 February 2028.
Our host controls the database version. What do we do?
Ask for three things: the date they will move you, a staging site on the new version first, and how to roll back. If the host will not give a date by the end of November, treat it as a risk and tell the client.
If you would rather hand this calendar to someone else, our WordPress maintenance services page explains how we look after updates, staging and monitoring. It is one option; the plan above works without us.
Plugins we build and run
We maintain these ourselves, which is why we can support them on your site.
- BuddyNextThe self-hosted community engine for WordPress
- BuddyXFree community theme, Pro when you outgrow it
- ReignPremium community theme. Add pieces, build anything
- JetonomyCommunity forum and Q&A for WordPress
- EventonomyEvents and RSVPs for WordPress communities
- LearnomyCourses and learning communities on WordPress
- ListoraDirectories and listings your members can browse
- SnipShareCode sharing built for developer communities
- WB Ad ManagerAd placements that turn traffic into revenue
- WP Career BoardA job board your community actually uses
- WP Sell ServicesSell services with offers, orders, and payouts
- MediaVersePhotos, video, and media albums for members
- WB GamificationPoints, badges, and rewards that keep members active
- Product RoadmapPublic roadmaps with voting your users trust
Related Posts

LiteSpeed Cache Vulnerability CVE-2026-93389: Check Your Version and What Was Exposed

Freemius SDK Stored XSS: How to Find Every Bundled Copy on a Client Site (Anything Under 2.13.5)

