Pin mesh-sdk dbcaa29, so the controller composes with the group fix/1960-no-hold-spread's SDK (issue 1960) #480

2026-10-29T15:18:58Z

mesh-tools commented

2026-10-29 15:18:58 +00:00

Why

The group fix/1960-no-hold-spread (recovery of novox, issue 1960) failed its check at the composition: "mesh-delivery-assigner claims mesh-placement ... the group must move mesh-controller onto mesh-sdk dbcaa29". The checker composes with the controller built on the group's SDK; the controller pinned an older one.

What changes

go.mod/go.sum pin mesh-sdk v0.1.14-0.20261029145421-dbcaa29a1a38 (the group's mesh-sdk head); resolved from the exact commit with a local module proxy while git.novox.be:443 is down; the hashes equal mesh-host's for the same version.
testdata/beside/CAPTURED names mesh-sdk dbcaa29; conformance/events is unchanged byte for byte.
No code change.

Quick fix or thorough fix

Quick, chosen: the pin the checker asks for, to finish the recovery.
Thorough, after design 47 (the operator): the build plan publishes the SDK as a version and moves every dependant onto it in the next tier; no module pins the SDK by hand.

How it is checked

go build, go vet -tags integration and go test ./... pass; the group's one check composes all four members.

Group: delivery group fix/1960-no-hold-spread (mesh-sdk, mesh-delivery, mesh-host, mesh-controller).

Reviewed-by: rev-hold@shanks at 020c6a99b0

## Why The group fix/1960-no-hold-spread (recovery of novox, issue 1960) failed its check at the composition: "mesh-delivery-assigner claims mesh-placement ... the group must move mesh-controller onto mesh-sdk dbcaa29". The checker composes with the controller built on the group's SDK; the controller pinned an older one. ## What changes - go.mod/go.sum pin mesh-sdk v0.1.14-0.20261029145421-dbcaa29a1a38 (the group's mesh-sdk head); resolved from the exact commit with a local module proxy while git.novox.be:443 is down; the hashes equal mesh-host's for the same version. - testdata/beside/CAPTURED names mesh-sdk dbcaa29; conformance/events is unchanged byte for byte. - No code change. ## Quick fix or thorough fix - Quick, chosen: the pin the checker asks for, to finish the recovery. - Thorough, after design 47 (the operator): the build plan publishes the SDK as a version and moves every dependant onto it in the next tier; no module pins the SDK by hand. ## How it is checked `go build`, `go vet -tags integration` and `go test ./...` pass; the group's one check composes all four members. Group: delivery group fix/1960-no-hold-spread (mesh-sdk, mesh-delivery, mesh-host, mesh-controller). Reviewed-by: rev-hold@shanks at 020c6a99b035a5e33ac0299579b95b4c58bf4e51

mesh-tools added 1 commit 2026-10-29 15:18:58 +00:00

Pin mesh-sdk dbcaa29 and capture its conformance events there, so the controller composes with the group fix/1960-no-hold-spread's SDK (issue 1960)

mesh/delivery merged: source.main moved to novox/mesh-controller@e04846e9fa49

Details

mesh/delivery-group group fix/1960-no-hold-spread merged: every member is merged

Details

mesh/check pass 020c6a99b035 on 5a9766d4a47a | unit 3318 run, 1951 kept, 38 skipped | integration 3994 run, 2125 kept, 38 skipped | over bound: unit, …

020c6a99b0

mesh-tools commented

2026-10-29 15:19:02 +00:00

Delivery novox/mesh-controller@020c6a99b035 — merged since 2026-10-29T15:35:32Z

Source — source.main moved to novox/mesh-controller@e04846e9fa. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.

Group fix/1960-no-hold-spread: novox/mesh-controller@020c6a99b0, novox/mesh-delivery@d54eab4052, novox/mesh-host@ece607e215, novox/mesh-sdk@dbcaa29a1a

composed together: pass — the checker's verdict at the members' heads (f0569710e57f)

Transitions

2026-10-29 15:18 (new) → proposed (announced): novox/mesh-controller#480's head announced
2026-10-29 15:19 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-10-29 15:35 ready → merged (merged): on the trunk its modules follow: merged there

The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.

**Delivery** `novox/mesh-controller@020c6a99b035` — **merged** since 2026-10-29T15:35:32Z **Source** — source.main moved to novox/mesh-controller@e04846e9fa49. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `fix/1960-no-hold-spread`: novox/mesh-controller@020c6a99b035, novox/mesh-delivery@d54eab4052d1, novox/mesh-host@ece607e21522, novox/mesh-sdk@dbcaa29a1a38 - composed together: pass — the checker's verdict at the members' heads (f0569710e57f) **Transitions** - 2026-10-29 15:18 (new) → proposed (announced): novox/mesh-controller#480's head announced - 2026-10-29 15:19 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false) - 2026-10-29 15:35 ready → merged (merged): on the trunk its modules follow: merged there The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.

mesh-tools merged commit e04846e9fa into main

2026-10-29 15:35:31 +00:00

mesh-tools deleted branch fix/1960-no-hold-spread

2026-10-29 15:35:32 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#480