A try accepts a mesh-sdk pin that is the head of mesh-sdk's branch of the same name, so a group's members can be tried before its pull requests (issue 1921) #37

2026-10-24T14:47:41Z

mesh-tools commented

2026-10-24 14:47:41 +00:00

Issue 1921 (narrow part, note 15), met twice on 2026-10-24 (the R4g finish group, then R6): a try of a repository whose go.mod pins a mesh-sdk commit from the group's own branch was refused ('neither on mesh-sdk's trunk nor the group's head (the group has no mesh-sdk pull request)'), so its integration tests ran first in the group's merge check, one fault per round. Now, in a TRY only, a pin not on the trunk is accepted when the tried head is the head of a branch (not main) whose namesake branch in mesh-sdk has a head matching the pin; the try's line says 'pin accepted: head of mesh-sdk '. Merge checks keep today's rule. Branches are read with gitea_list_branches over the bus (a new invoke; the bus's user list grants it in the delivery plan's grants step, no credential re-issue). Tests 1921/AC1-AC3 (AC1 fails with the try branch disabled). Try try-1792852903701147527 passed. The rest of 1921 (a full group try, every failure named) stays open.

Reviewed-by: review-1921pin@shanks at 991589fdd2
Pushed-by: lead-47@shanks

Issue 1921 (narrow part, note 15), met twice on 2026-10-24 (the R4g finish group, then R6): a try of a repository whose go.mod pins a mesh-sdk commit from the group's own branch was refused ('neither on mesh-sdk's trunk nor the group's head (the group has no mesh-sdk pull request)'), so its integration tests ran first in the group's merge check, one fault per round. Now, in a TRY only, a pin not on the trunk is accepted when the tried head is the head of a branch (not main) whose namesake branch in mesh-sdk has a head matching the pin; the try's line says 'pin accepted: head of mesh-sdk <branch>'. Merge checks keep today's rule. Branches are read with gitea_list_branches over the bus (a new invoke; the bus's user list grants it in the delivery plan's grants step, no credential re-issue). Tests 1921/AC1-AC3 (AC1 fails with the try branch disabled). Try try-1792852903701147527 passed. The rest of 1921 (a full group try, every failure named) stays open. Reviewed-by: review-1921pin@shanks at 991589fdd20a14ee51839a77fad1a2d39ced2741 Pushed-by: lead-47@shanks

mesh-tools added 1 commit 2026-10-24 14:47:42 +00:00

A try of a branch accepts a mesh-sdk pin at the head of mesh-sdk's branch of the same name, so a milestone's repositories can be tried before their pull requests (issue 1921)

mesh/delivery delivered

Details

mesh/check checking 991589fdd20a on 4c1d36c9cd7f

991589fdd2

mesh-tools commented

2026-10-24 14:47:50 +00:00

Delivery novox/mesh-delivery@991589fdd20a — delivered since 2026-10-24T15:39:44Z

Delivery plan — builds mesh-delivery-checker → novox; no bus step

tier 0: mesh-delivery-checker
novox: receives mesh-delivery-checker

Machines

mesh-delivery-checker on every machine running it: sent

Transitions

2026-10-24 14:47 (new) → proposed (announced): novox/mesh-delivery#37's head announced
2026-10-24 14:48 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-24 14:48 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-24 15:38 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-24 15:38 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-24 15:39 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-delivery@991589fdd20a` — **delivered** since 2026-10-24T15:39:44Z **Delivery plan** — builds mesh-delivery-checker → novox; no bus step - tier 0: mesh-delivery-checker - novox: receives mesh-delivery-checker **Machines** - mesh-delivery-checker on every machine running it: sent **Transitions** - 2026-10-24 14:47 (new) → proposed (announced): novox/mesh-delivery#37's head announced - 2026-10-24 14:48 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-24 14:48 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-24 15:38 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-24 15:38 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-24 15:39 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools merged commit 4c1d36c9cd into main

2026-10-24 15:37:07 +00:00

mesh-tools deleted branch fix/1921-try-same-branch-pin

2026-10-24 15:37:08 +00:00

jschoubben referenced this issue from a commit

2026-10-24 19:54:54 +00:00

Merge main into feat/r4g-finish, keeping #37's same-branch mesh-sdk pin rule beside the node-engine check's controller placing (issue 1295)

mesh-tools referenced this pull request

2026-10-24 20:06:57 +00:00

R4g finish: the composer as a job on node-build-go's check stream, merge-check.sh gone, reads-outside markers (issues 1295, 1621-1623, 1935) #35

Sign in to join this conversation.