chore(deps): patch rustls-webpki and rand advisories#132
Merged
Conversation
Addresses GHSA-xgp8-3hg3-c2mh and GHSA-965h-392x-2mh5 in rustls-webpki (0.103.10 -> 0.103.12) and GHSA-cq8v-f236-94qc in rand (0.9.2 -> 0.9.4). Older rand/glib versions remain pinned by transitive Tauri/wry deps.
🧪 Test BuildsVersion:
ℹ️ About these builds
|
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
1 participant
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.
Updates two Rust dependencies in src-tauri/Cargo.lock to resolve open Dependabot advisories.
rustls-webpki moves from 0.103.10 to 0.103.12, closing GHSA-xgp8-3hg3-c2mh and GHSA-965h-392x-2mh5 (both low-severity name-constraint parsing issues). rand goes from 0.9.2 to 0.9.4 for GHSA-cq8v-f236-94qc (unsound interaction with custom loggers through rand::rng()).
The older rand 0.7/0.8 and glib 0.18 copies that Dependabot also flags come in transitively through wry/webkit2gtk and the Tauri plugin stack, so they can only move when Tauri/wry publish a release that upgrades them — not something we can fix from the lockfile.
cargo fmt --check and cargo clippy --all-targets --all-features -- -D warnings pass locally.