A merge check of its own (hq ADR 0238) #4

2026-10-06T20:51:46Z

mesh-admin commented

2026-10-06 20:51:46 +00:00

merge-check.sh (TypeScript toolchain, whose Node is this module's NODE_BASE): the three images' own builds — server, client, admin client — installed from their lock files and built, before the merge instead of after. Nothing started (the server wants its stores); no tests exist. Into nox-mesh, the branch the mesh builds from. Tested in the emulated check environment: passes (~70s).

`merge-check.sh` (TypeScript toolchain, whose Node is this module's NODE_BASE): the three images' own builds — server, client, admin client — installed from their lock files and built, before the merge instead of after. Nothing started (the server wants its stores); no tests exist. Into `nox-mesh`, the branch the mesh builds from. Tested in the emulated check environment: passes (~70s).

mesh-admin added 1 commit 2026-10-06 20:51:46 +00:00

Check the photo application before a change merges into what the mesh builds (hq ADR 0237) 33ab118bcc

The repository's layer of the mesh's merge check (mesh/repo-check): the three images'
own builds — server, client and admin client installed from their lock files and built —
before the merge instead of after it.

mesh-admin merged commit 31c0c5e6bc into nox-mesh

2026-10-06 21:00:43 +00:00

mesh-admin deleted branch feat/a-merge-check-of-its-own

2026-10-06 21:00:43 +00:00

mesh-admin commented

2026-10-06 23:11:31 +00:00

Delivery novox/photos@31c0c5e6bcad — delivered since 2026-10-06T23:05:28Z

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/photos#4 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
2026-10-06 23:05 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's plans go
2026-10-06 23:05 delivering → delivered (done): its walk is done: 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/photos@31c0c5e6bcad` — **delivered** since 2026-10-06T23:05:28Z **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/photos#4 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on - 2026-10-06 23:05 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's `plans go` - 2026-10-06 23:05 delivering → delivered (done): its walk is done: 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`.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/photos#4