chore: separate mac binary #2198
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
hiento09
force-pushed
the
feat/separate-mac-binary
branch
3 times, most recently
from
dffa316 to
07b6111
Compare
vansangpfiev
approved these changes
Apr 10, 2025
hiento09
force-pushed
the
feat/separate-mac-binary
branch
from
07b6111 to
c89a2bd
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Describe Your Changes
Fixes Issues
Self Checklist
This pull request enhances the macOS build workflow by adding steps to handle separate binaries for different architectures (arm64 and amd64). The most important changes include adding code signing, notarizing, packaging, and uploading artifacts for these separate binaries.
Enhancements to macOS build workflow:
arm64andamd64) in thejobs:section of.github/workflows/template-build-macos.yml.quillin thejobs:section of.github/workflows/template-build-macos.yml.arm64andamd64architectures.actions/upload-artifact@v4.actions/[email protected].