A group's check names every member at its head, also one that publishes no package yet (issue 1921) #159

2026-11-05T22:46:04Z

mesh-tools commented

2026-11-05 22:46:04 +00:00

A delivery group's check or try gave a member's head only to packages already published, so a group adding a new package of a member (mesh-contracts' nested modules, its trunk holding only a README) built against a latest version that does not exist: try try-1793917436885989079 failed so for mesh-contracts, mesh-host and mesh-tools (issue 1921 note 44).

The checker's packagesOf now names every other member with a full head under its repository's root module path when no package of it is named; the build module's askedFor already takes a repository's head from any package of it. Every mesh package stays at the zero version (ADR 0573 §2, §4). No fingerprint changes: the indexer computes a candidate's versions itself.

Quick fix (rejected): replace the three modules by hand. Thorough fix (chosen): every member is named, published or not, for a check and a try alike; this is the second gap of the zero-version resolution (the first was mesh-catalog #617).

Group with mesh-catalog's branch of the same name (the build module resolves a repository's own nested modules from its tree).

Tests: a third bench in TestAGroupMemberIsBuiltAgainstTheSDKMembersHeadWhateverItsGoModNames, failing without the new loop; no new test function (mesh-delivery is over its budget).

Reviewed-by: mesh-code-reviewer@shanks at 261f8d54f7

https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

A delivery group's check or try gave a member's head only to packages already published, so a group adding a new package of a member (mesh-contracts' nested modules, its trunk holding only a README) built against a latest version that does not exist: try try-1793917436885989079 failed so for mesh-contracts, mesh-host and mesh-tools (issue 1921 note 44). The checker's packagesOf now names every other member with a full head under its repository's root module path when no package of it is named; the build module's askedFor already takes a repository's head from any package of it. Every mesh package stays at the zero version (ADR 0573 §2, §4). No fingerprint changes: the indexer computes a candidate's versions itself. Quick fix (rejected): replace the three modules by hand. Thorough fix (chosen): every member is named, published or not, for a check and a try alike; this is the second gap of the zero-version resolution (the first was mesh-catalog #617). Group with mesh-catalog's branch of the same name (the build module resolves a repository's own nested modules from its tree). Tests: a third bench in TestAGroupMemberIsBuiltAgainstTheSDKMembersHeadWhateverItsGoModNames, failing without the new loop; no new test function (mesh-delivery is over its budget). Reviewed-by: mesh-code-reviewer@shanks at 261f8d54f7ffd2bc10d01f3e189fdbd96433d1b5 https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i

mesh-tools added 2 commits 2026-11-05 22:46:04 +00:00

A check names a group member that publishes no package yet at its head by its root module path (issue 1921) 643ec7cd91

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

Fold the unpublished-member test into the group member's pins test (test budget, issue 1921)

mesh/check being carried to 261f8d54f7ff on cd01f1c196d8 | from c0e5bc2834fe, mesh-catalog df8168f4843f

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

Details

mesh/delivery-group group fix/1921-zero-pins-own-packages merged: every member is merged

Details

261f8d54f7

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

mesh-tools commented

2026-11-05 22:46:10 +00:00

Delivery novox/mesh-delivery@261f8d54f7ff — merged since 2026-11-05T23:00:46Z

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

Group fix/1921-zero-pins-own-packages: novox/mesh-catalog@7a5eef32e7, novox/mesh-delivery@261f8d54f7

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

Transitions

2026-11-05 22:46 (new) → proposed (announced): novox/mesh-delivery#159's head announced
2026-11-05 22:46 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-05 23:00 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@261f8d54f7ff` — **merged** since 2026-11-05T23:00:46Z **Source** — source.main moved to novox/mesh-delivery@cd01f1c196d8. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves. **Group** `fix/1921-zero-pins-own-packages`: novox/mesh-catalog@7a5eef32e772, novox/mesh-delivery@261f8d54f7ff - composed together: pass — the checker's verdict at the members' heads (66ab5396453b) **Transitions** - 2026-11-05 22:46 (new) → proposed (announced): novox/mesh-delivery#159's head announced - 2026-11-05 22:46 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-05 23:00 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 cd01f1c196 into main

2026-11-05 23:00:43 +00:00

mesh-tools deleted branch fix/1921-zero-pins-own-packages

2026-11-05 23:00:43 +00:00

jschoubben referenced this issue from a commit

2026-11-05 23:19:15 +00:00

Merge main (#159: packagesOf names every other member at its head) into the registry milestone (issue 1966)

mesh-tools referenced this pull request

2026-11-06 01:00:47 +00:00

Every build at a group's heads names every member; the node-engine beside a group's check is its member (issue 1921) #160

Sign in to join this conversation.