Repository navigation
fix(deps): patch webpki advisories RUSTSEC-2026-0381 to 0383 - #54
Open
LemonMantis5571 wants to merge 3 commits into
Open
LemonMantis5571 wants to merge 3 commits into
LemonMantis5571 wants to merge 3 commits into
Conversation
Bump the three crates in Cargo.lock that the RustSec gate flagged as vulnerable, so `cargo audit` passes again: - rustls-webpki 0.103.15 -> 0.103.16 (RUSTSEC-2026-0382) - webpki-roots 1.0.9 -> 1.0.11 (RUSTSEC-2026-0381) - webpki-root-certs 1.0.9 -> 1.0.11 (RUSTSEC-2026-0383) All three arrive through reqwest 0.13.1, and the patched releases are semver-compatible, so Cargo.toml is unchanged. The remaining 12 findings are allowed warnings (unmaintained, unsound, yanked) and are untouched. Record the locked versions in the developer-verification feature entry, as the previous advisory bump did.
LemonMantis5571
enabled auto-merge
November 2, 2026 21:16
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
cargo auditfails on master'sCargo.lockwith 3 vulnerabilities, which turns theRustSec (cargo audit)step of the Linux full verify red. PR #53 clearsnpm audit, which runs first, and that exposed this failure (failing run).This bumps the three flagged crates in
Cargo.lock:rustls-webpkiwebpki-rootswebpki-root-certsAll three are pulled in only through
reqwest0.13.1 (rustls-platform-verifier,hyper-rustls,tokio-rustls). The patched releases are semver-compatible, so no transitive pin blocked the bump andCargo.tomlis unchanged. No major upgrade was needed.The lockfile diff is exactly those three packages.
cargo updatealso flipped tempfile'sgetrandomedge from 0.4.3 to 0.3.4. tempfile accepts either (>=0.3.0, <0.5), so that was resolver noise and I restored it to keep the diff minimal.I also added the new locked versions and advisory IDs to the
developer-verification-and-releasefeature entry, as the previous advisory bump (e0a5c1d) did.Verification
cargo auditexits 0. The 3 vulnerabilities are gone. The 12 allowed warnings (unmaintained, unsound, yankedchacha200.10.1, and so on) are unchanged and not addressed here.cargo metadata --lockedaccepts the edited lockfile.cargo check --workspacepasses.cargo test -p zest-corepasses: 1081 passed, 0 failed. On the first run, threetools::external_agenttests timed out while the machine was still compiling, which CONTRIBUTING.md warns about. They pass alone (46/46) and in the full rerun.npm run features:checkpasses.npm run verifylocally. It needsnpm ciand a full clippy and Playwright pass, so CI's full verify on this PR is the check for that.Known unrelated flake
The Windows full verify job on PR #53 failed on one Playwright test,
crates/desktop/ui/e2e/slash-commands.spec.ts:5("slash skills can be invoked more than once from any draft position"), which timed out after 30s waiting for thebrowse-xoption in the Commands listbox. It passed on PR #52's Windows run, so it looks like a flake. This PR does not touch it, and a failure there on this PR would be that same flake.