Skip to content

Bump pnpm/action-setup from 5.0.0 to 6.0.1#14

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

Bump pnpm/action-setup from 5.0.0 to 6.0.1#14
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/github_actions/pnpm/action-setup-6.0.1

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Apr 20, 2026

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 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.1.
- [Release notes](https://github.com/pnpm/action-setup/releases)
- [Commits](pnpm/action-setup@fc06bc1...078e9d4)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Apr 20, 2026

Labels

The following labels could not be found: ci, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Apr 20, 2026

Greptile Summary

This is a routine Dependabot bump of pnpm/action-setup from v5.0.0 to v6.0.1 across both CI and release workflow files (5 occurrences total). The change is straightforward and low-risk.

Key points:

  • All references remain pinned to a specific commit SHA (078e9d416474b29c0c387560859308974f7e9c53) — a good supply-chain security practice that is preserved.
  • pnpm/action-setup v6 adds pnpm v11 support and reads the version from devEngines.packageManager if present. Since the project uses \"packageManager\": \"pnpm@9.15.0\" in package.json (not devEngines.packageManager), the action will continue to install pnpm 9.15.0 — no behavior change is expected.
  • The old YAML comments read # v4.4.0, but Dependabot correctly identified the locked commit as v5.0.0, meaning those inline comments were already stale before this PR. The new comments correctly reflect # v6.0.1.

Confidence Score: 5/5

Safe to merge — mechanical version bump with no behavioral impact on this project.

All changes are commit-pinned action references updated by Dependabot. The project's packageManager field resolves to pnpm 9.15.0, which is unaffected by v6's new pnpm v11 support. No logic or configuration changes were made.

No files require special attention.

Important Files Changed

Filename Overview
.github/workflows/ci.yml Updates pnpm/action-setup from v5.0.0 (pinned commit, previously mis-commented as v4.4.0) to v6.0.1 across all 4 jobs; commit-pinned references are preserved.
.github/workflows/release.yml Updates the single pnpm/action-setup reference in the release job from v5.0.0 to v6.0.1; no other changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["pnpm/action-setup@v6.0.1\n(commit 078e9d4)"] --> B{packageManager\nfield present?}
    B -- "Yes — pnpm@9.15.0\n(standard field)" --> C["Install pnpm 9.15.0\n(unchanged behavior)"]
    B -- "Yes — via devEngines\n(not used here)" --> D["Install version from\ndevEngines.packageManager"]
    C --> E["pnpm install --frozen-lockfile\n(ci.yml & release.yml)"]
    D --> E
Loading

Reviews (1): Last reviewed commit: "Bump pnpm/action-setup from 5.0.0 to 6.0..." | Re-trigger Greptile

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants