[TheStreamCode]

Summary

Refreshes the locked dependency graph to close seven Dependabot alerts, without changing any manifest, the toolchain, or application code.

Alerts	Package	Advisory	Locked version
#2, #3, #4, #5	aws-sdk-s3, aws-sdk-sso, aws-sdk-ssooidc, aws-sdk-sts	GHSA-g59m-gf8j-gjf5 (low)	1.123.0, 1.94.0, 1.96.0, 1.98.0
#12	aws-smithy-json	GHSA-8ffr-xgwf-xj56 / CVE-2026-18140 (high)	0.62.7
#6, #7	rand	GHSA-cq8v-f236-94qc (low)	0.8.6 and 0.10.1

The AWS family moves to the newest releases whose rust-version still fits the pinned 1.94.0 toolchain: aws-smithy-types 1.5.0 and aws-smithy-runtime-api-macros 1.0.0. In total 24 packages take a newer version and two crates enter the graph (aws-smithy-runtime-api-macros, aws-smithy-schema), all from crates.io. ryu 1.0.23 and tokio-util 0.7.20 take their latest patches in the same pass.

Two alert groups stay deliberately out:

• zip, 11 alerts (3 critical, 5 high, 3 medium): closing them means the 3 to 9 major migration, which is separate work rather than a lockfile refresh.
• lru fix(deps): resolve 7 Dependabot security alerts (rand, aws-sdk) #14 (low): the alert is on crates/codegen/chutes-markdown/fuzz/Cargo.lock, where ratatui 0.29 pins the lru 0.12 line. The fuzz lock is untouched.

Verification

• I ran the narrowest relevant checks and list them below. Compilation and the test suites are covered by this PR's CI jobs on Linux, Windows and macOS.
• Documentation: no user-visible or operational change applies, so no documentation update applies.
• I did not add credentials, private data, telemetry, or unreviewed network calls.
• I preserved upstream and third-party license notices; cargo deny reports licenses ok.

Commands and results:

cargo deny check
advisories ok, bans ok, licenses ok, sources ok   (exit 0)

MSRV scan over cargo metadata --locked (rust_version of every package)
checked=1347 violations=0

cargo update -p rand@0.10.0 --precise 0.10.1
Updating rand v0.10.0 -> v0.10.1   (exit 0)

No local build was run: this clone carries no build cache, and the CI jobs compile and test the full platform matrix on every push.

Privacy and compatibility

No change to network behavior, credentials, permissions, storage, supported platforms or model routing. Only transitive dependency versions move; the six native builds and the npm launcher are unaffected.