[EnRaiha]

Changes

• Cargo.lock moves wasmtime from 49.0.3 to 49.0.4.
• The lockfile moves the crates that release in step with it: cranelift-* 0.136.3 to 0.136.4, pulley-*, wasmtime-environ and the wasmtime-internal-* crates.
• No Cargo.toml, deny.toml or source file changes. The ^49 requirement already allows 49.0.4.

Reason

cargo deny check advisories fails on main for two advisories on wasmtime 49.0.3:

Advisory	Title	Fixed in
RUSTSEC-2026-0378	Panic lowering a host-created component model stream into a guest that expects a different payload type	49.0.4
RUSTSEC-2026-0379	Cranelift backend on aarch64 can jump to incorrect target on large Wasm br_table instruction	49.0.4

The failure sits in the Dependency audit step of Test Suite / Lint & Check, so every open PR shows that job red. deny.toml gains no exception.

Checks

• cargo deny check: advisories, bans, licenses and sources pass.
• cargo fmt --all -- --check: passes.
• cargo check -p nodedb --locked --all-targets: passes (--locked, 13 min 17 s).
• Focused tests: cargo test -p nodedb --lib --locked -- planner::wasm runs 20 tests and all 20 pass.
• Local preflight: clippy --workspace --all-targets --all-features --profile ci -D warnings fails on main with rustc 1.96.1 at nodedb-sql/src/types/plan/search_cells.rs:32 (unused import super::*). The PR changes only Cargo.lock. The push used PREFLIGHT_SKIP=1 for that reason.

[Copilot]

Copilot wasn't able to review any files in this pull request. Check if the Files changed in this pull request are included in default exclusions.

[EnRaiha]

Added a second commit: rustls-webpki 0.103.15 to 0.103.16 (RUSTSEC-2026-0382) and webpki-root-certs 1.0.9 to 1.0.10 (RUSTSEC-2026-0383). Both advisories were published after this PR opened and turned Dependency audit red again. cargo deny check passes locally. Cargo.lock only. The pre-push clippy -D warnings step reports an unused import in nodedb-sql that is already on main, so I pushed with PREFLIGHT_SKIP=1 once.