max / makeover

Note that the release restores the branch it pinned The recipe explained why the preflight leaves the checkout detached but not that anything undoes it, because until now nothing did.

Author: Max Johnson <me@maxj.phd> · 2026-07-28 23:21 UTC

Signed with PGP, not checked

Commit: dc2ad6ce96f20f5be19e078571e858aa8fcaa936

Parent: f6f5c67

1 file changed, +5 insertions, -0 deletions

M dist/recipes/publish.rhai +5

			@@ -23,6 +23,11 @@
23	23		//
24	24		// So this step asserts the pin instead of re-doing it: HEAD must be exactly a
25	25		// tag, or the release is not coming from where it claims.
	26	+	//
	27	+	// The tree does not STAY detached: the runner records each host's branch before
	28	+	// it pins the tag and checks it back out once the build settles. It did not
	29	+	// always, and makeover shipped 2.3.0 from a checkout three commits ahead of a
	30	+	// `main` that never moved, with the published commit on no branch and no remote.
26	31		step("checkout");
27	32		sh_ok(h, "cd " + r + " && git describe --exact-match --tags HEAD");
28	33