Repository navigation
docs: distinguish active and frozen legacy update feeds - #2432
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
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 merge-policy risk table still describes
docs/appcast.xmlas the active feed and saysSUFeedURLpoints at main. Document the current configuration: the committed file is the frozen legacy feed for older installs, while currentSUFeedURLselects the latest GitHub release’sappcast.xmlasset. Keep the legacy feed’s owner-path classification unchanged.Verified against
Info.plist, the existing freeze record and release artifact plumbing. Only the feed-location explanation changes; no merge permission, workflow, release surface or adjacent design-reference edits. Independent full single-hunk/source review againstorigin/main: GREEN from the coordinator before commit.Validation on
47a53d066: all three mapped documentation checks passed with clean/stable source; preflight passed;verify-change.shreported no applicable app check. The required release-impact full QA bench was explicitly BLOCKED before execution with exit 3 by a reviewed invocation guard. Exact-head full-bench proof remains pending. No native app or release-asset fetch, workflow dispatch or publication occurred.This extracts only DOCS-6’s factual feed correction from broad pending #2336, which remains untouched and unmerged. DOCS-7’s design references stay separate. Reconcile this explanation once during integration. No merge requested.