max / balanced_breakfast

Drop windows/x86_64 as a Bento target Bento cannot release it. The Windows checkout is at a Windows path while an app declares one unix repo, so the release preflight pins every host with a path windows-x86 does not have and fails on the first git command. Collect would strand the artifact anyway: the sync plane is rsync and the host has none. Declaring a target that cannot be released is worse than not declaring it. The recipe stays. GoingsOn e9855484 is what setting the host up costs; f05bdb85 is the restore.

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

Author: Max Johnson <me@maxj.phd> · 2026-08-06 22:58 UTC

Signed with PGP, not checked

Commit: b130f59f26eb78d89d764d3f53972991008cca4c

Parent: 85fcd14

1 file changed, +8 insertions, -1 deletion

M bento.toml +8 -1

			@@ -11,4 +11,11 @@
11	11
12	12		# macOS/iOS omitted until BB gains Developer ID signing + notarization infra;
13	13		# only linux + windows recipes exist today.
14		-	targets = ["linux/x86_64", "linux/aarch64", "windows/x86_64"]
	14	+	#
	15	+	# windows/x86_64 is dropped, not forgotten. The Windows checkout lives at a
	16	+	# Windows path while an app declares one unix `repo`, so the daemon's release
	17	+	# preflight pins every host with a path windows-x86 does not have and the build
	18	+	# fails on its first git command. Declaring a target Bento cannot actually
	19	+	# release is worse than not declaring it. dist/recipes/windows.rhai stays for
	20	+	# when the host is set up properly. See GoingsOn `f05bdb85`.
	21	+	targets = ["linux/x86_64", "linux/aarch64"]