Repository navigation
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @gutenbergplugin. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Size Change: 0 B Total Size: 2.58 MB ℹ️ View Unchanged
|
|
Flaky tests detected in 96247c9. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/20490240724
|
|
Closing in favor of #74413 |
What
Follow-up/alternative to #74202.
Backports the version bump from the 22.3 release to trunk.
Why
The last npm publish workflow failed to cherry-pick the version bump commit to trunk due to conflicts.
Without this fix, trunk is missing:
## X.Y.0 (2025-12-23)version headers in all package CHANGELOGspackage.jsonversion bumps (still showing-prereleasesuffixes)How
Cherry-picking commit
d096bed11dfromwp/latestand manually resolving the two CHANGELOG conflicts by preserving both the Unreleased content (from trunk) and the version headers (from the release).Testing Instructions
## X.Y.0 (2025-12-23)version header after the## Unreleasedsectionpackage.jsonversions are updated to match