-
Notifications
You must be signed in to change notification settings - Fork 5
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
The automated release is failing 🚨 #1043
Comments
🚨 The automated release from the
|
1 similar comment
🚨 The automated release from the
|
Wh... is NPM down? Can't seem to authenticate with it at the moment... |
RIGHT nevermind I can't log into the site with Firefox, I remember now... |
🚨 The automated release from the
|
24 similar comments
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
29 similar comments
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
|
🚨 The automated release from the
main
branch failed. 🚨I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the
main
branch. You can also manually restart the failed CI job that runs semantic-release.If you are not sure how to resolve this, here are some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
Invalid npm token.
The npm token configured in the
NPM_TOKEN
environment variable must be a valid token allowing to publish to the registryhttps://registry.npmjs.org/
.If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the
NPM_TOKEN
environment variable in your CI with the exact value of the npm token.Invalid npm token.
The npm token configured in the
NPM_TOKEN
environment variable must be a valid token allowing to publish to the registryhttps://registry.npmjs.org/
.If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the
NPM_TOKEN
environment variable in your CI with the exact value of the npm token.Invalid npm token.
The npm token configured in the
NPM_TOKEN
environment variable must be a valid token allowing to publish to the registryhttps://registry.npmjs.org/
.If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the
NPM_TOKEN
environment variable in your CI with the exact value of the npm token.Invalid npm token.
The npm token configured in the
NPM_TOKEN
environment variable must be a valid token allowing to publish to the registryhttps://registry.npmjs.org/
.If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the
NPM_TOKEN
environment variable in your CI with the exact value of the npm token.Invalid npm token.
The npm token configured in the
NPM_TOKEN
environment variable must be a valid token allowing to publish to the registryhttps://registry.npmjs.org/
.If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the
NPM_TOKEN
environment variable in your CI with the exact value of the npm token.Invalid npm token.
The npm token configured in the
NPM_TOKEN
environment variable must be a valid token allowing to publish to the registryhttps://registry.npmjs.org/
.If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the
NPM_TOKEN
environment variable in your CI with the exact value of the npm token.Good luck with your project ✨
Your semantic-release bot 📦🚀
The text was updated successfully, but these errors were encountered: