The automated release is failing 🚨 #1146
Description
🚨 The automated release from the v9 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 v9 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 9.1.0 on branch v9 cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=10.0.0 can be published from branch v9.
The following commits are responsible for the invalid release:
- feat(v9): backport openapi tooling etc. from v10 (feat(v9): backport openapi tooling etc. from v10 #1145) (14828db)
- docs: migration guide tweaks (docs: migration guide tweaks #1123) (3588c5a)
- ci: run CI on v9 branch (bd55e70)
- ci(release): don't sync changes back to next (1844bb0)
- docs: v9 doc touch-ups (docs: v9 doc touch-ups #1121) (8b09e87)
Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch v9 with git revert or git reset.
A valid branch could be main or v9.
See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot 📦🚀