A merge on the forge builds what it moved, bases first #110

2026-09-28T00:59:03Z

mesh-admin commented

2026-09-28 00:59:03 +00:00

No description provided.

mesh-admin added 1 commit 2026-09-28 00:59:03 +00:00

A merge on the forge builds what it moved, bases first 525f10b858

The controller follows the forge's merges (novox/hq 04-ISSUES/131). For each
module recorded as built from that repository and branch it records the move to
the merge commit and builds it — bases first, because a module built before the
module it stands on is built against the old one and reports success, and a base
that fails stops what stands on it. Nothing is pushed here: what a finished build
does to the machines running the module stays the upgrade's decision.

Two more things the same ordering gives: `build --behind` builds bases first, and
`build --on <module>` rebuilds everything that stands on a module — the rebuild a
changed base needs, which "behind" does not see because their sources did not
move.

mesh-admin merged commit 12ed35e87d into main

2026-09-28 00:59:04 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#110