WordPress 6.9.1 is out, and plenty of people will skip it because 7.0 lands in April anyway. That is usually how you end up with a broken checkout or a white screen on a random Tuesday.
I have been managing WordPress stacks for 14 years, and the short-cycle patches tend to be the safest ones to take. This one clears 49 bugs that had been sitting in Core and the Block Editor. If your mail delivery or a classic theme has been behaving oddly lately, the fix is probably in here.
What is inside WordPress 6.9.1
The changes land in the places that get hit constantly: the Gutenberg block editor and the internal wp_mail logic. If your transactional email has been hitting race conditions or failing silently, audit your logs once the update is in. A lot of contributors coordinated to get these asynchronous fixes shipped, and what you get out of it is a site that stays up.
Maintenance cycles have been messy before. My take on the 6.9 maintenance mess should make it clear I do not hand out praise easily, but 6.9.1 reads like a decent cleanup.
Updating without breaking production
Do not click the update button in the dashboard and hope. On production sites, run the update through WP-CLI so you can verify the checksums and confirm nothing got corrupted on the way down.
# Backup your database first!
wp db export backup.sql
# Update WordPress Core to 6.9.1
wp core update --version=6.9.1
# Verify checksums to ensure integrity
wp core verify-checksumsIf you have custom logic hooked into the Block Editor, read through the Gutenberg PRs in this release. A fix to a Core block can quietly override a filter you set up in your theme’s functions.php.
If you are already planning the bigger jump, my guide on preparing for WP 7.0 covers that side of it. April arrives sooner than it looks, and 6.9.1 is part of getting there.
If WordPress 6.9.1 is eating your dev hours, I can take it off your plate. I have been working with WordPress since the 4.x days.
Where that leaves you
Take this one. It fixes 49 bugs across Core and the Block Editor, including the ones breaking classic themes and mail. Run it on staging, check that your hooks still fire, then push it to production. There is no reason to sit on broken behavior until 7.0.
