π¨ The automated release from the 2.1.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.1.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 3.0.3
on branch 2.1.x
cannot be published as it is out of range.
Only releases within the range >=2.1.0 <2.2.0
can be merged into the maintenance branch 2.1.x
and published to the 2.1.x
distribution channel.
The branch 2.1.x
head should be reset to a previous commit so the commit with tag v3.0.3
is removed from the branch history.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π