You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to semantic-release/github#895, I want to investigate if there's any possible way to verify that the npm token has permission to publish the package in the verify step. Right now if publish fails, semantic-release has already pushed a git tag, and we have to manually delete the git tag (from GitHub etc) before rerunning semantic-release.
The text was updated successfully, but these errors were encountered:
Similar to semantic-release/github#895, I want to investigate if there's any possible way to verify that the npm token has permission to publish the package in the
verify
step. Right now if publish fails,semantic-release
has already pushed a git tag, and we have to manually delete the git tag (from GitHub etc) before rerunningsemantic-release
.The text was updated successfully, but these errors were encountered: