Packages: Move unreleased changelog entries out of the 23.8 published versions - #81502
Packages: Move unreleased changelog entries out of the 23.8 published versions#81502sirreal wants to merge 1 commit into
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 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. |
ntsekouras
left a comment
There was a problem hiding this comment.
I verified with npm changelogs and looks good, thanks for handling this!
8094ca8 to
64c0347
Compare
|
Flaky tests detected in 64c0347. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/31597852239 does not dirty related template parts or navigation menus when rendered in the post editor in
|
Follow-up to #81485. The npm release backport was cherry-picked onto trunk while several changelog edits were in flight. Git auto-merged them textually and filed nine entries under the newly published version headings, in packages
block-editor,block-library,componentsanddataviews.None of the six PRs involved (#80747, #81292, #81361, #81449, #81450, #81451) are ancestors of the publish commit
989764d42ff, so none of that code is in the published tarballs. This moves the entries back under## Unreleased.No version or lockfile changes. After this, the released sections of all 125 package changelogs are byte-identical to what was published.
See #81506