Skip to main content

max / balanced_breakfast

Pin the Linux release build to the tag instead of pulling the branch git pull --ff-only builds whatever main is at pull time, so each host in a multi-arch release could compile a different commit under one version. checkout_sha pins the tag and reports the commit, which the daemon's cross-host barrier then holds every host to.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-06 22:50 UTC
Signed with PGP, not checked
Commit: 85fcd147bf34e6b71b9298bab4dcfca4d6f9ab0c
Parent: 3dce1e5
1 file changed, +4 insertions, -1 deletion
@@ -16,7 +16,10 @@
16 16 let r = repo();
17 17
18 18 step("checkout");
19 - sh_ok(h, "cd " + r + " && git pull --ff-only");
19 + // Pin to the release tag v<version> (not whatever main is at pull time); the
20 + // daemon also runs this as a cross-host preflight barrier before any build.
21 + let sha = checkout_sha(h);
22 + log("pinned " + h + " to v" + v + " @ " + sha);
20 23
21 24 // Gate: no artifact is built from code that fails clippy or its tests. It runs
22 25 // on this target's own build host, so a break confined to one platform is