Skip to main content

max / makenotwork

Assert wam's health inside the deploy step, not a step of its own step() names one of a fixed set the daemon knows, so `health` aborted the run after the install had already happened: both nodes went live on 0.3.0 while the release record read failed. Assertions about a running service belong to the step that started it.
Author: Max Johnson <me@maxj.phd> · 2026-08-15 21:41 UTC
Signed with PGP, not checked
Commit: f44d18c01e5618633f751f354131464fedf86d5c
Parent: d2e908a
3 files changed, +26 insertions, -19 deletions
M wam/Cargo.lock +17 -17
@@ -1721,7 +1721,7 @@
1721 1721
1722 1722 [[package]]
1723 1723 name = "wam"
1724 - version = "0.3.0"
1724 + version = "0.3.1"
1725 1725 dependencies = [
1726 1726 "axum",
1727 1727 "chrono",
@@ -2227,22 +2227,6 @@
2227 2227 name = "synckit-config"
2228 2228 version = "0.2.0"
2229 2229
2230 - [[patch.unused]]
2231 - name = "docengine"
2232 - version = "0.7.0"
2233 -
2234 - [[patch.unused]]
2235 - name = "kberg"
2236 - version = "0.1.0"
2237 -
2238 - [[patch.unused]]
2239 - name = "ops-status"
2240 - version = "0.1.0"
2241 -
2242 - [[patch.unused]]
2243 - name = "tagtree"
2244 - version = "0.4.0"
2245 -
2246 2230 [[patch.unused]]
2247 2231 name = "quasi-axum"
2248 2232 version = "0.11.0"
@@ -2274,3 +2258,19 @@
2274 2258 [[patch.unused]]
2275 2259 name = "quasi-webview"
2276 2260 version = "0.11.0"
2261 +
2262 + [[patch.unused]]
2263 + name = "docengine"
2264 + version = "0.7.0"
2265 +
2266 + [[patch.unused]]
2267 + name = "kberg"
2268 + version = "0.1.0"
2269 +
2270 + [[patch.unused]]
2271 + name = "ops-status"
2272 + version = "0.1.0"
2273 +
2274 + [[patch.unused]]
2275 + name = "tagtree"
2276 + version = "0.4.0"
M wam/Cargo.toml +1 -1
@@ -1,6 +1,6 @@
1 1 [package]
2 2 name = "wam"
3 - version = "0.3.0"
3 + version = "0.3.1"
4 4 edition = "2024"
5 5 license = "MIT"
6 6
M wam/dist/recipes/linux.rhai +8 -1
@@ -54,7 +54,14 @@
54 54 // proportionate: putting it back and restarting is one command.
55 55 log(deploy(binary));
56 56
57 - step("health");
57 + // The health assertions live inside the deploy step rather than a step of their
58 + // own. `step()` names one of a fixed set the daemon knows (checkout, prebuild,
59 + // build, sign, notarize, staple, verify, package, publish, collect, deploy,
60 + // handoff); a "health" step aborts the run AFTER the install has already
61 + // happened, which is the worst of both -- the binary is live and the release
62 + // reads failed. Assertions about the running service belong to the step that
63 + // started it.
64 + //
58 65 // What "healthy" means is the service's business, so the recipe asserts it
59 66 // itself against the host it just restarted.
60 67 //