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-beta.1 can be published from branch main.

The following commits are responsible for the invalid release:

• feat(deps): upgrade all dependencies to latest (b440e7e)
• refactor(deps): remove direct dependency on arrify (a6fb163)
• fix(test): add @swc/helpers (0bb068f)
• build(deps-dev): add latest @types/node (7637e48)
• build(deps): deduplicate dependencies (fb9a12f)
• feat(deps): upgrade Prettier to 2.8.1 (47fdd1b)
• feat(deps): update eslint (eb20493)
• build: move shared TypeScript configuration to project root instead of extending (03565e5)
• feat(deps): upgrade commitlint (9cb5e7a)
• fix(scripts/pre-commit): don't fail when no related tests are found (9e2cb6d)
• feat(deps): upgrade @swc-node/jest and @swc/core (49abe25)
• feat(api/commit): add support for excluding directories in ls.dirs() (ff5ec7a)
• build: use Node 18 (9eeee51)
• feat(config/jest): @swc/jest → @swc-node/jest (supports tsconfig) (76c0c8a)
• fix(config/jest): add jest-environment-jsdom as a dependency (c72fdf3)
• build: use latest Node 16 (5eb2c8d)
• fix: remove skipLibCheck as it's no longer necessary (b7a1323)
• feat(config/test): use @swc/jest as default Jest transform (a8bbe7c)
• build: deduplicate lockfile (dddc727)
• ci(actions): release on Node 16 (c9c7d47)
• feat(scripts/test): upgrade Jest to 29.x (9a564ed)
• feat(scripts/ci-after-success): use Semantic Release 19 (6912bbe)
• feat(scripts/test): upgrade Jest to 28.x (48e8dfd)
• feat(config/eslint): dissallow default exports in strict configuration (ec5646f)
• fix(api/test): forward ts-jest utils from ts-jest, remove mocked (f18010a)
• build(deps): upgrade Jest to 27.4 (5f5821c)
• build: set skipLibCheck... ts-jest and jest aren't playing nicely (86dacc0)
• fix(config/jest): set ts-jest transform unconditionally (ba389a0)
• build(deps): bump json5 from 1.0.1 to 1.0.2 (5e94f75)

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