Skip to content

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

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 #56

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:

What are the breaking changes in pnpm/action-setup v6 compared to v5?

💡 Result:

The primary breaking change in pnpm/action-setup v6 compared to v5 is that it defaults to installing pnpm v11, ignoring the specified 'version' input in some cases. Users requesting older versions like v10 receive pnpm 11.0.0-beta.4-1 instead. This is evidenced by an open issue reported on 2026-04-11 where specifying version: 10 installs v11 anyway. v6 appears to be a recent tag (post-v5.0.0 on 2026-03-17) adding pnpm v11 support, likely bundling or defaulting to the latest pnpm version (v11). No official release notes explicitly list breaking changes, but the issue demonstrates incompatible behavior with prior versions. Workaround: Pin to a specific commit like 2e223e0f0d2b8fd9872cbadb8b7428e5f8b5556d (# v6) as suggested in the issue comments. Other changes in recent versions (v4 to v5) include Node.js 24 runtime, but v6 specifically introduces the pnpm version issue.

Citations:

🏁 Script executed:

#!/bin/bash
# Description: Check if package.json specifies a packageManager field that pnpm/action-setup will use

# Look for packageManager field in package.json
fd -t f '^package\.json$' --exec jq -r 'select(.packageManager) | "packageManager: " + .packageManager' {} \;

Repository: nuxt-ui-templates/changelog

Length of output: 99

Revert v6 or pin to a specific commit; v6 defaults to pnpm v11 which conflicts with package.json's pnpm@10.33.0.

The upgrade to pnpm/action-setup@v6 introduces a breaking change: it defaults to installing pnpm v11 and ignores version input parameters. Your project pins pnpm@10.33.0 in package.json, so upgrading to v6 will cause the workflow to use an incompatible pnpm version. This issue is documented in pnpm/action-setup#225.

Options:

  1. Revert to v5
  2. Pin v6 to a specific commit (e.g., uses: pnpm/action-setup@2e223e0f0d2b8fd9872cbadb8b7428e5f8b5556d) as a workaround
  3. Update the project to use pnpm v11
🤖 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 CI workflow currently uses the
action identifier "uses: pnpm/action-setup@v6" which forces pnpm v11 and
conflicts with package.json's pinned pnpm@10.33.0; update the workflow to either
revert to the previous major (use pnpm/action-setup@v5) or pin the v6 action to
a known working commit (e.g., replace the v6 ref with the specific commit hash
like 2e223e0f0d2b8fd9872cbadb8b7428e5f8b5556d) so the runner installs pnpm v10,
or alternatively update package.json to target pnpm v11—pick one consistent
option and update the "uses: pnpm/action-setup@..." entry accordingly.


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