Build mesh-build-go against the group mesh-sdk, so a manifest removing ASSIGNMENTS is accepted and the catalogue members of feat/072-moves build (issue 774) #580

2026-10-31T11:10:43Z

mesh-tools commented

2026-10-31 11:10:43 +00:00

Issue 774 (L3 of design 47), the delivery of the group feat/072-moves (merged 2026-10-31 11:31).

The Go build module checks every manifest with the mesh-sdk compiled into it. Its pin a37181261c24 does not know the bus removal ASSIGNMENTS (catalogue.BusRemovals, added in mesh-sdk acbf80a), so nats's manifest was refused at 11:45 and 11:48 ("removes ASSIGNMENTS, which is not one of DEAD_LETTER_NOTICES.controller, mesh-host_acts") and the catalogue's members of the group (the vault, the provisioner and the rest) never built.

This moves modules/mesh-build-go to mesh-sdk acbf80ad910a (go.mod and go.sum only; module.json unchanged).

Quick fix vs thorough fix: quick: this hand pin, which the operator allowed for this group one last time. Thorough: ADR 0573 §2 and §3, every module built against the latest published mesh-sdk and a publish rebuilding its dependents (issue 1585), next after this delivery. Chosen: quick now, since the group's delivery is blocked and 1585 is its own milestone.

Tests: in modules/mesh-build-go, gofmt -l, go vet ./..., go vet -tags integration ./..., go test ./... and go mod verify are clean.

After the merge: route-proxy stays held on ace and novox (assigner_put hold, 12:07) until the new provisioner runs healthy, because the new route-proxy serves only from plan contributions the old provisioner does not write.

Reviewed-by: rev-buildgo@shanks at b8f62cd2ac

Issue 774 (L3 of design 47), the delivery of the group feat/072-moves (merged 2026-10-31 11:31). The Go build module checks every manifest with the mesh-sdk compiled into it. Its pin a37181261c24 does not know the bus removal `ASSIGNMENTS` (`catalogue.BusRemovals`, added in mesh-sdk acbf80a), so nats's manifest was refused at 11:45 and 11:48 ("removes ASSIGNMENTS, which is not one of DEAD_LETTER_NOTICES.controller, mesh-host_acts") and the catalogue's members of the group (the vault, the provisioner and the rest) never built. This moves `modules/mesh-build-go` to mesh-sdk acbf80ad910a (go.mod and go.sum only; module.json unchanged). **Quick fix vs thorough fix:** quick: this hand pin, which the operator allowed for this group one last time. Thorough: ADR 0573 §2 and §3, every module built against the latest published mesh-sdk and a publish rebuilding its dependents (issue 1585), next after this delivery. Chosen: quick now, since the group's delivery is blocked and 1585 is its own milestone. **Tests:** in modules/mesh-build-go, `gofmt -l`, `go vet ./...`, `go vet -tags integration ./...`, `go test ./...` and `go mod verify` are clean. **After the merge:** route-proxy stays held on ace and novox (assigner_put hold, 12:07) until the new provisioner runs healthy, because the new route-proxy serves only from plan contributions the old provisioner does not write. Reviewed-by: rev-buildgo@shanks at b8f62cd2accb83d5ed09552ede620fff4857dedc

mesh-tools added 1 commit 2026-10-31 11:10:44 +00:00

Build mesh-build-go against the group's mesh-sdk acbf80a, so it accepts a manifest that removes the ASSIGNMENTS stream and the catalogue's modules of feat/072-moves build (issue 774)

mesh/delivery merged: source.main moved to novox/mesh-catalog@2ff7ef3a52d8

Details

mesh/check checking b8f62cd2accb on 2ff7ef3a52d8

b8f62cd2ac

The build module checks every manifest with the mesh-sdk compiled into it. At a37181261c24 that copy did not know
the removal ASSIGNMENTS, so nats's manifest was refused at 11:45 and 11:48 and the catalogue's members of the group
(the vault, the provisioner and the rest) never built. A hand pin, allowed for this group one last time; issue 1585
makes every dependent follow a published mesh-sdk.

mesh-tools commented

2026-10-31 11:10:47 +00:00

Delivery novox/mesh-catalog@b8f62cd2accb — merged since 2026-10-31T11:18:55Z

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

Transitions

2026-10-31 11:10 (new) → proposed (announced): novox/mesh-catalog#580's head announced
2026-10-31 11:10 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-31 11:18 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-catalog@b8f62cd2accb` — **merged** since 2026-10-31T11:18:55Z **Source** — source.main moved to novox/mesh-catalog@2ff7ef3a52d8. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-10-31 11:10 (new) → proposed (announced): novox/mesh-catalog#580's head announced - 2026-10-31 11:10 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-31 11:18 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 2ff7ef3a52 into main

2026-10-31 11:18:53 +00:00

mesh-tools deleted branch fix/build-go-sdk-assignments

2026-10-31 11:18:53 +00:00

jschoubben referenced this issue from a commit

2026-10-31 21:50:44 +00:00

disk-load and artifact-store-tools build on the current mesh-sdk, so they accept nats's manifest again (issue 1952)

mesh-tools referenced this pull request

2026-10-31 22:03:08 +00:00

disk-load builds on the current mesh-sdk, so it accepts nats manifest again (issue 1952) #583

Sign in to join this conversation.