The automated release is failing 🚨

[cheqd-bot]

🚨 The automated release from the commonjs branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

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 fix 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 commonjs branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are 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.1.0 on branch commonjs cannot be published as it is out of range.

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

The following commits are responsible for the invalid release:

• Merge main into cjs (c90f92e)
• feat: Remove file-type (feat: Remove file-type #163) (3d2e46a)

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

A valid branch could be main or commonjs.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

[cheqd-bot]

🚨 The automated release from the commonjs branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

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 fix 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 commonjs branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are 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.1.0 on branch commonjs cannot be published as it is out of range.

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

The following commits are responsible for the invalid release:

• build: Bump deps to latest where relevant (a24103f)
• build: Sync main branch changes to CommonJS (build: Sync main branch changes to CommonJS #167) (40df737)
• Merge main into cjs (c90f92e)
• feat: Remove file-type (feat: Remove file-type #163) (3d2e46a)

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

A valid branch could be main or commonjs.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀