chore(deps): update pnpm/action-setup action to v6#56
chore(deps): update pnpm/action-setup action to v6#56renovate[bot] wants to merge 1 commit intomainfrom
Conversation
📝 WalkthroughWalkthroughThe CI workflow was updated to use Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related issues
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/ci.yml:
- 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.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
|
|
||
| - name: Install pnpm | ||
| uses: pnpm/action-setup@v5 | ||
| uses: pnpm/action-setup@v6 |
There was a problem hiding this comment.
🧩 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:
- 1: action-setup@v6 does not take the requested pnpm version into account pnpm/action-setup#225
- 2: https://github.com/pnpm/action-setup/tags
- 3: https://github.com/pnpm/action-setup/releases
- 4: https://github.com/pnpm/action-setup
🏁 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:
- Revert to v5
- Pin v6 to a specific commit (e.g.,
uses: pnpm/action-setup@2e223e0f0d2b8fd9872cbadb8b7428e5f8b5556d) as a workaround - 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.
renovate
Bot
force-pushed
the
renovate/pnpm-action-setup-6.x
branch
from
ee897fd to
ef94059
Compare
renovate
Bot
force-pushed
the
renovate/pnpm-action-setup-6.x
branch
from
ef94059 to
0597df6
Compare
This PR contains the following updates:
v5→v6Release Notes
pnpm/action-setup (pnpm/action-setup)
v6.0.5Compare Source
What's Changed
Full Changelog: pnpm/action-setup@v6.0.4...v6.0.5
v6.0.4Compare Source
What's Changed
New Contributors
Full Changelog: pnpm/action-setup@v6.0.3...v6.0.4
v6.0.3Compare Source
Updated pnpm to v11.0.0-rc.5
Full Changelog: pnpm/action-setup@v6.0.2...v6.0.3
v6.0.2Compare Source
What's Changed
New Contributors
Full Changelog: pnpm/action-setup@v6.0.1...v6.0.2
v6.0.1Compare Source
Update pnpm to v11.0.0-rc.2.
pnpm-lock.yamlwill not be saved with two documents unless thepackageManageris set viadevEngines.packageManager. Related issue: #228v6.0.0Compare Source
v6Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.