🚨 The automated release from the main
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 main
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.5.0
on branch main
cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=2.4.1 <2.5.0-pre-release.1
can be published from branch main
.
The following commits are responsible for the invalid release:
- Create npm-publish-github-packages.yml (121a67a)
- chore(release): 2.5.1 [skip ci] (f60b797)
- fix(semantic-release): npm publish (3b084da)
- chore(release): 2.5.0 [skip ci] (0247837)
- fix(semantic-release): set the channel to next (bacfa9a)
- fix(semantic-release): bring back the regex (8306882)
- chore(release): 2.5.0-pre-release.1 [skip ci] (497818b)
- fix(semantic-release): properties change (6bcca0f)
- fix(semantic-release): prerelease property add regex again (4b70903)
- chore(release): 2.5.0-pre-release.1 [skip ci] (d0b17ff)
- fix(semantic-release): prerelease property remove regex (b9c55b3)
- fix(semantic-release): prerelease property validity (ed37488)
- feat(semantic-release): add a breaking change section to the release note (85aeece)
- feat(semantic-release): try to remove pre-release from version name (23c9bec)
Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch main
with git revert or git reset.
A valid branch could be main
or pre-release
.
See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot 📦🚀