A merge check of its own; every test on a bus of its own; git in the TypeScript toolchain (hq ADR 0238) #18

2026-10-06T20:51:38Z

mesh-admin commented

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

merge-check.sh (Go toolchain): node-tools gofmt, vet, suite under -race. The runtime's and console's tests launch bundles that import @novox/mesh-sdk (registry, no credential in a check) and are said as NOT TESTED HERE when node and that package are absent.
internal/meshtest: each test gets an embedded nats-server at the release go.mod pins (2.11.17), like mesh-controller's testbus (#97); packages run in parallel. MESH_TEST_NATS_EXTERNAL=1 keeps a person's own bus. A test holds the pin to the catalogue's bus image and, given MESH_FACTS, to the bus the mesh runs.
Dockerfile: the toolchain stage gets git (a suite reading repository history failed with spawnSync git ENOENT).

Tested with the build seat's environment emulated (Go toolchain + throwaway store/bus): passes.

- `merge-check.sh` (Go toolchain): node-tools gofmt, vet, suite under -race. The runtime's and console's tests launch bundles that import @novox/mesh-sdk (registry, no credential in a check) and are said as NOT TESTED HERE when node and that package are absent. - `internal/meshtest`: each test gets an embedded nats-server at the release go.mod pins (2.11.17), like mesh-controller's testbus (#97); packages run in parallel. `MESH_TEST_NATS_EXTERNAL=1` keeps a person's own bus. A test holds the pin to the catalogue's bus image and, given MESH_FACTS, to the bus the mesh runs. - Dockerfile: the `toolchain` stage gets git (a suite reading repository history failed with `spawnSync git ENOENT`). Tested with the build seat's environment emulated (Go toolchain + throwaway store/bus): passes.

mesh-admin added 2 commits 2026-10-06 20:51:38 +00:00

Check the tool runtime's own code before it merges, every test on a bus of its own (hq ADR 0237) 14bff5dfd7

A merge-check.sh, the repository's layer of the mesh's merge check (mesh/repo-check):
format, vet, and node-tools' suite under the race detector. The tests shared one bus and
had to run one package at a time; like the controller's (#97), each now starts a server
of its own at the release go.mod pins, held to the catalogue's bus image by a test. What
cannot run in the check — bundles that need @novox/mesh-sdk — is said as not tested.

Give the TypeScript toolchain git, for the merge checks that run in it (hq ADR 0237) b86a6ca228

A repository's own merge-check.sh may declare this toolchain, and a suite that reads a
repository's history failed with spawnSync git ENOENT. Nothing compiled here calls it.

mesh-admin merged commit 01c98db0a4 into main

2026-10-06 20:55:59 +00:00

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

2026-10-06 20:55:59 +00:00

mesh-admin commented

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

Delivery novox/mesh-tools@01c98db0a4f0 — delivered since 2026-10-06T23:05:28Z

Machines

mesh-tools on every machine running it: sent
node-tools on ace: passed — healthy 3 times over 2m14s
node-tools on the rest running it: sent

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/mesh-tools#18 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/mesh-tools@01c98db0a4f0` — **delivered** since 2026-10-06T23:05:28Z **Machines** - mesh-tools on every machine running it: sent - node-tools on ace: passed — healthy 3 times over 2m14s - node-tools on the rest running it: sent **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-tools#18 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/mesh-tools#18