fix(release): use dedicated keychain for cert pre-import#10
Merged
Conversation
PR #9 imported the Apple cert into login.keychain-db and then called `security set-key-partition-list -k ""` to authorize codesign access. macos-latest runners' login keychain has a non-empty password (set by the runner image), so this failed with "SecKeychainItemSetAccessWithPassword: The user name or passphrase you entered is not correct" and the whole step aborted. Switch to the same pattern tauri-action uses internally: create a fresh keychain in $RUNNER_TEMP with a freshly-generated password, import the cert there, authorize via set-key-partition-list with the known password, then add the keychain to codesign's user search list ahead of login.keychain-db. This isolates our keychain from the runner's, avoids fighting an unknown login password, and stays out of tauri-action's way when it creates its own ephemeral keychain later (codesign finds the identity in either; both have the same name). Co-Authored-By: Claude Opus 4.7 <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
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.
Summary
PR #9's pre-import step imported the Apple cert into `login.keychain-db` and called `security set-key-partition-list -k ""` to authorize codesign access. macos-latest runners' login keychain has a non-empty password (set by the runner image), so this failed with:
```
security: SecKeychainItemSetAccessWithPassword: The user name or passphrase you entered is not correct.
```
— and the whole step aborted before the sidecar build ever ran.
Fix
Use the same pattern tauri-action uses internally:
This stays out of tauri-action's way when it later creates its own ephemeral keychain — codesign finds the identity in either, both have the same name, no conflict.
🤖 Generated with Claude Code