Commit 49d6856
fix(Cargo.toml): remove stale tokio-tungstenite v0.28.0 patch (no-op, false assurance)
The [patch.crates-io] entry for tokio-tungstenite v0.28.0 was inert: the
workspace resolves tokio-tungstenite to 0.21.0 and 0.29.0 (both crates.io),
so Cargo marked the v0.28.0 patch [[patch.unused]] and emitted a "patch was
not used in the crate graph" warning on every build/clippy.
v0.29.0 already includes rustls 0.23.40, which natively fixes
RUSTSEC-2026-0049. The v0.28.0 git patch was a pre-0.29.0 workaround that
created false security assurance — a declared-but-never-applied "fix".
Scope is surgical (7 deletions, 0 additions, 2 files):
- Cargo.toml: delete the tokio-tungstenite comment + patch line.
- Cargo.lock: delete the [[patch.unused]] block for the v0.28.0 git source.
- The unrelated rustls-webpki git patch (RUSTSEC CRL/name-constraint scope)
is intentionally preserved.
This is the faithful mirror of commit c5119df (the Carthos-validated fix
for the duplicate #2742), re-applied on a pristine branch cut from
origin/main (236d747). Prior branches drifted into contamination
(.docs/.pr2659/.gitignore churn); this branch carries ONLY the patch removal.
Verification:
- cargo clippy --workspace -- -D warnings: exit 0, 0 warnings, no
"patch not used" warning.
- cargo build -p terraphim_server (tungstenite consumer): exit 0.
- cargo audit: no tokio-tungstenite / RUSTSEC-2026-0049 findings.
- cargo fmt --all --check: clean.
- Diff vs origin/main: exactly 7 deletions, 0 additions.
Refs #2986 (duplicate of #2742)
Co-Authored-By: Claude <noreply@anthropic.com>1 parent 236d747 commit 49d6856
2 files changed
Lines changed: 0 additions & 7 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
97 | 97 | | |
98 | 98 | | |
99 | 99 | | |
100 | | - | |
101 | | - | |
102 | 100 | | |
103 | 101 | | |
104 | 102 | | |
| |||
0 commit comments