Upgrades, deprecations, compatibility checks and release verification.
View All Tags
Next.js plans an out-of-band security update on Wednesday, October 14, 2026, for three vulnerabilities in upstream dependencies: two Critical and one High. The affected versions arrive only with the update. My call is to prepare now: list every Next.js app, name an owner, dry-run a dependency-only deploy and write the smoke test before the advisory is published.
WordPress 7.0 ships five block-editor changes that look small in a changelog and can still break custom patterns, mislead teams about hidden content, and let editors inject CSS into blocks that were never built for it. The dev notes landed on March 15, 2026, and they cover content-only pattern editing, viewport-based block visibility, per-block custom CSS, expanded dimensions support and native text indent. The good news is that several of them let plugin and theme teams delete custom UI and CSS they have been carrying for years.
Pantheon switched the Drupal CMS upstream to Drupal CMS 2 on March 6, 2026, for new sites only. Existing Drupal CMS sites are not auto-updated and Drupal 10/11 upstream sites are not affected, so a team that reads this as "new upstream, apply everywhere" is about to run a migration by accident.
WordPress 6.9 added assertEqualHTML(), so a test that fails because of whitespace in rendered HTML no longer has an excuse. I reviewed the implementation and mapped concrete migration patterns for plugin and theme test suites, plus the places where assertSame() should stay.
As of February 25, 2026, my call is to move production to Node 24.14.0 LTS first, run Node 25.7.0 in a lane that cannot fail the build, and spend the worry budget on native addons and framework engines ranges. Both versions shipped on February 24, 2026, but 24.x is LTS and 25.x is still the Current line.