The automated release is failing 🚨

[austince]

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

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 resolve 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 master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

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, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-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 📦🚀

[austince]

@keithamus what type of token is f674......69f0? semantic-release should now support NPM automation tokens, if you're able to make of one those.

[keithamus]

That token is an automation token.

[austince]

Hmm, if I could go back 2 years and tell myself not to recommend this... I guess I'll look into what else could be misconfigured.

[austince]

Any chance you'd be willing to run the release script locally with that token to see if that reproduces the error? / has the npm package settings been updated to allow automation tokens to publish?

[austince]

@keithamus I can't see the settings for chai-http, but could you double-check what they look like if you get a chance?

[keithamus]

They match the settings in your screenshot.

[austince]

Have you published anything else with an automation token with a package having these settings?

[keithamus]

I've rolled the token. The new one is ff9b......76c4. Double checked the user can publish to the package. I'm on mobile for the weekend so can't update the yml, but if you could please update the comment for it and I can approve from mobile.

Grasping at straws but I've no idea what is really going wrong here 🤷‍♂️

[austince]

Yeah I'm very confused as well, I'll update the yml and try it again. If not will raise some issues and see if semantic-release knows what's up.