Skip to content

ci: assert the Developer ID identity imported - #8

Merged
TerrifiedBug merged 1 commit into
mainfrom
ci/assert-signing-identity
Aug 27, 2026
Merged

ci: assert the Developer ID identity imported#8
TerrifiedBug merged 1 commit into
mainfrom
ci/assert-signing-identity

Conversation

@TerrifiedBug

Copy link
Copy Markdown
Owner

security find-identity -v -p codesigning is informational: it exits 0 even when it prints 0 valid identities found. A .p12 that imports but whose chain does not validate on the runner would pass the import step and fail later, confusingly, inside build-release.sh.

This matters here because the shipped p12 was produced by SecItemExport rather than a Keychain Access GUI export, which is a different code path for whether the Developer ID intermediate is bundled.

Now the step captures the listing, echoes it, and fails unless APP_IDENTITY appears in it. Covers both "no identities" and "wrong identity".

security find-identity exits 0 even when it finds "0 valid identities",
so a p12 that imports but whose chain does not validate on the runner
sailed past the import step and failed deep inside build-release.sh.
Grep the identity out of the listing instead.
@TerrifiedBug
TerrifiedBug merged commit a041ba8 into main Aug 27, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant