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

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

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

♻ 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 was generated by Mend Renovate. View the repository job log.

---

Note

Low Risk
Low risk: the only change is upgrading the pnpm/action-setup GitHub Action used in example CI workflows, which may affect dependency installation behavior but does not touch product code.

Overview
Updates the example GitHub Actions workflows (example-basic-pnpm and example-start-and-pnpm-workspaces) to install pnpm via pnpm/action-setup@v6 instead of @v5, leaving the rest of the CI steps unchanged.

^{Reviewed by Cursor Bugbot for commit 5ff1e07. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cypress-app-bot]

See the guidelines for reviewing dependency updates for info on how to review dependency update PRs.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 5ff1e07. Configure here.}

[cursor]

Upgrading to action-setup v6 installs wrong pnpm version

High Severity

pnpm/action-setup@v6 has a known critical bug (upstream issues #225, #226, #227, #228) where it ignores the version: 10 parameter and installs pnpm v11 beta instead. This causes the bootstrap v11 binary to shadow the self-updated v10 binary due to a PATH priority issue. The v11 bootstrap also modifies pnpm-lock.yaml, leading to ERR_PNPM_BROKEN_LOCKFILE errors and CI failures when combined with actions/setup-node caching and --frozen-lockfile.

Additional Locations (2)

• .github/workflows/example-start-and-pnpm-workspaces.yml#L30-L33
• .github/workflows/example-start-and-pnpm-workspaces.yml#L81-L84

 

^{Reviewed by Cursor Bugbot for commit 5ff1e07. Configure here.}

[MikeMcC399]

Rejecting this PR, since the action version v6 is tied to the pnpm@11 release, which is currently in RC status.

https://github.com/pnpm/action-setup/releases currently shows v5 as latest

This should be revisited when pnpm@11 is officially released.

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