chore: release v0.20.0 - #129
Merged
Merged
Conversation
Promote [Unreleased] to [0.20.0]: #128 closing #119 and #65 — the structural parity guard on every write path, calibrated against all 211 real source/target lecture pairs, plus the #127 docs wording fix. Minor bump: new behaviour (files can now fail that previously passed), though only when the output genuinely diverges structurally from the source — which was always a defect, just a silent one. Bump package.json/package-lock, copilot-instructions version + counts (50 suites), record the release in .dev/STATE with the operational note that the first wave may loudly fail files carrying pre-existing damage. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Release-prep PR for v0.20.0, aligning repository metadata and maintainer notes with the features shipped in #128 (structural parity guard) and #127 (CLI invocation wording).
Changes:
- Bump package version from
0.19.0→0.20.0inpackage.jsonandpackage-lock.json. - Promote the changelog entry to
## [0.20.0] - 2026-07-21and document the shipped items. - Update repository instructions/state docs to reflect
v0.20.0and the updated test/suite counts.
Reviewed changes
Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| package.json | Version bump to 0.20.0. |
| package-lock.json | Lockfile version metadata updated to 0.20.0 (root + package entry). |
| CHANGELOG.md | Adds the 0.20.0 release entry describing #128 and #127. |
| .github/copilot-instructions.md | Updates “Current Version” and test/suite counts for v0.20.0. |
| .dev/STATE.md | Records v0.20.0 as recently landed with a short operational note. |
11 tasks
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.
Minor release carrying #128 (closes #119, #65) and #127.
What ships
The structural parity guard — first item of the #120 P0 corruption-class plan. Full reasoning in the changelog entry; the operational headline for anyone watching the estate:
A sync or resync can now fail loudly where it previously succeeded silently. That happens only when the output genuinely diverges structurally from the source — a dropped
{raw}argument, a lost(label)=anchor, a re-fenced document — which was always a defect; the change is that it is now caught at write time instead of weeks later on a downstream strict build.Backlog note: files whose historical translations already carry anchor damage will fail their next sync until repaired (resync is the repair tool). The corpus dry-run suggests this population is small — one clean case found across 211 pairs, already fixed (.fr#16).
Validation
Release checklist
[Unreleased]→[0.20.0]package.json+ lockfile → 0.20.0.dev/STATE.mdupdatedv0.20.0, createv0.20, movev0, publish🤖 Generated with Claude Code