Split cargo check matrix to individual targets. Avoid cache poisoning#7540
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughRestructures the CI Changes
Sequence Diagram(s)(omitted) Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
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 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 |
57a6b73 to
7e6a7cb
Compare
The main motivation of this PR is to move away from
Swatinem/rust-cacheaction, as it doesn't allow a fine grained control over the cache likeactions/cachedoes.This PR will resolve the following lints warnings:
runtime artifacts potentially vulnerable to a cache poisoning attack(by using otheractions/cache)action functionality is already included by the runner(by usingrustupinstead ofdtolnay/rust-toolchain)Summary by CodeRabbit
Release Notes
No user-facing changes
This release contains internal improvements to the build and continuous integration infrastructure only.