Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The automated release is failing 🚨 #5

Open
github-actions bot opened this issue Dec 22, 2021 · 1 comment
Open

The automated release is failing 🚨 #5

github-actions bot opened this issue Dec 22, 2021 · 1 comment

Comments

@github-actions
Copy link

🚨 The automated release from the 0.5.x branch 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 0.5.x 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.


The release 0.6.0 on branch 0.5.x cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=0.5.2 <0.6.0 can be published from branch 0.5.x.

The following commit is responsible for the invalid release:

  • feat: just test feat in minor branch (d905bcf)

This commit should be moved to a valid branch with git merge or git cherry-pick and removed from branch 0.5.x with git revert or git reset.

A valid branch could be main.

See the workflow configuration documentation for more details.


Good luck with your project ✨

Your semantic-release bot 📦🚀

@dajay
Copy link
Owner

dajay commented Dec 28, 2021

🚨 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.


Version mismatch

The pom.xml version of 1.1.8-SNAPSHOT differs too much from last git tag version of 0.6.0.

Please edit the project entry in the pom.xml file to have a version number of no more than 1 patch version ahead of the git tag version of 0.6.0.


Good luck with your project ✨

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant