Finish plugin updates, backups, and auto-update settings before December 7, then freeze changes. Make WordPress Core sets dry run plus 24-hour code freeze for December 7 and 7.2 release for December 8, 2026 at 15:00 UTC in the WordPress 7.2 release schedule.
A code freeze pauses last-minute core changes just before release. Plugin updates around that date can collide with core changes. The PHP Group lists branch 8.2 as reaching end of life on December 31, 2026 in the supported-versions table.
Table of Contents
- What should you freeze, and when?
- How do you make updates recoverable?
- In what order should you update?
- How should you handle auto-updates over the holidays?
What should you freeze, and when?
Freeze production after your December 7 checkpoint. Hold new plugins, major updates, and theme switches.
Allow only emergency security fixes. Work through this order before the checkpoint: Document the frozen version list. Share it with anyone who can click Update.
- inventory active plugins and record versions
- apply pending updates on staging first
- verify forms, checkout, search, and login
How do you make updates recoverable?
WordPress.org Documentation instructs owners to keep a current backup of files and database before updating plugins, explained in the plugin management guide. Make the backup restorable, not just stored. Store one copy off the server.
Include the database plus files. Test the restore steps on staging before you need them. Date each backup. Keep host, FTP, and database credentials where on-call staff can reach them.
In what order should you update?
WordPress.org Documentation gives a clear order in the PHP update guide. Back up first. Then update WordPress, themes, and plugins from Dashboard > Updates and verify the site. Check theme and plugin PHP compatibility before switching PHP versions.
Run that sequence on staging. Update one item at a time. Verify key pages after each step. Save PHP version changes for last. A late PHP switch leaves less time to fix plugin conflicts.
How should you handle auto-updates over the holidays?
Manual control reduces surprise when staffing is thin. An overnight change can break checkout or lead forms.
Decide per plugin before the freeze: Record each choice. Re-check the Updates screen after the release before making bulk changes.
- keep commerce, membership, and multilingual plugins on manual
- allow automatic security updates only for simple, low-risk utilities
- turn off bulk auto-updates on production during the release week
