-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
After failed publish due to unauthorized credentials, lerna claims "no updated packages to publish" #1045
Comments
If you know what packages didn't publish successfully, you can However, the larger issue is that the commits and tags etc should be rolled back in the event a publish command fails. |
Yeah, that was an option, but a coworker recommended resetting the git commit and deleting the latest tag, which worked nicely. |
Sure, that works too. Not always possible on public repositories, though. I would like to figure out ways to mitigate this before it happens, though. |
There also can be a commit in master that will also broke publishing process. I've met this situation like 3 or 4 times on our local 2 days coding session. Would be great to have some way to rollback or lock master branch from merging at the publishing period. |
Me too; I can manually clean up when it happens, but I'd prefer preventing it or being able to roll back with a command. |
Just ran into this too and would love for failed publishes to clean themselves up (delete the tag and revert the commit). Next best option would be a lerna command to do both. |
As number of packages grows, it gets more unwieldy to do manually. It's clear how to make a cleanup command, perhaps not so clear yet how to prevent it. At the moment I'm feeling like this merits an interim solution. |
@morewry I'm finally making progress on #1091 (and many, many more issues around npm registry + credential validation) here: https://github.com/lerna/lerna/compare/one-time-password-to-rule-them-all |
Awesome! #1091 is the reason I had to do it today, lol. |
I have enabled 2FA for |
This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Expected Behavior
lerna publish
should publish updated packages after failing to publish due to invalidCurrent Behavior
lerna publish outputs "no updated packages to publish"
lerna.json
lerna-debug.log
Context
Trying to update a bunch of packages.
Your Environment
The text was updated successfully, but these errors were encountered: