Use non-single-file macOS release packaging#184
Merged
Conversation
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
Switch macOS release builds in GitHub Actions from self-contained single-file packaging to a standard self-contained app bundle.
Why
Bug report #183 shows a macOS user hitting:
Failed to create CoreCLR, HRESULT: 0x80070008
The current release workflow packages macOS as a single-file apphost inside the app bundle. This PR changes the macOS release artifact to bundle the full publish output instead, including the runtimeconfig, deps file, managed assemblies, and native .NET runtime libraries. That removes the single-file CoreCLR extraction/startup path from the shipped macOS app.
Validation
Closes #183