Repository navigation
feat(settings): get beta updates from a signed feed - #3501
Merged
Merged
Conversation
… feat/beta-update-channel
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
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.
Why
There is no way to get a release before everyone else, and the update feed is an unsigned file on raw.githubusercontent.com. Step 20 of the release rewrite; it merges in the freeze window with steps 20-23.
Change
betachannel. Off again, the installed beta stays until a newer release ships.com.TablePro.updates.receivesBetaUpdates: device-local, never synced, and pinnable by a configuration profile.https://updates.tablepro.app/appcast.xmlunder the new EdDSA key, withSURequireSignedFeedandSUVerifyUpdateBeforeExtractionon.requiredInfoPlistKeysandkeysMissingDefaults, and the unusedcheck-sparkle-update-defaults.shprobe.Verified
UpdateChannelTests(new) andPreferenceKeysGuardTestspass.SparkleUpdatePreferencesTestschanged on purpose: it now holds the required-key list and pins the exact feed URL and both signing keys.Not in this PR
release.yml), so no release ships between this merge andv0.82.0-beta.1.