🚨 The automated release from the 2.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 2.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.5.11 on branch 2.x cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=2.0.0 <1.5.11 can be published from branch 2.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 2.x with git revert or git reset.
A valid branch could be 1.x or master.
See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot 📦🚀
🚨 The automated release from the
2.xbranch 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
2.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
1.5.11on branch2.xcannot be published as it is out of range.Based on the releases published on other branches, only versions within the range
>=2.0.0 <1.5.11can be published from branch2.x.The following commits are responsible for the invalid release:
z-indexfor all descendants (12ce340)content-wrapperdiv element, as it wasn't needed - Added namespace constant for dynamic selectors names - Refactored selectors and changed to BEM naming, for improved isolation - Tests now using the (exported) namespace - TBD: use dynamic prefix imported from a centralized place (3d596be)2.x(0f8dad5).scrollbar-trackbecause the previous commit was wrong due to my misunderstanding of custom usage scenario (82bc4dd)@babel/eslint-parserin lock file, to match thepackage.jsonfile (69af63c)clientHeight&clientWidthas they might also change (324fa64)VerticalScrollbar&HorizontalScrollbarcomponents can be used manually which in in such case, requires the styles to be applied for the.scrollbarselector and not only to the internal.scrollbar-track(e0cd678)OmitObject method so the filtering process will happen inside thereduce(ead4fc8)@babel/eslint-parserversion (2cc1244)useMemo()#56) - Use an internal ref to eliminate the need for useMemo() (64afb31)useMemo()#56) - Use an internal ref to eliminate the need for useMemo() (3ca06b0)Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch
2.xwith git revert or git reset.A valid branch could be
1.xormaster.See the workflow configuration documentation for more details.
Good luck with your project ✨
Your semantic-release bot 📦🚀