Gutenberg 22.6 release checklist

[ockham]

This issue is to provide visibility on the progress of the release process of Gutenberg 22.6 and to centralize any conversations about it. The ultimate goal of this issue is to keep the reference of the steps, resources, work, and conversations about this release so it can be helpful for the next contributors releasing a new Gutenberg version.

• Gutenberg version to release: 22.6 (milestone)
• Release Manager (a.k.a. Release Lead): @ockham
• Release Date 22.6 RC: February 18, 2026
• Release Date 22.6: February 25, 2026
• Previous version change log (as a reference): 22.5.0

Resources

• 📖 Read: Gutenberg Release Process
• 📽 Watch: Gutenberg Plugin: New Release Workflow
• 📽 Watch: Creating the Gutenberg plugin v12.0 Release Candidate
• 📽 Watch: Gutenberg plugin v12.0.0 Release Party!

Checklist

RC Day - Wednesday, February 18, 2026

• Post a message in #core-editor channel to let folks know you are starting the RC release process
• Organize and Label PRs on the relevant milestone
• Start the release process by triggering the rc workflow
• Update the created Draft Release accordingly
• Curate the changelog before publishing
• Publish Release
• Approve the npm publishing job in the Build Plugin Zip workflow (ask in #core-editor if needed)
• Announce in #core-editor channel that RC1 has been released and is ready for testing
• Ping any other relevant channels announcing that the RC is available
• Create Draft of Release post on Make Core blog (initial draft in Google doc)

Between RC and Release

• Post a reminder in #core-editor for backporting PRs to RC (~Label Backport to Gutenberg RC)
• If there are any PRs marked as Backport to RC, run the cherry-pick command to apply them to the release branch. This needs to be run locally
• Draft Release Post Highlights and Change Log
• Get assets from Design Team for the post if required
• Reach out to Highlight Authors to draft sections (if necessary)

Release Day - Wednesday, February 25, 2026

• Post a message in #core-editor channel to let folks know you are starting the release process
• Start the release process by triggering the stable workflow
• Update the created Draft Release accordingly. Typically by copy/pasting the last RC release notes and add any changes/updates as needed.
• Publish Release
• Trigger the update to the plugin directory. (Get approval from a member of Gutenberg Release team if necessary)
• Announce in #core-editor channel that the plugin has been released
• Reach out to other contributors to help get the post reviewed
• Publish Release post on Make Core blog
• Post in the #core-editor channel requesting a volunteer for the next Gutenberg release.

[paulomfr]

Hi @ockham,

I don't know if this is the right place, but, it seems that @wordpress/vips wasn't published to NPM and because of it we can not install @wordpress/editor and other packages.

[jeanrinvil]

Hi,
Same issue @paulomfr with @wordpress/vips, can't create blocks

[ockham]

Thank you for reporting @paulomfr and @jeanrinvil, I'll look into this now.

FYI @ellatrix

[ockham]

A dedicated issue was just opened for this: #75718

[ockham]

@paulomfr and @jeanrinvil:

I've just published new versions of @wordpress/ npm packages (to include @andrewserong's two bugfixes).

I believe that this should fix the issue. I've tested by running npm i @wordpress/editor and npx @wordpress/create-block@latest copyright-date-block (each in a previously empty directory), and they seem to have worked.

Please test and let me know if it resolves the problem(s) y'all were seeing, or if any issues persist!

(#75718 (comment))

[ockham]

Release notes: https://make.wordpress.org/core/2026/02/25/whats-new-in-gutenberg-22-6-25-february/