chore(deps): update dependency @sanity/client to v7 - abandoned

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@sanity/client (source)	6.29.1 -> 7.0.0

---

Release Notes

sanity-io/client (@​sanity/client)

v7.0.0

Compare Source

⚠ BREAKING CHANGES

• Dropping support for Node.js < v20 as Node.js v18 is EOL as of 2025-04-30

Bug Fixes

• drop support for node < v20 (#​1060) (23e4082)

---

Configuration

📅 Schedule: Branch creation - On day 1 of the month, every 3 months ( * * 1 */3 * ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @sanity/[email protected]
npm error Found: @sanity/[email protected]
npm error node_modules/@sanity/client
npm error   @sanity/client@"7.0.0" from the root project
npm error   peer @sanity/client@"^7.0.0" from @sanity/[email protected]
npm error   node_modules/@sanity/presentation-comlink
npm error     @sanity/presentation-comlink@"^1.0.18" from @sanity/[email protected]
npm error     node_modules/@sanity/next-loader
npm error       @sanity/next-loader@"^1.5.0" from [email protected]
npm error       node_modules/next-sanity
npm error         next-sanity@"9.10.2" from the root project
npm error     @sanity/presentation-comlink@"^1.0.16" from @sanity/[email protected]
npm error     node_modules/@sanity/preview-kit
npm error       @sanity/preview-kit@"^6.0.8" from [email protected]
npm error       node_modules/next-sanity
npm error         next-sanity@"9.10.2" from the root project
npm error     2 more (@sanity/visual-editing, sanity)
npm error   6 more (@sanity/visual-editing-types, @sanity/preview-kit, ...)
npm error
npm error Could not resolve dependency:
npm error peerOptional @sanity/client@"^6.29.0" from @sanity/[email protected]
npm error node_modules/@sanity/visual-editing
npm error   @sanity/visual-editing@"2.13.18" from the root project
npm error   @sanity/visual-editing@"^2.13.18" from [email protected]
npm error   node_modules/next-sanity
npm error     next-sanity@"9.10.2" from the root project
npm error
npm error Conflicting peer dependency: @sanity/[email protected]
npm error node_modules/@sanity/client
npm error   peerOptional @sanity/client@"^6.29.0" from @sanity/[email protected]
npm error   node_modules/@sanity/visual-editing
npm error     @sanity/visual-editing@"2.13.18" from the root project
npm error     @sanity/visual-editing@"^2.13.18" from [email protected]
npm error     node_modules/next-sanity
npm error       next-sanity@"9.10.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-04-30T21_13_38_244Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-04-30T21_13_38_244Z-debug-0.log

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
nextjs-blog-cms-sanity-v3	❌ Failed (Inspect)			Apr 30, 2025 9:21pm

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.