ci: install cargo-deny via install-action instead of cargo-deny-action#65
Conversation
The cargo-deny-action rebuilds a Docker image each run (apk add + curl the musl binary), which flaked twice on transient apk-mirror / GitHub-release hiccups and red-X'd otherwise-clean runs. taiki-e/install-action pulls a cached prebuilt binary (already used for nextest here, same pinned SHA) — faster and no per-run Docker build. Adds the rust-toolchain step so cargo metadata resolves the pinned 1.95.0 toolchain (also removes the old musl-toolchain warning noise).
|
Warning Review limit reached
More reviews will be available in 43 minutes and 48 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ 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 |
Newer cargo-deny (from install-action) treats --all-features as a global cargo-metadata flag, so it must precede 'check' (cargo deny --all-features check), not follow it.
1 participant
The
cargo-deny-actionrebuilds a Docker image every run (apk add + curl the musl binary) — flaked twice on transient apk/GH-release hiccups, red-X'ing clean runs. Switch totaiki-e/install-action(cached prebuilt binary, already used for nextest with the same pinned SHA) + an explicit toolchain step socargo metadataresolves pinned 1.95.0. Same check (cargo deny check --all-features), no policy change.