Skip to content

Reduce directly owned Rust advisory exposure#2

Merged
OneNoted merged 1 commit intomainfrom
fix/dependabot-triage
Apr 15, 2026
Merged

Reduce directly owned Rust advisory exposure#2
OneNoted merged 1 commit intomainfrom
fix/dependabot-triage

Conversation

@OneNoted
Copy link
Copy Markdown
Owner

Summary

  • update Cargo.lock to move the directly owned reqwest/quinn branch onto rand 0.9.3
  • refresh rustls-webpki to 0.103.12
  • keep the remaining Tauri Linux stack advisories as explicit temporary risk acceptance instead of overstating them as fixed

Why

The lockfile still carried directly owned Rust dependency versions that could be tightened safely, even though the remaining Linux desktop advisories are inherited from the current upstream Tauri stack.

Impact

This narrows the advisory surface we own directly while keeping the workspace behavior unchanged. The remaining glib and tauri-utils advisory exposure still depends on upstream Tauri releases.

Validation

  • cargo test --workspace
  • cargo audit
  • GitHub Dependabot open-alert query returned [] after triage

The workspace still inherits unresolved Linux desktop advisories through the current Tauri stack, but the lockfile can still be tightened for the dependency branches this repo directly owns. Move the reqwest/quinn path onto rand 0.9.3 and refresh rustls-webpki so the remaining Dependabot triage is limited to upstream Tauri debt instead of stale local lockfile state.

Constraint: Current compatible Tauri Linux releases still resolve glib 0.18.x and tauri-utils rand copies
Rejected: Fork tauri-utils or replace Tauri for alert triage | too broad for this maintenance task
Confidence: medium
Scope-risk: narrow
Reversibility: clean
Directive: Revisit the dismissed GitHub alerts when Tauri publishes Linux stack updates for glib and rand advisories
Tested: cargo test --workspace; cargo audit; GitHub Dependabot open-alert query
Not-tested: packaged desktop runtime smoke test after the lockfile refresh
@OneNoted OneNoted marked this pull request as ready for review April 15, 2026 08:10
@OneNoted OneNoted merged commit eda5939 into main Apr 15, 2026
6 checks passed
@OneNoted OneNoted deleted the fix/dependabot-triage branch April 15, 2026 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant