Skip to content
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.

Sign up for GitHub

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

Jump to bottom

The automated release is failing 🚨 #176

Open
hongaar opened this issue Jan 22, 2024 · 37 comments
Open

The automated release is failing 🚨 #176

hongaar opened this issue Jan 22, 2024 · 37 comments
Labels
semantic-release

Comments

@hongaar
Copy link
Owner

hongaar commented Jan 22, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀
@hongaar
Copy link
Owner Author

hongaar commented Jan 22, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

28 similar comments
@hongaar
Copy link
Owner Author

hongaar commented Jan 29, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Jan 29, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Jan 29, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Feb 5, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Feb 5, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Feb 5, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Feb 5, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Feb 5, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Feb 5, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Feb 12, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Feb 19, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Feb 19, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Feb 26, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Feb 26, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Feb 26, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Mar 4, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Mar 4, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Mar 11, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Mar 11, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Mar 11, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Mar 18, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Mar 25, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Mar 25, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Mar 25, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Apr 1, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Apr 8, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Apr 15, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Apr 15, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Apr 15, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

7 similar comments
@hongaar
Copy link
Owner Author

hongaar commented Apr 15, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Apr 22, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented Apr 29, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented May 6, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented May 13, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented May 13, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

@hongaar
Copy link
Owner Author

hongaar commented May 20, 2024

🚨 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 access token.

The NPM access token configured must be a valid access token allowing to publish to the registry "https://registry.npmjs.org".

Please refer to the npm registry authentication section of the README to learn how to configure the NPM registry access token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
semantic-release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hongaar