docs: record 4.0.1 and 4.0.2, and prepare the 4.0.3 release - #79
Merged
Merged
Conversation
The CHANGELOG had no 4.0.1 or 4.0.2 sections: both shipped in July but only the releases page recorded them, and the [Unreleased] block still described #67 — which had already gone out in 4.0.2. So the file said the opposite of what the tags said. This adds the two missing sections (moving the #67 entry into 4.0.2 where it belongs) and writes 4.0.3 for the eight commits since: two runner-version bumps, the Dependabot/code-scanning sweep in #74, three dependency bumps and the security policy. All patch-level — no input, output or behaviour change. dist/ is unchanged: verified by rebuilding with `npm run package` against a clean `npm ci`, byte-identical to what is committed. 245 tests pass, lint clean. Signed-off-by: kurok <22548029+kurok@users.noreply.github.com>
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.
Prepares the v4.0.3 release, and repairs a CHANGELOG that had drifted from the tags.
The drift
The CHANGELOG had no
4.0.1or4.0.2sections at all — both shipped in July and were recorded only on the releases page. Worse, the[Unreleased]block still described the warm-restart registration race (#67), which had already gone out in 4.0.2. The file claimed as unreleased something that had been in users' hands for two months.This adds both missing sections (moving the #67 entry into
4.0.2, where it shipped) and writes4.0.3.What is in 4.0.3
Eight commits since v4.0.2, all patch-level — no input, output or behaviour change:
actions/runner→ 2.337.0 (#70, #75)js-yaml3.14.2→3.15.1 and least-privilege workflow permissions;undici6.28.0 (#71);brace-expansion(#72)browserslist(#77),js-yaml(#78)Also needs doing at tag time
The moving
v4tag is stale. It points atc5db9f0— the v4.0.0 docs commit — so it is three commits behind even the v4.0.0 release, and misses 4.0.1 and 4.0.2 entirely. Anyone pinning@v4has been running v4.0.0 code without the warm-restart user-data fix (#66), the registration-race fix (#67) or themode: stopfix (#69).That contradicts this file's own stated rule: "The moving major tag (e.g.
v4) always points at the latest release in that major line." I will movev4to the v4.0.3 tag once this merges.Verification
npm ciclean,npm run lintclean,npm test— 245 passingnpm run package— rebuiltdist/is byte-identical to what is committed, so this release ships no bundle change