The automated release is failing 🚨

[github-actions]

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

Based on the releases published on other branches, only versions within the range >=6.92.0 <7.0.0-next.1 can be published from branch main.

The following commits are responsible for the invalid release:

• Merge pull request 🔖 Beta #782 from hoverinc/beta (ad6df53)
• Merge branch 'main' into beta (17ce718)
• feat(deps): upgrade all dependencies to latest (82d6fdd)
• refactor(deps): remove direct dependency on arrify (6bb9799)
• fix(test): add @swc/helpers (446707a)
• build(deps): bump json5 from 1.0.1 to 1.0.2 (5e94f75)
• build(deps-dev): add latest @types/node (c58825a)
• build(deps): deduplicate dependencies (5e14147)
• feat(deps): upgrade Prettier to 2.8.1 (3f56e8a)
• feat(deps): update eslint (17e60e0)
• build: move shared TypeScript configuration to project root instead of extending (8ba039c)
• feat(deps): upgrade commitlint (fcb02d2)
• fix(scripts/pre-commit): don't fail when no related tests are found (12c307b)
• feat(deps): upgrade @swc-node/jest and @swc/core (a5d4057)
• feat(api/commit): add support for excluding directories in ls.dirs() (8648a39)
• build: use Node 18 (9997545)
• feat(config/jest): @swc/jest → @swc-node/jest (supports tsconfig) (7627f06)
• fix(config/jest): add jest-environment-jsdom as a dependency (c81409e)
• build: use latest Node 16 (be54bb5)
• fix: remove skipLibCheck as it's no longer necessary (d2e9873)
• feat(config/test): use @swc/jest as default Jest transform (bf86aac)
• build: deduplicate lockfile (639f4fa)
• ci(actions): release on Node 16 (67d8f1e)
• feat(scripts/test): upgrade Jest to 29.x (01dadec)
• feat(scripts/ci-after-success): use Semantic Release 19 (9e87c79)
• feat(scripts/test): upgrade Jest to 28.x (0c67b80)
• feat(config/eslint): dissallow default exports in strict configuration (1fbee33)
• fix(api/test): forward ts-jest utils from ts-jest, remove mocked (56756f9)
• build(deps): upgrade Jest to 27.4 (edea114)
• build: set skipLibCheck... ts-jest and jest aren't playing nicely (cca61de)
• fix(config/jest): set ts-jest transform unconditionally (03df4f9)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch main 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 📦🚀

[jrolfs]

🚨 The automated release from the main 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 main 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.

---

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org.

If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀