The automated release is failing 🚨 #2
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: unistack-org/protoc-gen-go-micro#2
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
🚨 The automated release from the
masterbranch 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
masterbranch. 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.
Missing
package.jsonfile.A package.json file at the root of your project is required to release on npm.
Please follow the npm guideline to create a valid
package.jsonfile.Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the
masterbranch 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
masterbranch. 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.
Missing
package.jsonfile.A package.json file at the root of your project is required to release on npm.
Please follow the npm guideline to create a valid
package.jsonfile.Good luck with your project ✨
Your semantic-release bot 📦🚀