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

Based on the releases published on other branches, only versions within the range >=2.0.0 <1.3.10 can be published from branch 2.x.

The following commits are responsible for the invalid release:

• ci: release on 2.x branch (991870e)
• feat!: support react 18 (b20a57d)
• fix: revert to React 17 (68d513b)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 2.x with git revert or git reset.

A valid branch could be main.

See the workflow configuration documentation for more details.

---

Good luck with your project ✨

Your semantic-release bot 📦🚀

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

---

Using a curated preset maintained by

Sanity: The Composable Content Cloud

---

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• chore(deps): update pnpm to v8.12.1

Awaiting Schedule

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

• chore(deps): lock file maintenance

Open

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

• chore(deps): update non-major (@types/react, @types/react-dom, eslint, eslint-plugin-import)
• chore(deps): update actions/checkout action to v4
• chore(deps): update actions/setup-node action to v4
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/main.yml

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

npm

package.json

• @babel/core ^7.23.6
• @babel/preset-env ^7.23.6
• @babel/preset-react ^7.23.3
• @babel/preset-typescript ^7.23.3
• @commitlint/cli ^18.4.3
• @commitlint/config-conventional ^18.4.3
• @sanity/pkg-utils ^3.3.5
• @sanity/semantic-release-preset ^4.1.6
• @sanity/ui ^1.9.3
• @sanity/ui-workshop ^2.0.3
• @svgr/core ^8.1.0
• @testing-library/jest-dom ^6.1.5
• @testing-library/react ^14.1.2
• @types/jest ^29.5.11
• @types/react ^18.2.43
• @types/react-dom ^18.2.17
• @types/styled-components ^5.1.34
• @typescript-eslint/eslint-plugin ^6.14.0
• @typescript-eslint/parser ^6.14.0
• camelcase ^8.0.0
• commitizen ^4.3.0
• cz-conventional-changelog ^3.3.0
• esbuild ^0.19.9
• esbuild-register ^3.5.0
• eslint ^8.55.0
• eslint-config-prettier ^9.1.0
• eslint-plugin-import ^2.29.0
• eslint-plugin-jsx-a11y ^6.8.0
• eslint-plugin-prettier ^5.0.1
• eslint-plugin-react ^7.33.2
• eslint-plugin-react-hooks ^4.6.0
• jest ^29.7.0
• jest-axe ^8.0.0
• jest-environment-jsdom ^29.7.0
• mkdirp ^3.0.1
• module-alias ^2.2.3
• npm-run-all ^4.1.5
• prettier ^3.1.1
• react ^18.2.0
• react-dom ^18.2.0
• react-is ^18.2.0
• rimraf ^5.0.5
• semantic-release ^22.0.12
• styled-components ^6.1.1
• typescript ^5.3.3
• react ^18
• node >=14.0.0
• pnpm 8.8.0

---

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