Repository navigation
chore(deps): batch dependency updates (early Nov 2026) - #643
Merged
Merged
Conversation
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
Cargo.lock,fuzz/Cargo.lock, andci/wasm-smoke/Cargo.lockare regenerated against currentmain.rustls-webpki0.103.16 (RUSTSEC-2026-0382) andwebpki-roots1.0.11 (RUSTSEC-2026-0381), both about distrusted intermediates being accepted during certificate verification,webpki-root-certs1.0.11 (RUSTSEC-2026-0383), andctutils0.4.5 (RUSTSEC-2026-0385), in the root and fuzz lockfiles. These are whycargo auditandcargo denyfail on every open Cargo PR, including fix: parse conditions on musl and refuse rule loads in which every rule fails #642.tokio1.54.1 also resolves the unsound warning RUSTSEC-2026-0386.evtx0.12 to 0.13 drops the unmaintainedencodingcrate (RUSTSEC-2021-0153), socargo auditnow reports no warnings at all. The stale note about it indeny.tomlis removed. One behavior change reaches rules: Windows bool substitution values other than 0 and 1 (bitmasks in some bool fields) are kept as integers instead of being coerced totrue. The changelog calls it out.pest2.9.4,serde_json1.0.154,jaq-core3.1.2,sha20.11.1,opentelemetry-proto0.33.1, and the rest of build(deps): bump the patch-updates group across 1 directory with 14 updates #640,uuid1.29.0 (chore(deps): bump uuid from 1.27.0 to 1.28.0 #636), andserde_json1.0.154 in the fuzz crate (chore(deps): bump serde_json from 1.0.151 to 1.0.154 in /fuzz in the patch-updates group #631).jsonschema0.58 to 0.60,rusqlite0.40 to 0.41,fancy-regex0.19 to 0.20,parking_lot0.12 to 0.13,p12-keystore0.3 to 0.4, andrmcp3.7.0. All build without code changes.fancy-regexis only used to validate|repatterns during linting, so its 0.20 matching fixes do not change detection results.Swatinem/rust-cachev2.9.3,taiki-e/install-actionv2.87.30,github/codeql-action/upload-sarifv4.39.1,rust-lang/crates-io-auth-actionv1.0.6, andzizmorcore/zizmor-actionv0.7.1, pinned by full commit SHA (build(deps): bump the actions-updates group across 1 directory with 5 updates #639). zizmor 1.31.1, which the new action runs, reports no findings.@types/node26.6.5 (chore(deps-dev): bump @types/node from 26.6.4 to 26.6.5 in /editors/vscode in the npm-updates group #630). Docs:markdown-it14.3.3 (chore(deps): bump markdown-it from 14.3.2 to 14.3.3 in /docs #628).pest2.9.5,rusqlite0.41.1,jsonschema0.60.2,rmcp3.8,async-nats0.51,tonic0.14.9, and the October 28debian:stable-slimandpython:3.13-slimdigests). The pySigma requirements have no updates outside the cooldown.yamlpath/yamlpatch1.31.0 (chore(deps): bump yamlpath from 1.27.0 to 1.31.0 #635, chore(deps): bump yamlpatch from 1.26.1 to 1.31.0 #634) require rustc 1.97 throughtree-sitter-iter, above the 1.96.0 MSRV.tikv-jemallocator0.7.0 (chore(deps): bump tikv-jemallocator from 0.6.1 to 0.7.0 #425) remains excluded after the measured musl daemon throughput regression.testcontainers0.28.0 waits for atestcontainers-modulesrelease.reqwest0.13 inrsigma-runtimeandrsigma-mcpswaps the bundledwebpki-rootstrust store for the platform verifier, which changes which certificates the webhook and OTLP/HTTP sinks, HTTP enrichers, HTTP dynamic sources, and the MCP daemon client trust, so it needs its own change.Closes #640, closes #639, closes #636, closes #631, closes #630, closes #628.
Test plan
cargo fmt --all -- --checkcargo clippy --workspace --all-targets --all-features --locked -- -D warningscargo doc --workspace --all-features --locked --no-depscargo test --workspace --all-features --locked(4520 tests pass)cargo check --lockedinfuzz/ci/wasm-smokerelease build with--lockedandwasmtime run --invoke run_selftestcargo auditon both lockfiles andcargo deny checkzizmor --pedantic .github/workflowswith 1.30.1 and 1.31.1python3 scripts/mcp-smoke.pyover stdio and--httpnpm ci,npm run compile, andtsc --noEmitnpm run docs:buildandnpm run docs:validate