Repository navigation
Prepare stable 2.02 Spanish translation release - #47
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.
Scope
Prepare user-authorized stable 2.02 from official main. Add short Spanish translation release notes crediting Luis Carlos, wire the active changelog, and update the packaged guide. Source version remains 0.0.0; package version is supplied by the existing workflow input. No speech code, updater policy, development features, or workflows changed.
Verification
Windows full source gate: 33 harnesses, 770 tests passed, zero skips. All 148 Python files compiled. Spanish MO translations match the PO; all 654 keys preserved against v2.01 (original MO translator header retained). Updater comparator accepts literal 2.02 and orders it after 2.01. Dirty primary presentation-presets checkout untouched; work done in isolated scratch worktree.
After merge, require main CI and separate non-publishing workflow dispatch with release_version=2.02 on exact final SHA; inspect that CI artifact before tagging and publishing.