fix(ci): sign macOS artifacts only on release tags#1348
Open
TimeToBuildBob wants to merge 1 commit into
Open
Conversation
Contributor
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.
Root cause
Master push run https://github.com/ActivityWatch/activitywatch/actions/runs/28720318129 fails only in the macOS
Package dmgsteps. The P12 imports, butsecurity find-identity -v -p codesigningreports0 valid identities found, so the repository signing certificate/chain is currently not usable on the runner.Branch pushes are CI signals, not release publications. They should still build DMGs, but stale signing secrets should not make every master push red. Tagged
v*releases are the place where signing/notarization must remain mandatory.Change
GITHUB_REF == refs/tags/v*in both Qt and Tauri DMG packaging steps.Verification
bash -non the changed DMG packaging shell block..github/workflows/release.ymlwith PyYAML.This should clear master CI for ordinary pushes while still surfacing the real signing-secret problem before publishing a tagged release.