The automated release is failing 🚨 #3

New issue

Closed

opened 2024-03-01 17:48:34 +01:00 by ghost · 0 comments

ghost commented

2024-03-01 17:48:34 +01:00

(Migrated from gitlab.zweieuro.at)

🚨 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 registry https://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 📦 🚀

## :rotating_light: The automated release from the `main` branch failed. :rotating_light: 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: - [Usage documentation](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/README.md) - [Frequently Asked Questions](https://github.com/semantic-release/semantic-release/blob/master/docs/support/FAQ.md) - [Support channels](https://github.com/semantic-release/semantic-release#get-help) 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](https://github.com/semantic-release/semantic-release/issues/new)**. --- ### Invalid npm token. The [npm token](https://github.com/semantic-release/npm/blob/master/README.md#npm-registry-authentication) configured in the `NPM_TOKEN` environment variable must be a valid [token](https://docs.npmjs.com/getting-started/working_with_tokens) allowing to publish to the registry `https://registry.npmjs.org/`. If you are using Two Factor Authentication for your account, set its level to ["Authorization only"](https://docs.npmjs.com/getting-started/using-two-factor-authentication#levels-of-authentication) 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](https://github.com/semantic-release/semantic-release)** bot :package: :rocket:

zweieuro (Migrated from gitlab.zweieuro.at) closed this issue

2024-03-01 18:16:43 +01:00

Commenting is not possible because the repository is archived.