Closed github-actions[bot] closed 4 years ago
@sdinesh86 Are you sure, that you also added the API token like described here: https://github.com/atom-extensions/atom-music/pull/23#issue-418373583 ? The report: https://github.com/atom-extensions/atom-music/runs/681403577?check_suite_focus=true Says:
[7:20:15 PM] [semantic-release] › ✖ Failed step "verifyConditions" of plugin "@semantic-release/apm"
...
[7:20:18 PM] [semantic-release] › ✖ ENOAPMTOKEN No apm token specified.
An apm token (https://github.com/semantic-release/apm/blob/master/README.md#atom-authentication) must be created and set in the ATOM_ACCESS_TOKEN environment variable on your CI environment.
Please visit your account page on atom.io (https://atom.io/account) and to set it in the ATOM_ACCESS_TOKEN environment variable on your CI environment.
AggregateError:
SemanticReleaseError: No apm token specified.
...
I still have not enough permissions to set GitHub secrets like API tokens. Get more information here: https://help.github.com/en/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets
Hey I have added the secret as mentioned 2 @UziTech and regarding the persmissions I will check on it
Looks like the release is working now :+1:
Oh, yes: https://github.com/atom-extensions/atom-music/runs/682108575 Then i will close this issue. :-)
:rotating_light: The automated release from the
master
branch failed. :rotating_light: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 :package::rocket: