chore(deps): update pnpm/action-setup action to v6#55
chore(deps): update pnpm/action-setup action to v6#55renovate[bot] wants to merge 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughUpdated the CI workflow's pnpm installation action from version 5 to version 6 in the GitHub Actions configuration. No other workflow logic, steps, or application code were modified in this change. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 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 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.
🪄 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:
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:
- 1: https://github.com/pnpm/action-setup/releases
- 2: action-setup@v6 does not take the requested pnpm version into account pnpm/action-setup#225
- 3: https://github.com/pnpm/action-setup/tags
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:
- Pin to a specific commit as a workaround until the bug is fixed
- Verify that your workflow does not depend on pnpm version specification
- 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.
renovate
Bot
force-pushed
the
renovate/pnpm-action-setup-6.x
branch
from
c215870 to
5bbc84f
Compare
|
Deployment failed with the following error: View Documentation: https://vercel.com/docs/two-factor-authentication |
renovate
Bot
force-pushed
the
renovate/pnpm-action-setup-6.x
branch
from
5bbc84f to
071e1da
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.