release: v4.7.2 - #209
Merged
Merged
Conversation
Eight version anchors bumped together, CHANGELOG's [Unreleased] section closed as [4.7.2]. The CHANGELOG needed more than a heading change. Four PRs merged since 4.7.1 and only two of them (#207, #208) had entries — #203's twelve user-facing fixes, the largest of the four at 83 files, were absent entirely, as was #206's README parity work. A release note that omits the biggest thing in the release is worse than a short one. Written from the commit messages, not from the PR titles. Deliberately NOT listed: #204 (CodeQL alerts in a test file and a build script) and #205 (a Windows test-cleanup race). Neither is reachable by an installed user, and listing a fix for something they never experienced reads as a defect they should worry about — the mistake the v4.6.0 notes made. node scripts/check-version-coherence.mjs exit=0, all 8 agree node scripts/run-tests-isolated.mjs exit=0 Test Files 188 passed (188) Tests 2592 passed (2592) node scripts/check-doc-claims.mjs exit=0
…uages Both translations were structurally complete after #206 but still read as English wearing another language's words: em-dash clauses carried over verbatim, stacked modifiers, and single sentences running four clauses deep. That fails the project's own plain-language bar, which assumes a reader without a university degree and asks for short sentences over nested ones. Rewritten, not re-translated. The three-part 'what it does' paragraph and the 'repeats work' paragraph became lists in both languages, because that is what those sentences were pretending to be. German lexical fixes: 'verdrahtet' (a literal rendering of 'wired') to 'eingerichtet', and 'die Constraint' to 'die Einschränkung'. NOT changed: 'Speicher' stays, all 19 occurrences. 'Gedächtnis' is arguably the better word for memory-as-recollection, but the file has already settled on the anglicism 'Memories' (21 uses) with 'Speicher' as the mass noun, and a 19-site terminology swap is a decision a native speaker should make, not one I should slip into a release commit. three-way structure: 19 '##', 15 '###', 30 code fences — identical node scripts/check-doc-claims.mjs exit=0 no simplified-Chinese characters
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.
Version bump + release notes for 4.7.2. Nothing else — no behaviour change lands in this PR.
Version anchors
All eight bumped together and verified by
check-version-coherence:The CHANGELOG needed more than a heading change
Four PRs merged since 4.7.1 and only two of them had entries. #203 — the largest at 83 files, with twelve user-facing fixes — was absent entirely, as was #206's README parity work. A release note that omits the biggest thing in the release is worse than a short one, so those were written from the commit messages rather than the PR titles.
Deliberately not listed: #204 (CodeQL alerts in a test file and a build script) and #205 (a Windows test-cleanup race). Neither is reachable by an installed user, and listing a fix for something they never experienced reads as a defect they should worry about.
Also in this PR: the two translated READMEs
Structurally complete since #206, but they still read as English wearing another language's words — em-dash clauses carried over verbatim, stacked modifiers, single sentences running four clauses deep. Rewritten, not re-translated; two paragraphs that were pretending to be lists became lists.
German lexical fixes:
verdrahtet→eingerichtet,die Constraint→die Einschränkung.Speicherdeliberately left alone at all 19 sites — a terminology swap is a native speaker's call, not something to slip into a release commit.Pre-release checks
Three-way README structure verified identical: 19
##, 15###, 30 code fences. No simplified-Chinese characters.After merge,
npm run release:finishcreates the tag and GitHub Release in one call, which triggerspublish-npm.yml.