The checker lays every repository a build requires beside it, and says a try's end (issue 1921, issue 1966) #161

2026-11-06T09:35:52Z

mesh-tools commented

2026-11-06 09:35:52 +00:00

A small release ahead of the registry milestone's delivery group (issue 1966), so the checker that judges the group's next try carries these two fixes (the operator's choice, 2026-11-06 10:30 CET).

Every repository a build requires lies beside it (66cf82e7, 29c525f4): besideFor reads each sibling's go.mod and places every repository it requires at the zero version. The 4th group try failed because the node-engine's composer fetched mesh-contracts from the network (the third failure of the zero-version kind; fixed as a kind, not by a named rule). Test: TestACatalogueChangeHasTheCatalogueBesideItAtItsTrunk, fails without it.
A try's end is said (d58b7172): the end a try run writes came back on the key's watch, Put cancelled the run's context while it said the end, so try.ended was never said and the indexer kept the try's candidate. The end is said on context.WithoutCancel. Test: TestATryIsJudgedAsAGroupsCheckAndOwesTheForgeNothing, fails without it.

Quick and thorough: the thorough form of the first fix is taken (derived from go.mod). The kind behind this release (a group that changes the checker is judged by the running checker, the second time a release had to go first) is noted on issue 1966 note 56 for its own record and work.

No module.json changed, so the manifest validator owes no verdict. No test function added (checker: 135 unit, 8 integration).

Reviewed-by: mesh-code-reviewer@shanks at d58b717243

https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

A small release ahead of the registry milestone's delivery group (issue 1966), so the checker that judges the group's next try carries these two fixes (the operator's choice, 2026-11-06 10:30 CET). - **Every repository a build requires lies beside it** (66cf82e7, 29c525f4): besideFor reads each sibling's go.mod and places every repository it requires at the zero version. The 4th group try failed because the node-engine's composer fetched mesh-contracts from the network (the third failure of the zero-version kind; fixed as a kind, not by a named rule). Test: TestACatalogueChangeHasTheCatalogueBesideItAtItsTrunk, fails without it. - **A try's end is said** (d58b7172): the end a try run writes came back on the key's watch, Put cancelled the run's context while it said the end, so try.ended was never said and the indexer kept the try's candidate. The end is said on context.WithoutCancel. Test: TestATryIsJudgedAsAGroupsCheckAndOwesTheForgeNothing, fails without it. Quick and thorough: the thorough form of the first fix is taken (derived from go.mod). The kind behind this release (a group that changes the checker is judged by the running checker, the second time a release had to go first) is noted on issue 1966 note 56 for its own record and work. No module.json changed, so the manifest validator owes no verdict. No test function added (checker: 135 unit, 8 integration). Reviewed-by: mesh-code-reviewer@shanks at d58b717243129b4090c62b060137098b07ec7485 https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-tools added 3 commits 2026-11-06 09:35:53 +00:00

A catalogue change has every repository the node-engine's composer requires beside it (issue 1921, issue 1966) 66cf82e7b6

mesh-build-go's composer test builds the node-engine's composer from what lies beside, with nothing fetched; with mesh-sdk
and the node-engine alone, its zero-version requirements on mesh-contracts (and mesh-delivery, mesh-networking) were looked
up on the network and the group's fourth try failed. The quick fix, chosen: the catalogue's beside rule names them. The
thorough fix, left: besideFor derives a built sibling's siblings from its go.mod's zero-version requirements.

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

A sibling's own siblings come from its go.mod's zero-version requirements, so no beside rule can lack one (issue 1921) 29c525f48d

The third failure of the kind (tries 1, 3, 4): a sibling a test builds, the node-engine's composer, needs every repository it requires at the zero version beside it. besideFor now reads each sibling's root go.mod through the forge and places those repositories as any sibling is placed; the catalogue's rule names only what its tests read themselves.

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

A try's end is said on a context its own stop does not cancel (issue 1921)

mesh/check being carried to d58b71724312 on 2d201f781ced | from 205a3b37501f

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

Details

d58b717243

The end a run writes comes back on the key's watch, where Put stops the run's context and leaves the saying to the run, so the end was never said and the indexer kept the try's candidate. The group try's unit test now echoes the end on the watch while the run says it.

Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-tools commented

2026-11-06 09:35:59 +00:00

Delivery novox/mesh-delivery@d58b71724312 — merged since 2026-11-06T09:41:20Z

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

Transitions

2026-11-06 09:35 (new) → proposed (announced): novox/mesh-delivery#161's head announced
2026-11-06 09:35 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-11-06 09:41 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-delivery@d58b71724312` — **merged** since 2026-11-06T09:41:20Z **Source** — source.main moved to novox/mesh-delivery@2d201f781ced. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Transitions** - 2026-11-06 09:35 (new) → proposed (announced): novox/mesh-delivery#161's head announced - 2026-11-06 09:35 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-11-06 09:41 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 2d201f781c into main

2026-11-06 09:41:18 +00:00

mesh-tools deleted branch fix/1966-checker-before-group

2026-11-06 09:41:18 +00:00

jschoubben referenced this issue from a commit

2026-11-06 10:07:06 +00:00

Merge mesh-delivery's trunk (the checker release #161) into the registry group

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-delivery#161