This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update codecov/codecov-action action to v4
• chore(deps): update dependabot/fetch-metadata action to v2
• chore(deps): update dependency semantic-release to v24
• fix(deps): update dependency fancy-log to v2
• fix(deps): update dependency schema-utils to v4
• Click on this checkbox to rebase all open PRs at once

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update jest monorepo to v29 (major) (@types/jest, jest, ts-jest)
• fix(deps): update dependency loader-utils to v3

Detected dependencies

github-actions

.github/workflows/ci.yml

• actions/checkout v3
• actions/setup-node v3
• codecov/codecov-action v3

.github/workflows/deps.yml

• dependabot/fetch-metadata v1

.github/workflows/publish.yml

• actions/checkout v3
• actions/setup-node v3

npm

package.json

• fancy-log ^1.3.3
• loader-utils ^2.0.0
• lodash ^4.17.21
• properties ^1.2.1
• schema-utils ^3.0.0
• @semantic-release/changelog 6.0.3
• @semantic-release/git 10.0.1
• @types/jest 27.5.2
• @types/loader-utils 2.0.6
• @types/node 20.14.9
• @types/webpack 5.28.5
• debug 4.3.5
• jest 26.6.3
• memfs 4.9.3
• memory-fs 0.5.0
• prettier 3.3.2
• rimraf 5.0.7
• semantic-release 22.0.12
• ts-jest 26.5.6
• ts-node 10.9.2
• tsconfig-paths 4.2.0
• typescript 5.5.2
• webpack 5.92.1

---

• Check this box to trigger a request for Renovate to run again on this repository

🚨 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.

---

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, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-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 📦🚀