fix(release): configure Speakeasy macOS signing - #34
Merged
Conversation
danielkov
enabled auto-merge (squash)
August 27, 2026 14:44
danielkov
disabled auto-merge
August 27, 2026 14:48
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
Configure Kit’s macOS release paths to sign with the Speakeasy Developer ID identifier and document the certificate, App Store Connect key, and GitHub Actions secret setup. Require an explicit local signing identity and update the release version to 0.1.98.
Motivation
The release workflow and local scripts still used a personal code-signing identifier and an unrelated fallback identity, preventing the company-owned credentials from being the canonical release configuration.
Impact
Future macOS ARM64 releases use
com.speakeasy.kitwhen signing and notarizing. Local notarization now requiresKIT_CODESIGN_IDENTITYinstead of silently selecting an organization-specific fallback.Technical details
1Password retrieval
Use the supported
op document get --out-fileoption when materializing the temporary App Store Connect API key.Validation
Shell syntax, workflow YAML, locked Cargo metadata, and diff checks pass. An actual Kit release binary was Developer ID signed and submitted to Apple’s notary service, which returned
Accepted.