fix: resolve Rust dependency advisories and audit Cargo.lock - #12
Merged
Conversation
Upgrade Tantivy to 0.26.1 so its lru dependency resolves to 0.16.3, update rand to 0.9.3, and preserve score ordering with Tantivy's explicit collector API.
Add rustsec/audit-check to the scheduled security workflow so the root Cargo.lock is audited alongside the npm wrapper.
Resolve each external action to the verified commit behind its existing version ref and retain readable version comments.
mstuart
added a commit
that referenced
this pull request
Aug 24, 2026
* fix(deps): resolve Rust dependency advisories Upgrade Tantivy to 0.26.1 so its lru dependency resolves to 0.16.3, update rand to 0.9.3, and preserve score ordering with Tantivy's explicit collector API. * ci: audit Rust dependencies with RustSec Add rustsec/audit-check to the scheduled security workflow so the root Cargo.lock is audited alongside the npm wrapper. * ci: pin security audit actions Resolve each external action to the verified commit behind its existing version ref and retain readable version comments. --------- Co-authored-by: Mark Stuart <mstuart@users.noreply.github.com>
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.
Summary
lruresolves to the patched 0.16.3 releaserandlock to 0.9.3order_by_score()collectorCargo.lockVerification
cargo check --all-targetscargo fmt --package code-memory -- --checkcargo clippy --all-targets -- -D warningscargo build --all-targetscargo build --releasecargo test(92 passed, 1 ignored; PostgreSQL-backed)cargo test --all-features(92 passed, 1 ignored; PostgreSQL-backed)cargo metadata --locked --format-version 1 --no-depscargo tree --locked -i lru->lru 0.16.3viatantivy 0.26.1cargo tree --locked -i rand@0.9.3-> all 0.9 consumers userand 0.9.3actionlint .github/workflows/security-audit.ymlgit diff --checknpm ci --ignore-scripts,npm run check,npm exec -- ultracite doctorScope note
A fresh full RustSec scan also reports five newer vulnerabilities not present in the two requested Dependabot alerts:
crossbeam-epoch,h2, two inpostgres-protocol, andtokio-postgres. They are intentionally not bundled into this PR. The new scheduled audit will surface them after merge.