This repository has been archived by the owner on Aug 11, 2023. It is now read-only.
The automated release is failing 🚨 #2
Comments
|
🎉 This issue has been resolved in version 3.1.10 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version 3.1.10 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
🚨 The automated release from the
devbranch 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
devbranch. 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.
Version mismatch
The pom.xml version of
3.1.9-SNAPSHOTdiffers too much from last git tag version of3.1.9.Please edit the
projectentry in thepom.xmlfile to have a version number of no more than 1 patch version ahead of the git tag version of3.1.9.Good luck with your project ✨
Your semantic-release bot 📦🚀
The text was updated successfully, but these errors were encountered: