Repository navigation
ci: pin cargo-llvm-cov installer to release SHA - #583
Conversation
Use the v2.90.5 release commit with an explicit cargo-llvm-cov tool input in all three coverage workflows. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Performance Report (Linux)Result: ✅ Within regression budgets
|
Test Coverage Report (Linux)Result: ✅ Within regression budget
|
Performance Report (Windows)Result: ✅ Within regression budgets
|
Performance Report (macOS ARM64)Result: ✅ Within regression budgets
|
Test Coverage Report (Windows)Result: ✅ Within regression budget
|
Performance Report (macOS)Result: ✅ Within regression budgets
|
|
🔒 Automated review in progress — Rich Chiodo (@rchiodo) is auto-reviewing this PR. |
|
Reviewed commit: Result: 🔴 Verification detailsVerification: Automated verification is best effort. The PR author remains responsible for testing. Summary: [unavailable] Container verification could not start and local execution was not authorized for this PR HEAD: C:\Users\rchiodo\AppData\Local\Programs\Podman\podman.EXE --connection pyrx-automation failed: stderr: Error: unable to start container "3801b3f5535d24047c24f35d39827e1ac4ec5222e9a23c266bae0cc9714bf105": crun: open `memory.max` for writing: No such file or directory: OCI runtime attempted to invoke a command that was not found Test runs: none recorded. |
Rich Chiodo (rchiodo)
left a comment
There was a problem hiding this comment.
Approved via Review Center.
Pin the remaining mutable
taiki-e/install-action@cargo-llvm-covreference in all three coverage workflows (coverage.yml,coverage-baseline.yml, andcoverage-macos.yml) toab49d3c64680143e184118bed66a46419fc15519, the commit for v2.90.5. Add an explicittool: cargo-llvm-covinput and a human-readable version comment.Use the versioned release rather than the generated tool-tag commit: the action maintainer discourages pinning tool tags by hash because those generated commits become unreferenced after subsequent releases. The selected release commit is the parent of the tool-tag commit verified during the original investigation, and their only difference is the tool input default; specifying that input explicitly preserves the existing installation behavior.
All action references in the repository's workflows use full-length commit SHAs. Existing weekly grouped Dependabot updates and the seven-day cooldown are unchanged.