ci: add --check-cache to yarn install in CI workflows - #10392
ci: add --check-cache to yarn install in CI workflows#10392dev-hari-prasad wants to merge 1 commit into
Conversation
Pass --check-cache to yarn install in GitHub Actions workflows to verify that cached package archives match the remote registry checksums, protecting against cache poisoning or corrupted cached packages.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (4)
Included review availability: Your plan provides up to 8 included reviews per hour; 6 remain after this review. WalkthroughFour GitHub Actions workflows now run ChangesWorkflow cache integrity
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to CI now validates cached JavaScript dependencies during installs in the style, JavaScript test, and feature-test workflows, failing on corrupted or inconsistent cache entries. No current merge-blocking risk is identified. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Part of #10363 (Item 6 from the tracking table).
As Dave noted in the issue discussion,
yarn install --check-cacheis a stronger form of cache and lockfile verification in CI.Instead of just checking that the lockfile is self-consistent and trusting whatever is already in the runner's disk cache,
--check-cachetells Yarn to re-verify the cached archives against the registry checksums to catch any cache tampering or poisoned archives.Changes
--check-cachetoyarn installacross the 4 GitHub Actions workflows:check-javascript-style.ymlrun-javascript-tests.ymlrun-feature-tests-epas.ymlrun-feature-tests-pg.ymlSummary by CodeRabbit