max / alloy

Move SHOP_REV onto the makeover the console already takes Yesterday's lock settle took makeover 2.5.1 here and left shop's lock on 2.5.0. Both build --locked in the one rust stage against one registry, so both landed, and STEP 17 refused to guess which themes directory was the desktop's. alloy main has not built since. shop@7861672 takes 2.5.1, and this points at it. build/check-rust-stage.sh is green on the pair; it is also what found this, which is the case its header asks for it to be run in. The nightly rust-stage cell was supposed to be the backstop and did not report this. Whether it ran green on a tree that does not build, or did not run, is GoingsOn alloy problem c204d7d7.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Max Johnson <me@maxj.phd> · 2026-08-14 18:00 UTC

Signed with PGP, not checked

Commit: 343f974657683fd08f6d5cadc4ec1862421b0b7d

Parent: d108211

1 file changed, +1 insertion, -1 deletion

M Containerfile +1 -1

			@@ -94,7 +94,7 @@
94	94		# alone, so console edits — the thing that changes most often — reuse it
95	95		# instead of rebuilding a terminal that did not change. Moving it below the
96	96		# `COPY crates/` would defeat the dependency-cache split that follows.
97		-	ARG SHOP_REV=183ce3d0d6698ef34be98b7dd9d474eb60fbfb15
	97	+	ARG SHOP_REV=7861672f0a622d426d82ea74e3a13ab09d0ce829
98	98
99	99		# Does the remote have anything to build from, before anything expensive runs.
100	100		#