npm publish: Add --force-publish flag to lerna#44296
Closed
ockham wants to merge 1 commit into
Closed
Conversation
ockham
added
[Type] Build Tooling
|
Size Change: 0 B Total Size: 1.26 MB ℹ️ View Unchanged
|
Member
|
I ended up executing https://github.com/WordPress/gutenberg/actions/runs/3089777274/jobs/4997772404 I will report back soon. |
Member
|
I think I used a wrong prerelease name. Trying now with Let's see in: |
Member
|
In the future, we need a better strategy when executing the first npm publishing targeting
|
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
2 participants
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?
Add the
--force-publishflag to lerna when invoked for releasing npm packages.Why?
There's been a problem when publishing npm packages for WP 6.1. It appears that some npm packages didn't get the required
wp-6.1dist-tag.How?
We'll attempt to fix that by re-publishing; however, since there haven't been any changes to some of them, we'll need to force publishing.
Once that's done, we'll revert this PR.
Testing Instructions
N/A