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

This repository currently has no open or pending branches.

Detected dependencies

github-actions

.github/workflows/release.yml

• actions/checkout v4@b4ffde65f46336ab88eb53be808477a3936bae11
• pnpm/action-setup v2
• actions/setup-node v4
• changesets/action v1

.github/workflows/review.yml

• actions/checkout v4@b4ffde65f46336ab88eb53be808477a3936bae11
• pnpm/action-setup v2
• actions/setup-node v4

npm

package.json

• @eslint/eslintrc 3.0.2
• @tammergard/eslint-config-base 5.0.6
• @typescript-eslint/eslint-plugin 7.7.0
• @typescript-eslint/parser 7.7.0
• eslint-config-airbnb 19.0.4
• eslint-plugin-jsx-a11y 6.8.0
• eslint-plugin-react 7.34.1
• eslint-plugin-react-hooks 4.6.0
• @changesets/cli 2.27.1
• @tammergard/prettier-config 2.1.0
• prettier 3.2.5
• typescript 5.4.5
• eslint >=8.52.0
• prettier >=3.0.3

---

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

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

---

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀