Repository navigation
Backport npm publish metadata to release/23.5 - #79824
Merged
Merged
Conversation
|
Size Change: 0 B Total Size: 7.51 MB |
|
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. |
aduth
approved these changes
Jul 2, 2026
ciampo
commented
Jul 2, 2026
Comment on lines
+3
to
+6
| ## Unreleased | ||
|
|
||
| ## 2.50.0 (2026-07-01) | ||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Backports the corrected npm publish metadata to
release/23.5:packages/*/package.jsonpackage-lock.jsonWhy?
The npm publish workflow published the packages, but failed before pushing the version commit/tags back to the repository. This keeps the release branch coherent with the corrected
wp/latestmetadata from #79821.How?
Transplants the corrected release metadata from #79821 onto
release/23.5. The resultingpackage-lock.jsonandpackages/tree match the correctedwp/latestmetadata branch.Testing Instructions
npm install --package-lock-only --ignore-scripts --offlinegit diff --cached --checknpm run lint:pkg-jsonnpm run lint:lockfilepackage-lock.jsonandpackages/match the correctedwp/latestmetadata branch.Testing Instructions for Keyboard
Not applicable; this changes release metadata only.
Screenshots or screencast
Not applicable.
Use of AI Tools
Created with assistance from OpenAI Codex; changes and test output were reviewed.