chore(deps): update pnpm/action-setup action to v6#282
chore(deps): update pnpm/action-setup action to v6#282renovate[bot] wants to merge 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughThe CI workflow was changed to use the 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 workflow currently uses the broken action reference
"pnpm/action-setup@v6" which ignores the version input and forces pnpm v11;
change the action to a safe release (e.g., "pnpm/action-setup@v5") or another
fixed tag, and explicitly set the "version" input (for example version: '7' or
whichever pinned pnpm you require) in the step that calls the action to ensure
the intended pnpm version is installed instead of the v6 implicit v11.
🪄 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
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Verify tag exists
curl -sSfL https://api.github.com/repos/pnpm/action-setup/tags?per_page=100 \
| jq -r '.[].name' | rg '^v6$' || {
echo "Tag v6 not found for pnpm/action-setup"
exit 1
}
# Fetch action metadata for v5 and v6 and compare core fields
curl -sSfL https://raw.githubusercontent.com/pnpm/action-setup/v5/action.yml -o /tmp/pnpm-action-v5.yml
curl -sSfL https://raw.githubusercontent.com/pnpm/action-setup/v6/action.yml -o /tmp/pnpm-action-v6.yml
echo "=== v5: inputs ==="
yq '.inputs' /tmp/pnpm-action-v5.yml
echo "=== v6: inputs ==="
yq '.inputs' /tmp/pnpm-action-v6.yml
echo "=== v5: runs ==="
yq '.runs' /tmp/pnpm-action-v5.yml
echo "=== v6: runs ==="
yq '.runs' /tmp/pnpm-action-v6.ymlRepository: nuxt-ui-templates/dashboard
Length of output: 175
🌐 Web query:
pnpm/action-setup v6 release notes changelog
💡 Result:
pnpm/action-setup v6 was released recently (tags v6 and v6.0.0 exist as of 2026-04-13). No detailed release notes or changelog are available in the releases page snippets, which primarily detail earlier versions like v5.0.0 (updated to use Node.js 24) and v4.x changes (e.g., package.yaml support, caching, .npmrc registry, Node.js 24 updates). However, v6 is actively used, as evidenced by an open GitHub issue #225 from 2026-04-11 reporting a bug: "action-setup@v6 does not take the requested pnpm version into account" — it always installs pnpm v11 (specifically 11.0.0-beta.4-1) regardless of the 'version' input (e.g., version: 10 installs v11 instead). The official releases page is at https://github.com/pnpm/action-setup/releases. Latest listed release in some pages is v5.0.0 (2026-03-17), suggesting v6 may be a recent tag without full release notes yet or a pre-release/development version. Repository README examples use up to v5. For full details, check the GitHub releases page or compare commits between v5.0.0 and v6.0.0 tags directly on GitHub.
Citations:
- 1: https://github.com/pnpm/action-setup/releases
- 2: pnpm/action-setup@fe02b34...41ff726
- 3: Bump pnpm/action-setup from 4 to 5 actions/setup-node#1513
- 4: https://github.com/pnpm/action-setup
- 5: action-setup@v6 does not take the requested pnpm version into account pnpm/action-setup#225
- 6: https://github.com/pnpm/action-setup/tags
Do not merge with pnpm/action-setup@v6 — known critical bug.
A critical bug exists in v6 (GitHub issue #225): the version input is ignored and v6 always installs pnpm v11 (11.0.0-beta.4-1), regardless of the requested version. If your workflow requires a specific pnpm version, revert to v5 or wait for v6 to be fixed. If version pinning is not required, ensure the implicit v11 installation is acceptable.
🤖 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 uses the broken
action reference "pnpm/action-setup@v6" which ignores the version input and
forces pnpm v11; change the action to a safe release (e.g.,
"pnpm/action-setup@v5") or another fixed tag, and explicitly set the "version"
input (for example version: '7' or whichever pinned pnpm you require) in the
step that calls the action to ensure the intended pnpm version is installed
instead of the v6 implicit v11.
renovate
bot
force-pushed
the
renovate/pnpm-action-setup-6.x
branch
from
f961eeb to
eac247b
Compare
This PR contains the following updates:
v5→v6Release Notes
pnpm/action-setup (pnpm/action-setup)
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.