π¨ The automated release from the 1.x.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 1.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:
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 1.7.1
on branch 1.x.x
cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=1.7.0 <1.7.0
can be published from branch 1.x.x
.
The following commits are responsible for the invalid release:
- ci: π set proper depth for maintenance branch (3dc48f0)
- ci: π support building maintenance releases (db46ef1)
- docs: β¬οΈ upgrade examples (15c1a10)
- docs: π reference v2 in readme (088ba74)
- ci: β
run tests on node version 18 and 20 (f8d14eb)
- build: β¬οΈ upgrade deps (5f09c2a)
- ci: π· upgrade actions/checkout to v4 (e824da3)
- ci: π· remove dependabot in favour of snyk (29a2e5b)
Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 1.x.x
with git revert or git reset.
A valid branch could be main
.
See the workflow configuration documentation for more details.
Good luck with your project β¨
Your semantic-release bot π¦π