Refine language readiness warnings for 2.10.0 - #19
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.
Finalize the Quick Setup readiness indicator before releasing 2.10.0. An installed alternative mode is usable, but it must not appear as full readiness of the selected mode.
Validation: 244 macOS app tests passed, including readiness selection and stale-response checks. Live availability for English → Finnish reported low latency unsupported and high fidelity installed. Catalog and release-note checks passed; PR CI passed.
This is finishing work within the new 2.10.0 setup feature, not a separate released-user fix in the changelog. The full release inventory remains based on v2.9.1 through this candidate, as summarized in #18.
Released as v2.10.0, build 33, from merge commit
bdb5db0. Release and site deployment succeeded. Public DMG signing/notarization, Sparkle signature and key continuity, legacy/current feeds, Homebrew checksum, and five localized sites were independently verified. VM smoke checks covered existing configuration retention and fresh-install Quick Setup.