Repository navigation
[ty] Use shared release signing actions - #4652
Merged
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.
ty's release pipeline publishes unsigned macOS and Windows binaries. Add shared actions to sign Windows binaries and sign and notarize macOS binaries, then reassemble wheels and GitHub archives with updated
RECORDentries and checksums before publication. Remove the stalepowerpc64-unknown-linux-gnurelease target so signing preparation matches the build matrix. Use 16 KiB code-signature pages for ARM64 macOS binaries to reduce signature-verification work. Signing uses the protectedreleaseenvironment and the repository'smainworkflow, including release dry runs.