Repository navigation
release: correct 0.17.1 delivery for Alpha 1 with bundled dictionary - #258
Merged
Merged
Conversation
Lucas1479
marked this pull request as draft
October 22, 2026 17:58
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.
Correction to the previous release preparation
This is the unified release-preparation correction to merged PR #245, not a second Pi-only documentation PR. The existing
v0.17.1-alpha.0tag remains at fd17e70 and its old artifacts stay historical. The corrected candidate uses v0.17.1-alpha.1.Candidate changes
The maintainer already selected full-resource default delivery with independent updates/rollback and personal-dictionary preservation. This PR follows that direction. The resource remains 2026.10.22.1-rc2: 134,201 source rows are preserved, 462 correction records are distinguished from
original_unverifiedsource data, and existing exclusions/quality limits remain documented. This is not a claim that every reading has been manually reviewed or listened to.Qualification
Runtime/artifact qualification at 4d1127f:
Final candidate e26d204 changes only the proposed download URL and release notes. The regenerated ZIP differs only in those two files and SOURCE_MANIFEST.json; every runtime and resource member is byte-identical to the qualified archive, and every final manifest digest was rechecked. The pin/release regression subset passed another 20 tests. All 18 final-head CI checks passed on e26d204, including the required build/cpu-model-less gates, Source Release and all platform/model jobs. The previous Linux Voice attempt stalled in the Ubuntu apt mirror before Python setup and was cancelled at its existing 30-minute limit; its log is retained. No timeout, assertion or ignore was changed.
Final source ZIP SHA-256:
09f4fa30753fdf9eba39aa1a0c069e68fa85fa018b21b2eb820d1c047f7fe49b.Resource ZIP SHA-256:
a935b3adfded9022afe3b2384cebc2ef1e4023f54f48df1f9ded9ff45b896989.Alpha 1 notes · Full distribution procedure
Publication boundary
Keep this unified PR draft for release review. No new tag, Release, dictionary upload or mainline merge has been performed. The actual full-resource artifact work is Windows qualification; cloud PR jobs use explicit code-only packages and do not consume the unpublished full data ZIP. The Electron build retains the separate Python runtime contract. This round does not add human/native-speaker listening or pitch-accent sign-off, and NUL recovery is simulated damage, not physical power-loss testing.