The automated release is failing 🚨

[github-actions]

🚨 The automated release from the 2.x 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 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 is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

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 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.1 <2.0.1 can be published from branch 2.x.

The following commits are responsible for the invalid release:

• ci: fix semantic-release (a188316)
• feat: accept dragEnabled as function (feat: accept function as dragEnabled prop #200) (2d2b935)
• chore(deps): upgrade lodash (chore(deps): upgrade lodash #199) (8af7531)
• chore: configure maintenance releases (chore: configure maintenance releases #197) (4934053)

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 master, next or next-major.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀