ci: verify macOS signatures and upload packaged artifacts - #2484
Merged
flyinghead merged 1 commit intoSep 13, 2026
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
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.
Verify the installed macOS app’s signatures, including nested code and all architectures, before packaging or publishing.
Move macOS (
apple-darwin) and MinGW Windows (x86_64-w64-mingw32) packaging before GitHub artifact upload.Use
archive: falseso GitHub and S3 receive byte-identical ZIPs without an extra archive wrapper.Use
packagePathto create platform-named copies outsideartifact/binfor GitHub’s artifact naming.S3 continues uploading only
artifact/bin, preserving its existing filenames and paths.Other builds retain their existing upload behavior.
upload-artifact@v7also supports uploading Linux’s AppImage directly; let me know if you’d prefer to include that alignment in this PR.