The automated release is failing 🚨

[KJDev-Bot]

🚨 The automated release from the master 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 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 1.4.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.3.1 <1.3.2 can be published from branch master.

The following commits are responsible for the invalid release:

• feat: Force release (58f3d3b)
• release 1.3.6 (release 1.3.6 #31) (5cb58c4)

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 📦🚀

[KJDev-Bot]

🚨 The automated release from the master 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 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 1.4.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.3.1 <1.3.2 can be published from branch master.

The following commits are responsible for the invalid release:

• chore(release): 1.3.7 [skip ci] (d36ffee)
• fix(dot import): Fix import XYZ from '.' (fix(dot import): Fix import XYZ from '.' #52) (b4194c0)
• chore(deps-dev): bump semantic-release from 17.0.4 to 17.0.7 (chore(deps-dev): bump semantic-release from 17.0.4 to 17.0.7 #42) (f85beae)
• chore(deps-dev): bump prettier from 2.0.4 to 2.0.5 (chore(deps-dev): bump prettier from 2.0.4 to 2.0.5 #41) (2be5ec1)
• chore(release): 1.3.6 [skip ci] (d706572)
• fix(dynamicInstantiate): works with pnpm (fix(dynamicInstantiate): works with pnpm #45) (9c3e8c9)
• chore(deps-dev): bump conventional-changelog-conventionalcommits (chore(deps-dev): bump conventional-changelog-conventionalcommits from 4.2.3 to 4.3.0 #49) (2facb00)
• chore(deps-dev): bump typescript from 3.8.3 to 3.9.2 (chore(deps-dev): bump typescript from 3.8.3 to 3.9.2 #50) (7c82cf1)
• chore(deps-dev): bump prettier from 2.0.2 to 2.0.4 (chore(deps-dev): bump prettier from 2.0.2 to 2.0.4 #33) (f42a03a)
• chore(deps-dev): bump @types/node from 13.11.0 to 13.11.1 (chore(deps-dev): bump @types/node from 13.11.0 to 13.11.1 #35) (eed70d4)
• chore(release): 1.3.5 [skip ci] (dd5db51)
• fix(resolve): Don't run findFiles if we can already see an extension. (a00c446)
• chore(release): 1.3.4 [skip ci] (5ce5527)
• fix(findFiles): Fix the discovery of files when a directory of partial name match occurs (2e5d8ed)
• tests(Similar Folder): Add a test for similar folder names when searching for a file (should fail currently) (d7d4462)
• chore(deps-dev): bump @types/node from 13.9.8 to 13.11.0 (chore(deps-dev): bump @types/node from 13.9.8 to 13.11.0 #30) (4c66dfc)
• chore(deps-dev): bump @types/node from 13.9.5 to 13.9.8 (chore(deps-dev): bump @types/node from 13.9.5 to 13.9.8 #29) (dd543bd)
• chore(release): 1.3.3 [skip ci] (9ee0651)
• fix: Readd JS_EXTS to findFIles to allow for post build JS support (c72ee53)
• chore(release): 1.3.2 [skip ci] (0736915)
• refactor: Remove Node 13.7/13.8 from supported versions (92499c2)
• fix(Resovler): Refactor resolver and module loader to prevent loading of URLs and already discovered javascript files (fix(Resovler): Refactor resolver and module loader to prevent loading… #28) (cda330e)
• chore(branches): Setup Next branch (74df98a)
• Revert "release 1.3.6 (release 1.3.6 #31)" (db72a3f)
• feat: Force release (58f3d3b)
• release 1.3.6 (release 1.3.6 #31) (5cb58c4)

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 📦🚀