Fix macOS release packaging to use proper .app bundle#51
Merged
erikdarlingdata merged 1 commit intodevfrom Mar 6, 2026
Merged
Conversation
macOS builds were shipping as flat folders of DLLs/binaries that weren't runnable. Now creates a proper .app bundle (Contents/MacOS, Contents/Resources, Info.plist) so the app is double-clickable on macOS. Also adds missing CFBundleExecutable to Info.plist and auto-syncs the plist version from the csproj at build time so it can't drift. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.appbundle structure (Contents/MacOS/,Contents/Resources/,Info.plist)CFBundleExecutablekey to Info.plist so macOS knows which binary to launchWhat users get now
Test plan
.appbundle launches🤖 Generated with Claude Code