:rotating_light: The automated release from the release/4.x.x branch failed. :rotating_light:
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 release/4.x.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:
:rotating_light: The automated release from the
release/4.x.xbranch failed. :rotating_light: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
release/4.x.xbranch. 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
4.16.0on branchrelease/4.x.xcannot be published as it is out of range.Based on the releases published on other branches, only versions within the range
>=6.3.0can be published from branchrelease/4.x.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
release/4.x.xwith git revert or git reset.A valid branch could be
mainorrelease/4.x.x.See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot :package::rocket: