chore(ci): upgrade pnpm/action-setup from v4 to v6#216
Conversation
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
linked PR addressed this. |
Summary
Upgrades
pnpm/action-setupfromv4tov6in the CI workflow.Replaces: #211 (Renovate PR - CI was broken on the Renovate branch and it is protected, so we cannot push a fix there.)
Change
Single-line change in
.github/workflows/build-test-ci.yml:Compatibility
pnpm/action-setup@v6reads thepackageManagerfield frompackage.jsonto determine which pnpm version to install. This project has"packageManager": "pnpm@10.18.1+sha512...", so the action will continue installing pnpm 10.18.1 - no lockfile format changes or other side-effects expected.