fix(ci): downgrade pnpm/action-setup to v5 in dependency-audit reusable#152
fix(ci): downgrade pnpm/action-setup to v5 in dependency-audit reusable#152
Conversation
The SHA 08c4be7e (mislabeled # v4) is actually pnpm/action-setup@v6.0.0, which bootstraps with pnpm v11.0.0-rc.0. pnpm v11-rc cannot parse lockfiles generated by pnpm v9 (lockfileVersion '9.0'), causing ERR_PNPM_BROKEN_LOCKFILE in all repos still on pnpm v9. Pinning to action-setup@v5.0.0 (fc06bc1), which installs pnpm via npm directly with no v11 bootstrap, restoring compatibility with pnpm v9.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdated the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
|
There was a problem hiding this comment.
Pull request overview
This PR fixes a breaking CI regression in the org’s reusable dependency-audit workflow by pinning pnpm/action-setup to a compatible major version, avoiding pnpm v11-rc bootstrapping that fails on pnpm v9 lockfiles.
Changes:
- Downgrade
pnpm/action-setuppin in the pnpm audit job from the (mis-labeled) v6 SHA to a v5.0.0 SHA.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Automated review — APPROVEDRisk: LOW SummarySingle-line SHA pin correction in a reusable CI workflow: the old SHA was mislabeled as v4 but resolved to pnpm/action-setup@v6.0.0, which broke pnpm v9 repos; the new SHA correctly pins v5.0.0. All CI gates pass (CodeQL, SonarCloud, ShellCheck, AgentShield, Lint) with zero new issues or security hotspots. No security concerns — SHA pinning is maintained, no secrets or credentials touched. FindingsInfo
Reviewed by the don-petry PR-review cascade (triage: haiku 4.5 → deep: sonnet 4.6 + duck: gpt-5.4 → audit: opus 4.6). Reply with `@don-petry` if you need a human. |



Problem
The SHA `08c4be7e` pinned in `dependency-audit-reusable.yml` is labeled `# v4` but is actually pnpm/action-setup@v6.0.0. v6 bootstraps with pnpm v11.0.0-rc.0, which cannot parse `lockfileVersion: '9.0'` lockfiles generated by pnpm v9. This causes `ERR_PNPM_BROKEN_LOCKFILE` in all repos still on pnpm v9 — confirmed breaking `broodly` main.
Fix
Pin to `pnpm/action-setup@v5.0.0` (`fc06bc1`), which installs pnpm directly via npm with no v11-rc bootstrap, restoring compatibility with pnpm v9.
Note
Upgrade to action-setup@v6 can be revisited org-wide once repos have migrated to pnpm v11.
Summary by CodeRabbit