Skip to content

chore(deps): update pnpm/action-setup action to v6 #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update pnpm/action-setup action to v6 #55

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ jobs:
uses: actions/checkout@v6

- name: Install pnpm
uses: pnpm/action-setup@v5
uses: pnpm/action-setup@v6
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot Apr 13, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

pnpm/action-setup v6 release notes breaking changes

💡 Result:

pnpm/action-setup v6 was recently released (tag exists as of 2026-04-13). Official release notes are not yet detailed on the releases page, but it adds support for pnpm v11. Known issue (potentially breaking): v6 does not respect the specified 'version' input and always installs pnpm v11 (e.g., 11.0.0-beta.4-1), even when version: 10 is set. See open GitHub issue #225 created 2026-04-11. No other explicit breaking changes documented in available sources. Previous versions like v5 updated to Node.js 24 runtime. Users report pinning to specific commits as workaround.

Citations:

Do not update to pnpm/action-setup@v6 without resolving a critical known bug.

v6 has a critical issue (GitHub issue #225) where it does not respect the version input parameter and always installs pnpm v11, even when a different version is specified. This is a breaking change in behavior.

Either:

  1. Pin to a specific commit as a workaround until the bug is fixed
  2. Verify that your workflow does not depend on pnpm version specification
  3. Wait for a v6 patch release that fixes the issue
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/ci.yml at line 19, The workflow currently references the
action "uses: pnpm/action-setup@v6" which has a known bug forcing pnpm v11;
update the workflow to avoid v6 until fixed by either pinning the action to a
specific commit or tag that contains the working behavior (e.g., a commit SHA)
or revert to the last known-good release (e.g., an explicit v5.x tag) so the
`version` input is respected; locate the line containing uses:
pnpm/action-setup@v6 and replace it with a pinned commit or a stable v5 tag, or
add a comment noting why v6 is intentionally avoided until the upstream issue is
resolved.


- name: Install node
uses: actions/setup-node@v6
Expand Down