The automated release is failing 🚨

[the-dr-lazy]

:rotating_light: The automated release from the master branch failed. :rotating_light:

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:

• 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 4.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 >=3.3.1 <4.0.0 can be published from branch master.

The following commits are responsible for the invalid release:

• chore: trigger release (b8e70f3)
• chore(release): 4.0.0 [skip ci] (62dacc3)
• feat: remove configureStore function and dependency to @reduxjs/toolkit (37995dd)
• style: change prettier config (6a5f95b)
• ci: respect to [skip ci] commit message (d371351)

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 :package::rocket: