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 3.3.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.2.1 <3.2.2 can be published from branch master.

The following commits are responsible for the invalid release:

• chore(release): 3.3.0 [skip ci] (03794ee)
• test: fix unknown default handler (f9b902a)
• ci: thanks to Circle CI sanctions! (8f07454)
• fix: handle.others instead of handle.default (ffe271b)
• refactor: create-handler-map.ts (29c25ab)
• fix: more explicit typing to avoid TS4025 (25b78c3)
• feat: default handler in createReducer (0b3dfcf)
• chore(dependencies): update lockfiles (53ab4d9)
• test: remove redundant tests (bc64042)
• chore(deps): bump acorn from 5.7.3 to 5.7.4 in /examples/tasks (75634ec)
• chore(release): 3.2.2 [skip ci] (22a27bc)
• fix: type for plain action creator. (#144) (f228b81)
• docs: remove excess highlight (9925130)
• Merge pull request #142 from thebrodmann/next (d209aba)
• Merge pull request #137 from thebrodmann/next (8fe1758)

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 2.1.x or next.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot :package::rocket: