π¨ 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 2.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 >=2.0.4 <2.0.5
can be published from branch master
.
The following commits are responsible for the invalid release:
- fix: style and default value fix (6046c28)
- fix: select component default value fix (6f01d9c)
- fix: month Year Dropdown (51b2124)
- feat(datepicker): adding Datepicker component (2596656)
- docs(readme): changed docs build (6dd1010)
- docs(readme): changed docs (d269103)
- docs(readme files, icongallery): fixed documentation for All components and IconGallery style change (cc8c7eb)
- docs(icon): adds listing of icons in docs (87a1221)
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 π¦π