The automated release is failing 🚨

[github-actions]

🚨 The automated release from the undefined 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 undefined 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 1.0.0 on branch next cannot be published as it is out of range.

Based on the releases published on other branches, only versions within the range >=2.0.0 can be published from branch next.

The following commits are responsible for the invalid release:

• Merge pull request ci: fix No GitHub token specified #13 from itigoore01/fix-no-github-token-specified (d6babc3)
• ci: fix No GitHub token specified (1fbad85)
• Merge pull request ci: setup semantic-release #12 from itigoore01/setup-semantic-release (81a686f)
• ci: setup semantic-release (67e0738)
• Merge pull request feat(praparat): set config with @Input #11 from itigoore01/set-config-with-input (47d1add)
• feat(praparat): set config with @input (46b7c10)
• Merge pull request merge develop #5 from itigoore01/develop (d1f89a3)
• Merge pull request Update README.md #4 from itigoore01/itigoore01-patch-1 (319a5ef)
• Update README.md (e039eaf)
• Merge pull request merge develop #3 from itigoore01/develop (dbc4dea)
• Merge branch 'master' into develop (74aa365)
• ci: update build.yml (a9bc7a5)
• Merge pull request Develop #2 from itigoore01/develop (0b30039)
• ci: rename action (53ce5df)
• docs(README): add badge (0e75e44)
• Merge pull request Update nodejs.yml #1 from itigoore01/itigoore01-patch-1 (51b55e5)
• Update nodejs.yml (a4e29ba)
• ci: set custom launcher (07d930d)
• chore: update package version (a3cd35e)
• fix(praparat): fix aot build error (5710afc)
• chore: update package version (89810fc)
• fix(praparat): jaggy occurs in chrome (237bb83)
• chore: update package version. (553531e)
• chore(praparat): fix peerDependencies (98df108)
• chore(praparat): preparing to publish npm (024bebd)
• feat(praparat): add ability to pan and zoom (a7384e0)
• initial commit (91a0237)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch next with git revert or git reset.

A valid branch could be master or next.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀