The automated release is failing 🚨
opened this issue · comments
🚨 The automated release from the 2.25.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.25.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.26.0 on branch 2.25.x cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=2.25.0 <2.26.0 can be published from branch 2.25.x.
The following commits are responsible for the invalid release:
- feat: updating tracked LMS release version [skip ci] (7a29e3b)
- fix: cert: Updating Translations 2207 27/06/2022 (#2581) (7855212)
Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 2.25.x with git revert or git reset.
A valid branch could be 1.x or main.
See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot 📦🚀