The automated release is failing 🚨

[ioredis-robot]

🚨 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 📦🚀

[AVVS]

@luin it will close issues like that automatically on a successful release, btw

[luin]

Aha, good to know! btw, I think the semantic-release have been set up successfully. I'll merge #723 tomorrow to see whether all things work.

[AVVS]

ok, I saw there is a git tag + draft release - was this intentional for testing or do we need to fix that?

[luin]

It was an issue with tag v4.1.0 (it was attached to the wrong commit so that semantic-release can't find it). I re-published the tag again, so semantic-release works well again. Just updated the draft release to the new tag.