fix(updater): pin release signing identity - #66
Merged
Conversation
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.
Description
Fixes macOS updates failing after download because release builds could be signed with a different designated requirement. The release command now explicitly selects the verified local signing identity instead of relying on an optional environment variable.
Key Changes
yarn disttoAgentBar Local Code SigningVerification & Testing
yarn distcodesign --verify --deep --strict --verbose=2 release/0.1.4/mac-arm64/SkillLedger.app49EF1856F36B8E839262AFB52E862F58AB49C2CEEnvironment-specific verification: one-time manual migration is required for existing ad-hoc-signed installs.
Impact & Risk
Existing ad-hoc-signed builds cannot self-update across the signature boundary; after one manual install, future builds retain a stable signing requirement. No database migrations or environment variables.