The automated release is failing 🚨
Closed this issue · 1 comments
🚨 The automated release from the master branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
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 resolve 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 master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is 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.0 on branch master cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=1.0.2 <1.1.0 can be published from branch master.
The following commits are responsible for the invalid release:
- fix: Document events sometimes not firing for
mouseup(e45687b) - fix: unnecessary div for min-width causing display issues (2a4e89e)
- feat: collapsed panes now retain minimum width and the overflow is hidden (711c78e)
- fix: Min sizes now applied correctly on resize and initial size calculation (c220695)
- fix: collapse now cascades correctly to all siblings (70b829f)
Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch master with git revert or git reset.
A valid branch could be next.
See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the master branch failed. 🚨
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
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 resolve 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 master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is 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.0 on branch master cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=1.0.2 <1.1.0 can be published from branch master.
The following commits are responsible for the invalid release:
- feat: release fixes from next (#11) (51dd338)
- fix: Document events sometimes not firing for
mouseup(e45687b) - fix: unnecessary div for min-width causing display issues (2a4e89e)
- feat: collapsed panes now retain minimum width and the overflow is hidden (711c78e)
- fix: Min sizes now applied correctly on resize and initial size calculation (c220695)
- fix: collapse now cascades correctly to all siblings (70b829f)
Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch master with git revert or git reset.
A valid branch could be next.
See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot 📦🚀