Skip to content

ci(security): allow retired relay pool advisory - #5404

Merged
wesbillman merged 1 commit into
mainfrom
carl/rustsec-0243-exception
Aug 9, 2026
Merged

ci(security): allow retired relay pool advisory#5404
wesbillman merged 1 commit into
mainfrom
carl/rustsec-0243-exception

Conversation

@wesbillman

Copy link
Copy Markdown
Collaborator

Summary

  • temporarily allow the informational RUSTSEC-2026-0243 advisory for the retired nostr-relay-pool crate
  • document the exact MeshLLM → nostr-sdk 0.44.1 transitive path and removal condition
  • keep every other advisory and the global dependency policy enforced

Why an exception

RustSec provides no patched nostr-relay-pool release because the standalone crate was absorbed into nostr-sdk >= 0.45. Buzz inherits it through pinned MeshLLM v0.74. A direct test bump to nostr-sdk 0.45.1 removed the retired crate but produced 13 MeshLLM API compilation errors, so the durable fix requires an upstream source migration rather than a lockfile update.

This narrow exception restores the required Security check while that migration is completed. It must be removed once MeshLLM adopts nostr-sdk >= 0.45.

Validation

  • bin/cargo-deny --locked check --config deny.toml advisories
  • bin/cargo-deny --locked check
  • git diff --check origin/main...HEAD
  • mandatory pre-push Rust and desktop/Tauri checks

Scope

One four-line deny.toml addition. No Rust source, lockfile, runtime, or release behavior changes.

@wesbillman
wesbillman requested a review from a team as a code owner August 9, 2026 15:14
Temporarily allow the informational unmaintained advisory inherited
through MeshLLM until its Nostr integration migrates to nostr-sdk 0.45.

Co-authored-by: Carl <c7ebe626f000404285d3686e1dc74cc07cc60a9754a150041ba132e14bd3e2ec@buzz.block.builderlab.xyz>
Signed-off-by: Wes <wesbillman@users.noreply.github.com>
@wesbillman
wesbillman force-pushed the carl/rustsec-0243-exception branch from bb0f6d9 to 768500c Compare August 9, 2026 16:09
@wesbillman
wesbillman merged commit d2ebaa9 into main Aug 9, 2026
27 checks passed
@wesbillman
wesbillman deleted the carl/rustsec-0243-exception branch August 9, 2026 16:39
adrienlacombe pushed a commit to adrienlacombe/buzz that referenced this pull request Aug 9, 2026
## Summary

- temporarily allow the informational `RUSTSEC-2026-0243` advisory for
the retired `nostr-relay-pool` crate
- document the exact MeshLLM → `nostr-sdk 0.44.1` transitive path and
removal condition
- keep every other advisory and the global dependency policy enforced

## Why an exception

RustSec provides no patched `nostr-relay-pool` release because the
standalone crate was absorbed into `nostr-sdk >= 0.45`. Buzz inherits it
through pinned MeshLLM v0.74. A direct test bump to `nostr-sdk 0.45.1`
removed the retired crate but produced 13 MeshLLM API compilation
errors, so the durable fix requires an upstream source migration rather
than a lockfile update.

This narrow exception restores the required Security check while that
migration is completed. It must be removed once MeshLLM adopts
`nostr-sdk >= 0.45`.

## Validation

- `bin/cargo-deny --locked check --config deny.toml advisories`
- `bin/cargo-deny --locked check`
- `git diff --check origin/main...HEAD`
- mandatory pre-push Rust and desktop/Tauri checks

## Scope

One four-line `deny.toml` addition. No Rust source, lockfile, runtime,
or release behavior changes.

Signed-off-by: Wes <wesbillman@users.noreply.github.com>
Co-authored-by: Carl <c7ebe626f000404285d3686e1dc74cc07cc60a9754a150041ba132e14bd3e2ec@buzz.block.builderlab.xyz>
(cherry picked from commit d2ebaa9)
Signed-off-by: adrienlacombe <6303520+adrienlacombe@users.noreply.github.com>
wpfleger96 pushed a commit that referenced this pull request Aug 9, 2026
…ckend

* origin/main:
  chore(deps): update react monorepo (#4441)
  ci(security): allow retired relay pool advisory (#5404)
  chore(deps): update dependency @tanstack/react-virtual to v3.14.9 (#4439)
  chore(deps): update all non-major dependencies (#3049)
  chore(deps): update rust crate anyhow to v1.0.104 (#4447)
  chore(deps): update rust crate arc-swap to v1.9.2 (#4448)
  chore(deps): update rust crate async-trait to v0.1.91 (#4458)
  chore(deps): update rust crate diffy to v0.5.1 (#4466)
  chore(deps): update rust crate async-compression to v0.4.43 (#4456)
  chore(deps): update rust crate clap to v4.6.6 (#4465)
  fix(desktop): preserve Welcome banner dismissal (#5406)

Signed-off-by: Duncan <dcfd242e557282d7a1e2cf2e6877522682f1e5c6156dc92ca7d90eaedd3b0f95@buzz.block.builderlab.xyz>
41fred pushed a commit to 41fred/buzz that referenced this pull request Aug 9, 2026
## Summary

- temporarily allow the informational `RUSTSEC-2026-0243` advisory for
the retired `nostr-relay-pool` crate
- document the exact MeshLLM → `nostr-sdk 0.44.1` transitive path and
removal condition
- keep every other advisory and the global dependency policy enforced

## Why an exception

RustSec provides no patched `nostr-relay-pool` release because the
standalone crate was absorbed into `nostr-sdk >= 0.45`. Buzz inherits it
through pinned MeshLLM v0.74. A direct test bump to `nostr-sdk 0.45.1`
removed the retired crate but produced 13 MeshLLM API compilation
errors, so the durable fix requires an upstream source migration rather
than a lockfile update.

This narrow exception restores the required Security check while that
migration is completed. It must be removed once MeshLLM adopts
`nostr-sdk >= 0.45`.

## Validation

- `bin/cargo-deny --locked check --config deny.toml advisories`
- `bin/cargo-deny --locked check`
- `git diff --check origin/main...HEAD`
- mandatory pre-push Rust and desktop/Tauri checks

## Scope

One four-line `deny.toml` addition. No Rust source, lockfile, runtime,
or release behavior changes.

Signed-off-by: Wes <wesbillman@users.noreply.github.com>
Co-authored-by: Carl <c7ebe626f000404285d3686e1dc74cc07cc60a9754a150041ba132e14bd3e2ec@buzz.block.builderlab.xyz>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants