Repository navigation
fix(ci): install cargo-audit with --locked - #157
Merged
Merged
Conversation
cargo install cargo-audit resolves tinyvec 1.13.0 (released 2026-09-03), which fails to compile ("cannot find macro vec in this scope"), so the Security Scan job dies before the audit runs. --locked uses cargo-audit's own lockfile, which pins a tinyvec that builds. Verified locally: unlocked reproduces the error, locked installs cargo-audit 0.22.2.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Original fix. The
Security Scanjob ondevelop(run 33812431685, first red after the 2026-09-03 sync) fails before the audit runs:cargo install cargo-auditnow resolves tinyvec 1.13.0, released today, which does not compile.--lockedmakes cargo use cargo-audit's own lockfile, which pins a tinyvec that builds.Repro, local x64 toolchain
Upstream's own
Security Scanpassed at 19:53 UTC today with the unlocked command; the fork's failed at 22:21. Nothing in the repo is involved: the same command fails on a clean machine.Not a fork divergence
The install line is identical to upstream's
ci.yml. Upstream has no open PR or issue for this (searchedcargo-audit,tinyvec,locked; PR rtk-ai#3539 touchesci.ymlbut not this step). An upstream PR follows once this is green here.Quality gate
YAML-only change; no Rust touched. CI on this branch is the verification.