Closed robertrossmann closed 5 years ago
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.
tarballDir
option.The tarballDir option option, if defined, must be a String
.
Your configuration for the tarballDir
option is false
.
Good luck with your project ✨
Your semantic-release bot :package::rocket:
: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 vsce personal access token specified. (set env "VSCE_TOKEN")
Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the
semantic-release-vsce
plugin to add more helpful information.Good luck with your project ✨
Your semantic-release bot :package::rocket: