From 3cf7da94fe15224d51cdce76ed8a13aefb9dc535 Mon Sep 17 00:00:00 2001 From: TerrifiedBug Date: Mon, 5 Oct 2026 16:33:40 +0100 Subject: [PATCH] Ask SwiftPM where the release binary is build-release.sh copied .build/arm64-apple-macosx/release/yap. On a toolchain that lays the build out under .build/out/Products/Release that path still held a binary from a month ago, so a local build would have packaged the stale one without a word. Use --show-bin-path. Claude-Session: https://claude.ai/code/session_01TG4DEV5UyCPRFegrkNK3oE --- scripts/build-release.sh | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/scripts/build-release.sh b/scripts/build-release.sh index e50af00..93ae86d 100755 --- a/scripts/build-release.sh +++ b/scripts/build-release.sh @@ -25,7 +25,11 @@ VERSION="${VERSION:-0.1.0}" APP_IDENTITY="${APP_IDENTITY:-}" NOTARY_PROFILE="${NOTARY_PROFILE:-}" -BUILD_BIN="$ROOT/.build/arm64-apple-macosx/release/yap" +# Asked, not assumed: SwiftPM puts the product under +# .build/arm64-apple-macosx/release on one toolchain and .build/out/Products/ +# Release on another, and a hardcoded path shipped a stale binary from the +# other layout without a word. +BUILD_BIN="$(swift build -c release --arch arm64 --show-bin-path)/yap" ENTITLEMENTS="$ROOT/packaging/yap.entitlements" PLIST_TEMPLATE="$ROOT/packaging/Info.plist" ICON="$ROOT/packaging/yap.icns"