release: prepare 0.9.1 with Apple Developer ID signing - #130
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.
Prepare 0.9.1 with a required Developer ID signature and Apple notarization. The release job uses the protected signing environment, selects the project certificate by SHA-1, and stops on build or notarization failures. Local development can still use its existing self-signed identity.
Remove the unsigned-install warnings from both READMEs and update the release instructions. The cask version, checksums and quarantine workaround will be updated together after the new assets exist.
Validation: local universal Release build succeeded at version 0.9.1; app and share extension match the Nifro certificate, strict signature verification passed. Workflow and shell syntax checks passed. Apple notarization awaits credentials; this PR does not publish a release.