chore(deps): bump pnpm/action-setup from 5.0.0 to 6.0.1

[dependabot]

Bumps pnpm/action-setup from 5.0.0 to 6.0.1.

Release notes

Sourced from pnpm/action-setup's releases.

v6.0.1

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: pnpm/action-setup#228

v6.0.0

Added support for pnpm v11.

Commits

• 078e9d4 fix: update pnpm to 11.0.0-rc.2
• 08c4be7 docs(README): update action-setup version
• 5798914 chore: update .gitignore
• ddffd66 fix: remove accidentally committed file
• b43f991 fix: update pnpm to 11.0.0-rc.0
• 3852509 README.md: bring versions up-to-date (#222)
• 6e7bdbd chore: bump bootstrap pnpm to 11.0.0-beta.4-1 and add update script
• 6b87c46 fix: Windows standalone mode — bypass broken npm shims (#217)
• 994d756 feat: read pnpm version from devEngines.packageManager (#211)
• 738f428 docs: upgrade pnpm/action-setup from v4 to v5
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0d98665

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in StackBlitz

@modelcontextprotocol/client

npm i https://pkg.pr.new/@modelcontextprotocol/client@1938

@modelcontextprotocol/server

npm i https://pkg.pr.new/@modelcontextprotocol/server@1938

@modelcontextprotocol/express

npm i https://pkg.pr.new/@modelcontextprotocol/express@1938

@modelcontextprotocol/fastify

npm i https://pkg.pr.new/@modelcontextprotocol/fastify@1938

@modelcontextprotocol/hono

npm i https://pkg.pr.new/@modelcontextprotocol/hono@1938

@modelcontextprotocol/node

npm i https://pkg.pr.new/@modelcontextprotocol/node@1938

commit: 0d98665

[claude]

LGTM — straightforward Dependabot SHA bump for pnpm/action-setup.

Extended reasoning...

Overview

Dependabot bump of pnpm/action-setup from the v5.0.0 pinned SHA to the v6.0.1 pinned SHA across all six workflow files. The diff is purely mechanical: nine identical one-line replacements of the uses: SHA + version comment, with no changes to inputs (run_install: false everywhere) or surrounding steps.

Security risks

None introduced by this diff. The action remains pinned to a full commit SHA (not a mutable tag), the SHA matches the upstream v6.0.1 release commit referenced in the PR body, and pnpm/action-setup is a well-known first-party action from the pnpm org. No new permissions, secrets, or inputs are added.

Level of scrutiny

Low. This is CI tooling only — no SDK source, types, or published artifacts are touched, and no changeset is needed. The repo pins packageManager: pnpm@10.26.1 in package.json, so the action will continue to install pnpm 10.x; the v6 changes (bootstrap pnpm v11, devEngines support, Windows shim fix) don't alter which pnpm version the workflows actually use. The PR-triggered workflows (main.yml, conformance.yml, publish.yml) will exercise the new action immediately, so any regression would surface in CI on this PR.

Other factors

No prior reviews or outstanding comments. The bug-hunting system found nothing. Per the repo's CI/Actions guidance, I verified the upstream changelog rather than speculating: the only behavioral changes are internal to the action's bootstrap and don't affect this repo's pinned pnpm version.