Repository navigation
docs: scope the staged Sparkle recipe to its pinned repair - #2390
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 1.1.68 → 1.1.69 staged updater recipe can look like a current release checklist. Add an explicit version scope, point current release work to its owning docs, and identify the still-executable Swift CI input/job and fixed candidate. Preserve the original hosted and manual procedures.
check.sh passed all 3 mapped checks on 45557e2; preflight passed. verify-change.sh selected no app checks. Independent full diff review against fetched origin/main: GREEN. No native harness, workflow dispatch, release action or full QA bench ran. Full release-impact bench verification remains deferred to an isolated validation branch while test-fixture isolation work is pending.
The index row overlaps the pending row in #2336. Keep one version-scoped entry when integrating the two PRs. Draft only; no archive or retirement decision, and no merge requested.