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

[dependabot]

Bumps pnpm/action-setup from 5.0.0 to 6.0.0.

Release notes

Sourced from pnpm/action-setup's releases.

v6.0.0

Added support for pnpm v11.

Commits

• 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
• 62bce64 fix: extract pnpm version from packageManager field instead of returning unde...
• 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: 01dacf9

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@1890

@modelcontextprotocol/server

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

@modelcontextprotocol/express

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

@modelcontextprotocol/fastify

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

@modelcontextprotocol/hono

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

@modelcontextprotocol/node

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

commit: 01dacf9

[claude]

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

Extended reasoning...

Overview

Dependabot bumps pnpm/action-setup from the v5.0.0 pinned SHA to the v6.0.0 pinned SHA across all six workflow files (conformance.yml, deploy-docs.yml, main.yml, publish.yml, release.yml, update-spec-types.yml). No other lines change; the with: run_install: false inputs are preserved everywhere.

Security risks

None introduced by this diff. The action remains pinned to a full commit SHA (not a mutable tag), and the upstream v6.0.0 release is a maintenance release adding pnpm v11 support plus a few bootstrap fixes — no new permissions, secrets, or inputs are required. The repo continues to resolve the actual pnpm version from packageManager in package.json, so the bootstrap version change inside the action does not alter what runs in CI.

Level of scrutiny

Low. This is a mechanical, Dependabot-generated version bump touching only CI workflow plumbing, not SDK source, tests, or published artifacts. Any incompatibility would surface immediately as a CI failure on this PR itself (the main.yml build/test jobs run on pull_request). No changeset is needed since nothing user-facing changes.

Other factors

No prior reviews or outstanding comments beyond the changeset-bot notice (expected for CI-only changes). All nine call sites are updated consistently, so there are no leftover references to the old SHA.