Skip to content

chore(deps): bump pnpm/action-setup from 5.0.0 to 6.0.5#2016

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/github_actions/pnpm/action-setup-6.0.5
Open

chore(deps): bump pnpm/action-setup from 5.0.0 to 6.0.5#2016
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/github_actions/pnpm/action-setup-6.0.5

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 4, 2026

Bumps pnpm/action-setup from 5.0.0 to 6.0.5.

Release notes

Sourced from pnpm/action-setup's releases.

v6.0.5

What's Changed

Full Changelog: pnpm/action-setup@v6.0.4...v6.0.5

v6.0.4

What's Changed

New Contributors

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

v6.0.3

Updated pnpm to v11.0.0-rc.5

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

v6.0.2

What's Changed

New Contributors

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

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
  • 8912a91 fix: append (not prepend) action node dir to PATH for npm bootstrap (#241)
  • 26f6d4f fix: use npm co-located with the action node binary (#239)
  • 903f9c1 fix: update pnpm to 11.0.0-rc.5
  • bdf0af2 test: add strict version-match jobs to reproduce #225 / #227
  • 71c9247 fix: pnpm self-update binary shadowed by bootstrap on PATH (#230)
  • 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
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [pnpm/action-setup](https://github.com/pnpm/action-setup) from 5.0.0 to 6.0.5.
- [Release notes](https://github.com/pnpm/action-setup/releases)
- [Commits](pnpm/action-setup@fc06bc1...8912a91)

---
updated-dependencies:
- dependency-name: pnpm/action-setup
  dependency-version: 6.0.5
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels May 4, 2026
@dependabot dependabot Bot requested a review from a team as a code owner May 4, 2026 23:02
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels May 4, 2026
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 4, 2026

⚠️ No Changeset found

Latest commit: ad18186

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
Copy link
Copy Markdown

pkg-pr-new Bot commented May 4, 2026

Open in StackBlitz

@modelcontextprotocol/client

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

@modelcontextprotocol/server

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

@modelcontextprotocol/express

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

@modelcontextprotocol/fastify

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

@modelcontextprotocol/hono

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

@modelcontextprotocol/node

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

commit: ad18186

Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM — mechanical SHA-pinned action bump across all workflows.

Extended reasoning...

Overview

Dependabot bumps pnpm/action-setup from fc06bc1 (v5.0.0) to 8912a91 (v6.0.5) across all six workflow files (9 call sites). The diff is a pure commit-SHA swap on the uses: line; no inputs, steps, or permissions are changed. The upstream changelog is bootstrap/PATH fixes plus support for pnpm v11 — the action still reads the target pnpm version from packageManager in package.json, which here is pnpm@10.26.1 and remains supported. The run_install: false input is unchanged and still valid in v6.

Security risks

None introduced by this diff. The action remains pinned to a full 40-char commit SHA (not a mutable tag), which is the recommended supply-chain practice. No new permissions are requested and no secrets are touched.

Level of scrutiny

Low. This is a routine, mechanical dependency bump confined to CI tooling — it does not touch SDK source, public API, or published artifacts. Any regression would surface immediately as a failed pnpm install step in the PR's own CI checks (the main.yml and conformance.yml workflows run on pull_request).

Other factors

Grep confirms no stale references to the old SHA remain anywhere in the repo, so the migration is complete (per the "Completeness" recurring catch). No changeset is needed since this is CI-only and ships nothing to consumers. No prior reviewer comments to address.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants