Repository navigation
Publish a notarized release from a tag - #4
Merged
Merged
Conversation
- Add release.yml, which runs on a v* tag and checks the tag against MARKETING_VERSION before building, so a release cannot carry a version the app does not report - Import the Developer ID certificate into a temporary keychain and let build.sh find it, keeping signing out of the workflow file - Add Scripts/notarize.sh, used by both the workflow and a local run; it picks the notarytool credentials from the environment - Package the app after stapling and publish it as Blip-<version>.zip with generated notes - Document the release path and the six repository secrets in the README Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Summary
Pushing a
v*tag now builds, notarizes, and publishes the app as a GitHub release.release.ymlchecks the tag againstMARKETING_VERSIONin project.yml before building, so a release cannot carry a version the app does not reportbuild.sh, so nothing about signing lives in the workflow fileScripts/notarize.shsubmits the app, staples the ticket, and verifies the result withstapler validateandspctl. The workflow and a local run use the same script; the notarytool credentials come from the environmentBlip-<version>.zipopens on another Mac without Gatekeeper blocking itThe notarization path was verified locally first: submission accepted, ticket stapled, and
spctlreportsaccepted / source=Notarized Developer ID.🤖 Generated with Claude Code