Repository navigation
chore(deps): fix dependency-audit findings (#358) - #359
Merged
Merged
Conversation
ajianaz
force-pushed
the
chore/fix-dependency-audits
branch
from
October 22, 2026 14:40
e1de4d3 to
5409a15
Compare
3 tasks
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.
What
Dependency-audit fixes: lockfile refreshes + targeted minor updates for the vulnerable packages; transitive advisories with no compatible fix get a documented, dated audit-ignore (
.cargo/audit.toml).Why
Closes #358. The Security audit gates have been red on
develop(pre-existing; isolated during the fleet CLA retirement, uteke#1548). This PR makes the gates honestly green.Testing
cargo auditbefore/after locally (advisory DB refreshed): remaining findings = none beyond the documented ignores