-
Notifications
You must be signed in to change notification settings - Fork 5
Description
🚨 The automated release from the 1.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 1.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 1.1.1 on branch 1.1.x cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=1.1.0 <1.1.1 can be published from branch 1.1.x.
The following commits are responsible for the invalid release:
- Merge branch '1.1.2' into 1.1.x (0dbd3d7)
- Revert "ci(release): fixes branch pattern" (Revert "ci(release): fixes branch pattern" #45) (90a0968)
- ci(release): fixes branch pattern (ci(release): fixes branch pattern #42) (8429a83)
- Merge branch '1.x' into 1.1.x (b0dab46)
- Revert "ci(release): fixes the branch pattern" (Revert "ci(release): fixes the branch pattern" #41) (0d656f5)
- ci(release): fixes the branch pattern (ci(release): fixes the branch pattern #40) (535d82e)
- ci(release): fixes branch pattern (ci(release): fixes branch pattern #38) (7265fe5)
- ci(release): hopefully fixes the branch pattern for good (ci(release): hopefully fixes the branch pattern for good #36) (f8bb085)
- ci(release): fixes the branch matching pattern (ci(release): fixes the branch matching pattern #35) (33e6258)
- ci(release): updates the release script to be accurate for v1.1 (ci(release): updates the release script to be accurate for v1.1 #33) (73723ab)
- fix(types): updates type resolution in package.json (fix(types): updates type resolution in package.json #32) (7531341)
- fix(build): corrects the output of the build process (fix(build): corrects the output of the build process #28) (fix(build): corrects the output of the build process (#28) #29) (4c517d6)
Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 1.1.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 📦🚀