build-release: build Lately iOS in its own Bazel invocation #45

Merged

founder merged 1 commit from ios-joint-build-lately into main

2026-08-16 09:32:53 +00:00

founder commented

2026-08-16 09:32:47 +00:00

Owner

After #44 (Lately iOS 18 vs key.store iOS 15) the joint bazel build of both apps transitions them to distinct configurations and Bazel clears the bazel-bin symlink, so APPLE_BAZEL_ARTIFACT went missing in run 17148. Lately’s IPA is built by build-lately-ios-release-ipa in its own invocation regardless; drop it from the joint build.

🤖 Generated with Claude Code

After #44 (Lately iOS 18 vs key.store iOS 15) the joint `bazel build` of both apps transitions them to distinct configurations and Bazel clears the `bazel-bin` symlink, so `APPLE_BAZEL_ARTIFACT` went missing in run 17148. Lately’s IPA is built by `build-lately-ios-release-ipa` in its own invocation regardless; drop it from the joint build. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

founder added 1 commit

2026-08-16 09:32:47 +00:00

build-release: build Lately iOS in its own Bazel invocation

Release: If Needed / Check (Release Needed) (push) Successful in 5s

Details

Deploy: API / Deploy (API) (push) Has been cancelled

Details

Deploy: Web / Deploy (Web) (push) Has been cancelled

Details

Release: Signing Preflight / Release (Signing Preflight) (push) Successful in 58s

Details

cefa64beb1

Since #44 Lately iOS targets iOS 18 while key.store targets iOS 15. Asking
Bazel for both applications in one invocation makes them transition to
distinct configurations, and Bazel then clears the bazel-bin convenience
symlink -- so the workflow's bazel-bin/key_store_ios_release.ipa path went
missing (run 17148). The Lately IPA is produced by
build-lately-ios-release-ipa in its own invocation anyway; drop it from the
joint build.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>