Skip to content
This repository has been archived by the owner on Jun 27, 2023. It is now read-only.

The automated release is failing 🚨 #110

Closed
github-actions bot opened this issue Sep 28, 2020 · 1 comment
Closed

The automated release is failing 🚨 #110

github-actions bot opened this issue Sep 28, 2020 · 1 comment
Labels
semantic-release

Comments

@github-actions
Copy link

🚨 The automated release from the 0.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.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.5.0 on branch 0.x cannot be published as it is out of range.

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

The following commits are responsible for the invalid release:

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 0.x with git revert or git reset.

A valid branch could be next.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀
@github-actions
Copy link
Author

🚨 The automated release from the 0.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.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.5.0 on branch 0.x cannot be published as it is out of range.

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

The following commits are responsible for the invalid release:

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 0.x with git revert or git reset.

A valid branch could be next.

See the workflow configuration documentation for more details.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
semantic-release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants