Repository navigation
Write down the twelve changes merged since the notes were drafted - #279
Merged
Merged
Conversation
The 0.3.1 section stopped where #266 left it, and eleven merges since then were undocumented with [Unreleased] empty. That is the same gap #266 fixed, recreated by merging all day without writing entries as I went; the check added in #266 catches a wrong date, not a missing entry. Added: the tab context menu. Website: even page padding, the heading scale, anchor links landing clear of the header, the nav's hover highlight lining up with the current page's, the theme selector's focus ring and dropdown, the search and menu buttons matching, the breadcrumb separators, mobile search filling the screen, the install section leading with winget and losing its repeated rows, the interface coverage table's ticks and dashes and corrected semantics, and two FAQ answers written from the Search Console data. The winget entry is rewritten rather than added to. It said the submission "would have published the wrong version"; `v0.2.2` through `v0.2.6` are already in the public catalog that way, so it now says what actually happened, that upgrades still work because winget normalises a leading `v`, and that the publish job asserts the shape rather than trusting the strip. Deliberately not listed, because a changelog is for people who use the thing rather than people who build it, and none of these change what ships: - the dead-CSS prune (cascade winners identical before and after) - the preferences refactor (no behaviour change) - the Node version pin (contributors only) - the preview host change and its revert, which net to zero and were never in a release astro check 0 errors, a11y 0 violations in both themes, and the new entries render on the built changelog page.
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.
The 0.3.1 section stopped where #266 left it, and eleven merges since then were undocumented with
[Unreleased]empty — the same gap I raised as finding #4 and fixed in #266, recreated by merging all day without writing entries as I went. The check #266 added catches a wrong date, not a missing entry.Added
The tab context menu (#273).
Website
Even page padding, the heading scale, anchor links landing clear of the header, the nav hover highlight lining up with the current page's, the theme selector's focus ring and dropdown, matching search/menu buttons, breadcrumb separators (#268) · mobile search filling the screen (#272) · the install section leading with winget and losing its repeated rows (#270) · the coverage table's ticks, dashes and corrected semantics (#269) · two FAQ answers written from the Search Console data (#271).
The winget entry is rewritten, not appended to
It said the submission "would have published the wrong version".
v0.2.2throughv0.2.6are already in the public catalog that way, so the entry now says what actually happened — thatwinget show netsclireports a version this project never issued, that upgrades still work because winget normalises a leadingv, and that the publish job now asserts the shape rather than trusting the strip.Deliberately not listed
A changelog is for people who use the thing, not people who build it, and none of these change what ships:
Say the word if you'd rather any of those were listed.
Verification
astro check0 errors · a11y 0 violations in both themes · CSS budget 24 ·check:changelogpasses · new entries confirmed rendering on the built changelog page.