max / goingson

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:57 UTC

Signed with PGP, not checked

Commit: 366fe5805104a6a60d39949ea76b1ae2d64c3e50

Parent: e529dd3

1 file changed, +7 insertions, -1 deletion

M bento.toml +7 -1

			@@ -3,4 +3,10 @@
3	3		#
4	4		# The daemon's own bento.toml holds the build hosts and points at this repo.
5	5
6		-	targets = ["macos/aarch64", "ios/universal", "linux/x86_64", "linux/aarch64", "windows/x86_64"]
	6	+	# windows/x86_64 is dropped, not forgotten. The Windows checkout lives at a
	7	+	# Windows path while an app declares one unix `repo`, so the daemon's release
	8	+	# preflight pins every host with a path windows-x86 does not have and the build
	9	+	# fails on its first git command. Declaring a target Bento cannot actually
	10	+	# release is worse than not declaring it. dist/recipes/windows.rhai stays for
	11	+	# when the host is set up properly. See GoingsOn `f05bdb85`.
	12	+	targets = ["macos/aarch64", "ios/universal", "linux/x86_64", "linux/aarch64"]