Cordy/Cairn
2
1
Fork 0
Code Issues 20 Pull requests Projects Releases Packages Wiki Activity Actions

#244 Ship 1: inbound space allow-list + CanReceiveSpace (v0.6.26) #245

Merged
Cordy merged 2 commits from feat/244-ship1 into main 2026-08-15 16:18:58 +00:00
Conversation 0 Commits 2 Files changed 3 +63 -2
Cordy commented 2026-08-15 16:17:39 +00:00
Owner
Copy link

First slice of #244 (Space as a peering recipient). Backend groundwork only — no user-facing surface yet; deploy/test happens after Ship 3.

  • peering.Senders (shared shape) gains Spaces; peers now carry an inbound Receivers.Spaces allow-list.
  • Registry.CanReceiveSpace(peer, space) — fail-closed, disabled-aware, mirrors CanReceive. Existence is a separate delivery-time check (Ship 2).
  • Registry.ReceiverSpaces(peer) accessor.
  • Admin peers API: add/update/list carry receivers.spaces / recvSpaces.

Runner: go vet / build / test ./internal/peering/... ./internal/api/... all green.

Part of #244.

First slice of #244 (Space as a peering recipient). Backend groundwork only — no user-facing surface yet; deploy/test happens after Ship 3. - `peering.Senders` (shared shape) gains `Spaces`; peers now carry an inbound `Receivers.Spaces` allow-list. - `Registry.CanReceiveSpace(peer, space)` — fail-closed, disabled-aware, mirrors `CanReceive`. Existence is a separate delivery-time check (Ship 2). - `Registry.ReceiverSpaces(peer)` accessor. - Admin peers API: `add`/`update`/`list` carry `receivers.spaces` / `recvSpaces`. Runner: `go vet` / `build` / `test ./internal/peering/... ./internal/api/...` all green. Part of #244.
#244: inbound space allow-list + CanReceiveSpace (Ship 1, v0.6.26)
All checks were successful
ci / test-and-build (pull_request) Successful in 37s
Details
50c2aaa03a
Cordy merged commit ec8ecac8b1 into main 2026-08-15 16:18:58 +00:00
Cordy deleted branch feat/244-ship1 2026-08-15 16:19:00 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#245
No description provided.
Delete branch "feat/244-ship1"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?