chore(deps): bump actions/setup-node from 6 to 7

[dependabot]

Bumps actions/setup-node from 6 to 7.

Release notes

Sourced from actions/setup-node's releases.

v7.0.0

What's Changed

Enhancements:

• Add cache-primary-key and cache-matched-key as outputs by @​gowridurgad in actions/setup-node#1577
• Migrate to ESM and upgrade dependencies by @​gowridurgad in actions/setup-node#1574

Bug fixes:

• Remove dummy NODE_AUTH_TOKEN export by @​gowridurgad in actions/setup-node#1558
• Only use mirrorToken in getManifest if it's provided by @​deiga in actions/setup-node#1548

Documentation updates:

• Add documentation for publishing to npm with Trusted Publisher (OIDC) by @​chiranjib-swain in actions/setup-node#1536
• docs: Update restore-only cache documentation by @​priya-kinthali in actions/setup-node#1550
• docs: Update caching recommendations to mitigate cache poisoning risks by @​chiranjib-swain in actions/setup-node#1567

Dependency update:

• Upgrade @​actions/cache to 5.1.0, log cache write denied by @​jasongin in actions/setup-node#1569

New Contributors

• @​chiranjib-swain made their first contribution in actions/setup-node#1536
• @​deiga made their first contribution in actions/setup-node#1548
• @​jasongin made their first contribution in actions/setup-node#1569

Full Changelog: actions/setup-node@v6...v7.0.0

v6.5.0

What's Changed

• Update @​actions/cache to 5.1.0 and add security overrides for undici and fast-xml-parser by @​HarithaVattikuti in actions/setup-node#1579

Full Changelog: actions/setup-node@v6.4.0...v6.5.0

v6.4.0

What's Changed

Dependency updates:

• Upgrade @​actions dependencies by @​Copilot in actions/setup-node#1525
• Update Node.js versions in versions.yml and bump package to v6.4.0 by @​priya-kinthali in actions/setup-node#1533

New Contributors

• @​Copilot made their first contribution in actions/setup-node#1525

Full Changelog: actions/setup-node@v6...v6.4.0

v6.3.0

What's Changed

Enhancements:

• Support parsing devEngines field by @​susnux in actions/setup-node#1283

... (truncated)

Commits

• 8207627 Migrate to ESM and upgrade dependencies (#1574)
• 04be95c Add cache-primary-key and cache-matched-key as outputs (#1577)
• 7c2c68d docs: Update caching recommendations to mitigate cache poisoning risks (#1567)
• 6a61c03 Merge pull request #1569 from jasongin/update-actions-cache-5.1.0
• 30eb73b Resolve high-severity audit issues
• 4e1a87a Update dist
• 360237f Strict equality
• 4f8aac5 Bump @​actions/cache to 5.1.0, log cache write denied
• f4a67bb Only use mirrorToken in getManifest if it's provided (#1548)
• 0355742 Remove dummy NODE_AUTH_TOKEN export (#1558)
• 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: 94ab4a4

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

@modelcontextprotocol/codemod

npm i https://pkg.pr.new/@modelcontextprotocol/codemod@2524

@modelcontextprotocol/core

npm i https://pkg.pr.new/@modelcontextprotocol/core@2524

@modelcontextprotocol/server

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

@modelcontextprotocol/server-legacy

npm i https://pkg.pr.new/@modelcontextprotocol/server-legacy@2524

@modelcontextprotocol/express

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

@modelcontextprotocol/fastify

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

@modelcontextprotocol/hono

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

@modelcontextprotocol/node

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

commit: 94ab4a4

[claude]

LGTM — mechanical Dependabot bump of actions/setup-node from v6 to v7.

What was reviewed

• All 12 setup-node usages across the 7 workflows are bumped consistently; grepped .github/ for stragglers — none remain.
• Checked v7's breaking changes against these workflows: the removed dummy NODE_AUTH_TOKEN export is unused here (release uses npm OIDC trusted publishing; preview publish uses pkg-pr-new), and the ESM/node24 runtime migration is transparent on ubuntu-latest runners.
• All inputs in use (node-version, cache, cache-dependency-path, registry-url) remain supported in v7.

Extended reasoning...

Overview

This is a Dependabot PR bumping actions/setup-node from v6 to v7 across all 7 workflow files (conformance.yml, deploy-docs.yml, examples.yml, main.yml, publish.yml, release.yml, update-spec-types.yml). Every one of the 12 usages in the repo is updated; no code, config, or dependency-lock changes are involved.

Security risks

Minimal. The action stays on the mutable @v7 major tag, matching the repo's existing convention for first-party actions/* actions (e.g. actions/checkout@v7 is also tag-pinned, while third-party actions are SHA-pinned). No new permissions, secrets, or token flows are introduced. The v7 release notes were checked for behavior changes relevant to these workflows: the ESM migration and node24 runtime are handled by GitHub-hosted ubuntu-latest runners, and the removal of the dummy NODE_AUTH_TOKEN export does not affect this repo — release.yml publishes via npm OIDC trusted publishing (it even installs npm@11.5.1 for that purpose) and publish.yml uses pkg-pr-new, so no workflow depends on NODE_AUTH_TOKEN being set.

Level of scrutiny

Low. This is CI tooling, not shipped SDK code — a bad bump would surface immediately as red CI on this very PR (main.yml, examples.yml, conformance.yml, and publish.yml all run on pull_request), not as a latent production issue. Per the repo's review conventions on CI diffs, I verified the claimed v7 behavior against the action's release notes rather than asserting failure modes from memory, and found nothing these workflows rely on that changed incompatibly.

Other factors

The timeline contains only the standard changeset-bot notice; no changeset is needed for a workflow-only change since no package is versioned. All with: inputs used (node-version, cache, cache-dependency-path, registry-url) remain supported in v7, and the cache behavior (pnpm + pnpm-lock.yaml) is unchanged. The bug hunting system found no issues, consistent with my own read of the diff.