The automated release is failing 🚨
github-actions opened 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 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 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 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 2.0.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.4.2 <2.0.0 can be published from branch master.
The following commits are responsible for the invalid release:
- chore: remove yarn.lock and update broken package.json and storybook configuration (#50) (8ba689f)
- chore: Upgrade dependencies for v2 (#43) (639ef30)
- chore: create dependabot config file (#45) (9e53cc6)
- docs: Updated to reflect api changes (c2ccd62)
- docs: removed irrelevant section (b0964fa)
- chore: added meta tags for SEO (fff909b)
- fix: Bug where setState depth exceeded if user started dragging but did not move (e84614e)
- feat!: Offer simplified collapse defaults in the API (c8c01d1)
- refactor: Simply component definition and class generation (4b77e92)
- refactor: Moved Pane into component directory (c93f605)
- Create CNAME (f86344f)
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 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 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 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 2.0.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.4.2 <2.0.0 can be published from branch master.
The following commits are responsible for the invalid release:
- fix: always use arrow functions for hooks to prevent scope hoisting (8fe33bd)
- chore: remove yarn.lock and update broken package.json and storybook configuration (#50) (8ba689f)
- chore: Upgrade dependencies for v2 (#43) (639ef30)
- chore: create dependabot config file (#45) (9e53cc6)
- docs: Updated to reflect api changes (c2ccd62)
- docs: removed irrelevant section (b0964fa)
- chore: added meta tags for SEO (fff909b)
- fix: Bug where setState depth exceeded if user started dragging but did not move (e84614e)
- feat!: Offer simplified collapse defaults in the API (c8c01d1)
- refactor: Simply component definition and class generation (4b77e92)
- refactor: Moved Pane into component directory (c93f605)
- Create CNAME (f86344f)
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 📦🚀