Skip to content

Derive dev bundle ID from git branch#14

Merged
rosslazer merged 1 commit intomainfrom
nick/dev-bundle-per-worktree
Apr 28, 2026
Merged

Derive dev bundle ID from git branch#14
rosslazer merged 1 commit intomainfrom
nick/dev-bundle-per-worktree

Conversation

@nickdirienzo
Copy link
Copy Markdown
Collaborator

Summary

  • Local builds now produce a per-branch bundle ID (ai.miragesecurity.flight.dev.<slug>) and display name (Flight (<branch>))
  • Each worktree gets fully siloed Application Support, Preferences, and Keychain data — so the released Flight in /Applications and any number of in-progress dev builds can run side-by-side without clobbering each other
  • Detached HEAD or non-git checkouts fall back to ai.miragesecurity.flight.dev / Flight (dev)
  • Production CI is unaffected: release.yml explicitly sets FLIGHT_BUNDLE_ID=ai.miragesecurity.flight, which short-circuits the branch logic and skips the display-name override

Test plan

  • ./build.sh on this branch produces a bundle with CFBundleIdentifier=ai.miragesecurity.flight.dev.nick-dev-bundle-per-worktree
  • Open the resulting Flight.app and verify it shows as Flight (nick/dev-bundle-per-worktree) in dock and Finder
  • Released Flight in /Applications is unaffected — separate prefs, separate Application Support
  • CI release run (post-merge) still produces an app signed and notarized as ai.miragesecurity.flight

🤖 Generated with Claude Code

Local builds now get a per-branch bundle ID (and display name) so that
worktrees don't clobber each other's Application Support, Preferences,
and Keychain data — and so a released Flight in /Applications stays
fully siloed from any in-progress dev build.

Production CI is unaffected: release.yml explicitly sets
FLIGHT_BUNDLE_ID, which short-circuits the branch logic.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@rosslazer rosslazer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@rosslazer rosslazer merged commit f124c52 into main Apr 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants