Repository navigation
Unify updater behavior and shared release checks - #32
Merged
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.
The Daddy apps duplicate updater lifecycle code and use different tooling revisions. Add ContextDaddy’s dedicated Sparkle integration, public-key-only release configuration, signed-feed path and bootstrap download. Management writes and review sheets hold relaunch.
Pin candidate and protected release validation to the reviewed shared foundation at 67dcb59d289c396349244f42778dccbd2953ba41. Local CI rejects shared-source, Sparkle-version and tooling-pin drift; the shared runner additionally compares canonical copies.
Validation: the focused updater/lifecycle suites passed in all four apps (225 native tests across this change’s checks), shared foundation/release fixtures and four-app copy checks passed. ContextDaddy’s packaging and feed-routing fixtures passed; its updater-enabled local bundle launched and exposed native update controls. Public and installed-update acceptance will be verified separately during the owner-authorized release.