You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🚨 The automated release from the master 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 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 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.
No publisher found in package.json.
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.
## [2.3.1](v2.3.0...v2.3.1) (2023-07-27)
### Bug Fixes
* move pkg-prebuilds should be a runtime dep ([58c15af](58c15af)), closes [#81](#81)
### General maintenance
* **deps-dev:** bump word-wrap from 1.2.3 to 1.2.4 ([3c743be](3c743be))
### Build and continuous integration
* build only typescript when packaging ([4acc829](4acc829))
* disable hooks in CI ([947f61b](947f61b))
* download prebuilds before install ([43c03d9](43c03d9))
* ignore workspaces on release ([164abbe](164abbe)), closes [#76](#76)
🚨 The automated release from the
master
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
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 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.
No
publisher
found inpackage.json
.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 text was updated successfully, but these errors were encountered: