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

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): lock file maintenance

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency @testing-library/react to v15
• chore(deps): update dependency eslint to v9
• chore(deps): update dependency husky to v9
• chore(deps): update dependency lint-staged to v15
• chore(deps): update dependency prettier to v3
• chore(deps): update github/codeql-action action to v3
• chore(deps): update semantic-release monorepo (major) (@semantic-release/npm, semantic-release)
• chore(deps): update storybook monorepo to v8 (major) (@storybook/addon-actions, @storybook/addon-docs, @storybook/addon-essentials, @storybook/addon-interactions, @storybook/addon-links, @storybook/addon-mdx-gfm, @storybook/blocks, @storybook/cli, @storybook/manager-api, @storybook/preset-create-react-app, @storybook/react, @storybook/react-webpack5, @storybook/theming, storybook)
• chore(deps): update typescript-eslint monorepo to v7 (major) (@typescript-eslint/eslint-plugin, @typescript-eslint/parser)
• 🔐 Create all rate-limited PRs at once 🔐

Open

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

• chore(deps): update all non-major dependencies (@babel/core, @babel/eslint-parser, @babel/preset-env, @babel/preset-react, @babel/preset-typescript, @semantic-release/npm, @storybook/addon-actions, @storybook/addon-docs, @storybook/addon-essentials, @storybook/addon-interactions, @storybook/addon-links, @storybook/addon-mdx-gfm, @storybook/blocks, @storybook/cli, @storybook/manager-api, @storybook/preset-create-react-app, @storybook/react, @storybook/react-webpack5, @storybook/testing-library, @storybook/theming, @testing-library/react, @types/jest, @types/react, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, babel-loader, eslint, eslint-config-prettier, eslint-plugin-import, eslint-plugin-jsx-a11y, eslint-plugin-react, eslint-plugin-react-hooks, eslint-plugin-storybook, jest, lint-staged, node, react, react-dom, react-test-renderer, rimraf, semantic-release, storybook, ts-jest, ts-loader, ts-node, typescript, yarn)
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• chore(deps): update dependency @shopify/jest-dom-mocks to v5
• chore(deps): update dependency eslint-config-prettier to v9
• chore(deps): update dependency eslint-plugin-prettier to v5
• chore(deps): update dependency fork-ts-checker-webpack-plugin to v9
• chore(deps): update dependency gh-pages to v6
• chore(deps): update node.js to v20
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

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

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

Is your feature request related to a problem? Please describe.

const [{title, index}, error, isLoading] = useNft(assetIndex, {network: 'mainnet'})

const [{title, index}, error, isLoading] = useNftWithArc(assetIndex, {network: 'mainnet', arc: ARC.ARC_69 })