chore(deps): update pnpm/action-setup action to v6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
pnpm/action-setup	action	major	v5 → v6

---

Release Notes

pnpm/action-setup (pnpm/action-setup)

v6.0.3

Compare Source

Updated pnpm to v11.0.0-rc.5

Full Changelog: pnpm/action-setup@v6.0.2...v6.0.3

v6.0.2

Compare Source

What's Changed

• fix: pnpm self-update binary shadowed by bootstrap on PATH by @​oniani1 in #​230

New Contributors

• @​oniani1 made their first contribution in #​230

Full Changelog: pnpm/action-setup@v6.0.1...v6.0.2

v6.0.1

Compare Source

Update pnpm to v11.0.0-rc.2. pnpm-lock.yaml will not be saved with two documents unless the packageManager is set via devEngines.packageManager. Related issue: #​228

v6.0.0

Compare Source

v6

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 5am"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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

[github-actions]

📦 Bundle Stats — @sanity/cli

Compared against main (cb1e19a5)

@sanity/cli

Metric	Value	vs main (cb1e19a)
Internal (raw)	2.1 KB	-
Internal (gzip)	799 B	-
Bundled (raw)	10.94 MB	-
Bundled (gzip)	2.05 MB	-
Import time	818ms	-6ms, -0.7%

bin:sanity

Metric	Value	vs main (cb1e19a)
Internal (raw)	975 B	-
Internal (gzip)	460 B	-
Bundled (raw)	9.84 MB	-
Bundled (gzip)	1.77 MB	-
Import time	1.97s	+7ms, +0.4%

🗺️ View treemap · Artifacts

Details

• Import time regressions over 10% are flagged with ⚠️
• Sizes shown as raw / gzip 🗜️. Internal bytes = own code only. Total bytes = with all dependencies. Import time = Node.js cold-start median.

📦 Bundle Stats — @sanity/cli-core

Compared against main (cb1e19a5)

Metric	Value	vs main (cb1e19a)
Internal (raw)	93.1 KB	-
Internal (gzip)	21.9 KB	-
Bundled (raw)	21.62 MB	-
Bundled (gzip)	3.42 MB	-
Import time	784ms	+6ms, +0.8%

🗺️ View treemap · Artifacts

Details

• Import time regressions over 10% are flagged with ⚠️
• Sizes shown as raw / gzip 🗜️. Internal bytes = own code only. Total bytes = with all dependencies. Import time = Node.js cold-start median.

📦 Bundle Stats — create-sanity

Compared against main (cb1e19a5)

Metric	Value	vs main (cb1e19a)
Internal (raw)	976 B	-
Internal (gzip)	507 B	-
Bundled (raw)	50.7 KB	-
Bundled (gzip)	12.6 KB	-
Import time	❌ ChildProcess denied: node	-

Details

• Import time regressions over 10% are flagged with ⚠️
• Sizes shown as raw / gzip 🗜️. Internal bytes = own code only. Total bytes = with all dependencies. Import time = Node.js cold-start median.

[claude]

Claude finished @renovate[bot]'s task in 1m 12s —— View job

---

Review: pnpm/action-setup v5 → v6

• Gather context and understand request
• Read changed file
• Check v6 release notes for breaking changes
• Search codebase for all usages of pnpm/action-setup
• Verify compatibility and report findings

---

Summary

This upgrade is safe to merge. The change is a single-line version bump in .github/actions/setup/action.yml:22.

Findings

Single usage point: pnpm/action-setup is only referenced in .github/actions/setup/action.yml, which is a composite action consumed by 13 workflow files (test.yml, release.yml, e2e.yml, lint.yml, build.yml, depcheck.yml, and others). The centralized setup means the upgrade applies uniformly with no drift.

pnpm version pinned via packageManager: The action is used without any version in a with: block:

- name: Install pnpm
  uses: pnpm/action-setup@v6

The action resolves the pnpm version from the root package.json "packageManager": "pnpm@10.30.3" field. This pin is preserved across the v5→v6 upgrade.

v6 breaking changes — none applicable here:

• The bundled default pnpm version changed to v11.0.0-rc.2, but only applies when no packageManager field is set. This repo sets it explicitly, so pnpm 10.30.3 continues to be installed.
• The pnpm-lock.yaml two-document format behavior (v6.0.1 release note) only activates under pnpm v11 with a devEngines.packageManager field. This repo has neither, so no lock file format change is expected.

No devEngines field: The repo does not use devEngines.packageManager, which is the opt-in mechanism for the new pnpm v11 lock file behavior. Nothing to add here.

Verdict

All usages are compatible with v6. No code changes needed.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 6.x releases. But if you manually upgrade to 6.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.