The automated release is failing 🚨
opened this issue · comments
🚨 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 vsce token. Additional information:
Error: Command failed with exit code 1: vsce verify-pat
ERROR Can not read the publisher's name. Either supply it as an argument or run vsce from the extension folder. Additional information:
Error: @types/vscode ^1.64.0 greater than engines.vscode ^1.59.0. Consider upgrade engines.vscode or use an older @types/vscode version
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 📦🚀
🚨 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 vsce token. Additional information:
Error: Command failed with exit code 1: vsce verify-pat
ERROR Can not read the publisher's name. Either supply it as an argument or run vsce from the extension folder. Additional information:
Error: @types/vscode ^1.64.0 greater than engines.vscode ^1.59.0. Consider upgrade engines.vscode or use an older @types/vscode version
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 📦🚀
🚨 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 vsce token. Additional information:
Error: Command failed with exit code 1: vsce verify-pat
ERROR The Personal Access Token verification has failed. Additional information:
Error: Failed request: (401)
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 📦🚀
🚨 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 vsce token. Additional information:
Error: Command failed with exit code 1: vsce verify-pat
ERROR The Personal Access Token verification has failed. Additional information:
Error: Failed request: (401)
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 📦🚀
🚨 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 vsce token. Additional information:
Error: Command failed with exit code 1: vsce verify-pat
ERROR The Personal Access Token verification has failed. Additional information:
Error: Failed request: (401)
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 📦🚀