Repository navigation
Release ClassicSpeech 2.01: updater-only stable/dev channels - #43
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.
Authorized stable 2.01 release preparation from main 41d6ee3. Backports only updater runtime/config/Advanced UI from fca9422, with focused tests and updater guide hunks. Adds versioned 2.01 notes/changelog and package source provenance; existing pinned dev publisher is byte-identical. No rolling development notes machinery or other development speech/UI behavior is imported. Local NVDA-master venv: 33 harnesses, 770 tests, zero failures/skips; Python compilation, actionlint and diff checks pass. Byte audit preserves all baseline runtime outside the three updater integration files plus one new channel module. Live NVDA installation/keyboard/speech acceptance not performed; no runtime or configuration was touched. Release publication follows exact-SHA CI, merged-main CI and inspection of the explicitly versioned CI artifact.