The automated release is failing 🚨
opened this issue · comments
🚨 The automated release from the 2.18.x 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 2.18.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 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.
The release 2.18.8 on branch 2.18.x cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=2.18.7 <2.18.7 can be published from branch 2.18.x.
The following commit is responsible for the invalid release:
This commit should be moved to a valid branch with git merge or git cherry-pick and removed from branch 2.18.x with git revert or git reset.
A valid branch could be 1.100.x, 1.111.x, 1.118.x, 1.131.x, 1.139.x, 1.150.x, 1.215.x, 1.223.x, 1.231.x, 1.242.x, 1.78.x, 1.85.x, 1.x, 2.10.x or main.
See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot 📦🚀