Will Pfleger 448407a972 test(relay): configure a community in the Git ban-lookup fixture (#8039) ...

🤖 Follows #8036 (merged).

The Postgres test `failed_restriction_lookup_is_503_not_403` in
`crates/buzz-relay/src/api/git/transport.rs` sets `nip_fi.mode =
Enforce` but configured no NIP-FI communities. Since #8028, enforce mode
refuses that request at Host-to-community lookup with the same `503
authorization unavailable` the test expects, so the enforce half never
reached the ban lookup it is meant to guard. Deleting the `unavailable`
mapping on the ban-lookup error in `GitAuth::from_request_parts` left
the test passing.

The fixture now binds a community with `test_support::any_host`, the
same way #8028 fixed the other enforce fixtures in this file. With the
mapping deleted, the enforce half now fails.

Found by @loganj's review comment on #8036.

Signed-off-by: Will Pfleger <pfleger.will@gmail.com>
Co-authored-by: Duncan <dcfd242e557282d7a1e2cf2e6877522682f1e5c6156dc92ca7d90eaedd3b0f95@buzz.block.builderlab.xyz>

2026-10-02 08:34:28 -06:00

..

repos

feat(buzz-relay): NIP-FI stateless enforcement (S3) — upgrade gate, NIP-42 pairing, session lifetime, JWKS warm (#7224)

2026-09-29 14:27:40 -04:00

src

test(relay): configure a community in the Git ban-lookup fixture (#8039)

2026-10-02 08:34:28 -06:00

tests

Make relay readiness process-local (#7341)

2026-09-28 14:02:12 -04:00

Cargo.toml

feat(relay): enforce NIP-FI assertion+NIP-98 pairing on HTTP ingress (#7264)

2026-09-25 21:01:31 +00:00

CHANGELOG.md

chore(release): release Buzz Relay version 0.2.1 (#2856)

2026-08-08 12:26:24 -04:00