The automated release is failing 🚨
Closed this issue · 6 comments
🚨 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:
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.
No apm token specified.
An apm token must be created and set in the ATOM_ACCESS_TOKEN environment variable on your CI environment.
Please visit your account page on atom.io and to set it in the ATOM_ACCESS_TOKEN environment variable on your CI environment.
Good luck with your project ✨
Your semantic-release bot 📦🚀
@sdinesh86 Not able to fix this, because i have not enough rights.
🚨 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:
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.
No apm token specified.
An apm token must be created and set in the ATOM_ACCESS_TOKEN environment variable on your CI environment.
Please visit your account page on atom.io and to set it in the ATOM_ACCESS_TOKEN environment variable on your CI environment.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 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:
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.
No apm token specified.
An apm token must be created and set in the ATOM_ACCESS_TOKEN environment variable on your CI environment.
Please visit your account page on atom.io and to set it in the ATOM_ACCESS_TOKEN environment variable on your CI environment.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 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:
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.
No apm token specified.
An apm token must be created and set in the ATOM_ACCESS_TOKEN environment variable on your CI environment.
Please visit your account page on atom.io and to set it in the ATOM_ACCESS_TOKEN environment variable on your CI environment.
Good luck with your project ✨
Your semantic-release bot 📦🚀
It would be best to create an organization secret for ATOM_ACCESS_TOKEN. @sdinesh86 you can get the API token from https://atom.io/account