Skip to content

Commit 8e3b150

Browse files
committed
chore(security): drop the nostr-relay-pool exception its own condition retired
#5404 allowed RUSTSEC-2026-0243 with the removal condition written into the comment: "Remove after mesh-llm migrates to nostr-sdk >= 0.45, which absorbed the standalone relay pool." MeshLLM v0.75.1 does exactly that, so nostr-relay-pool is no longer in either lockfile and the advisory has nothing to fire on. That PR measured 13 MeshLLM API compilation errors from bumping nostr-sdk to 0.45 against v0.74; upstream did the migration in v0.75, which is why this needs no source change here. Verified with the same commands #5404 used: bin/cargo-deny --locked check --config deny.toml advisories, and bin/cargo-deny --locked check -- advisories ok, bans ok, licenses ok, sources ok. Leaving a satisfied exception in place would suppress a real future advisory for this crate, so it goes with the bump that retired it rather than waiting for someone to notice. Signed-off-by: Michael Neale <[email protected]>
1 parent 00a4ddf commit 8e3b150

1 file changed

Lines changed: 0 additions & 4 deletions

File tree

‎deny.toml‎

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,6 @@ ignore = [
1515
# remove these when upstream catches up.
1616
{ id = "RUSTSEC-2026-0194", reason = "transitive via rust-s3 and mesh-llm→plist; trusted-input XML only; no upstream fix available yet" },
1717
{ id = "RUSTSEC-2026-0195", reason = "transitive via rust-s3 and mesh-llm→plist; trusted-input XML only; no upstream fix available yet" },
18-
# nostr-relay-pool 0.44.3 — informational/unmaintained, not a vulnerability.
19-
# Transitive via mesh-llm 0.74 → nostr-sdk 0.44.1. Remove after mesh-llm
20-
# migrates to nostr-sdk >= 0.45, which absorbed the standalone relay pool.
21-
{ id = "RUSTSEC-2026-0243", reason = "transitive via mesh-llm; upstream nostr-sdk 0.45 migration requires API changes" },
2218
]
2319

2420
[licenses]

0 commit comments

Comments
 (0)