-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm publish: Add --force-publish flag to lerna #44296
Conversation
Size Change: 0 B Total Size: 1.26 MB ℹ️ View Unchanged
|
I ended up executing https://github.com/WordPress/gutenberg/actions/runs/3089777274/jobs/4997772404 I will report back soon. |
I think I used a wrong prerelease name. Trying now with Let's see in: |
In the future, we need a better strategy when executing the first npm publishing targeting
|
What?
Add the
--force-publish
flag 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.1
dist-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