Draft the 0.17.0 release report; reconcile the changelog - #2728
Draft
chalin wants to merge 13 commits into
Draft
Conversation
- Adds the 0.17.0 release post (draft: true) covering the dart-sass swap, breadcrumb semantic classes, the install-command rename, and the Mermaid pin, with per-mode actions and sanity checks. - Reconciles the changelog `#next` section: adds the breadcrumb breaking entry and the trusted-publishing maintainers line, weaves release-report links, drops the 0.16.1 placeholders. - Marks two holds with TODO comments: semantic-classes docs links (after google#2727 merges) and the warnings-expected clause (after the Sass own-warnings PR). - Adds the draft-cycle lychee excludes (0.16 pattern, removed when 0.17.0 ships).
The consumer-contract link target for the post and changelog is the user guide's semantic-classes section, not the contributor conventions page (owner call, 2026-08-19); TODO holds updated accordingly.
- Repoints the Cloudflare guidance at Hugo's renamed Host on Cloudflare page (the host-on-cloudflare-pages URL now 404s). - Excludes the draft post's Next-variant self-link (main--docsydocs.netlify.app) until the post is on main.
Cross-resource audit outcome: the one edit is the google#2727 TODO, which now tells the link-wiring refresh to replace the post's @extend mechanism clause with the page link instead of stacking a link on a restatement.
- Reshapes the supply-chain For-maintainers echo of the changelog list into summary prose that links it. - Rehomes the Chroma isolation note from the escape hatch to the recheck section, where it applies. - Trims doubled statements: the Ready-to-upgrade Hugo line now defers to the version list, Mermaid states its benefit once, and the Dart Sass row and why-now close each carry one clause.
Focused review against the owner dash standard: none of the post's 16 dash asides is a true interruption, so each takes its matching construct (colon for elaborations, parentheses for asides, comma or semicolon elsewhere). Descriptions aspect reviewed clean, no changes.
The user-guide section owns more than first assumed: the per-release selector-changes promise and the keep-alive caveat, not just the @extend mechanism. The wiring refresh now trims all three.
- Self-provisioned bullet: drops the false consumer-pin claim (only the monorepo root pins sass-embedded; @docsy/theme declares none) and the premature floor rationale (the shipped head-css.html passes no toCSS silencing options); the floor stands bare, with the supported version routed to the official support policy. - Holds: the warnings-clause TODO now carries the floor rationale for when the clause lands; the google#2727 TODO adds the What's-next selector-table promise to the trim list. - Cloudflare snippet: curl -f, and an unprefixed example version. - Update docs: 0.16-or-earlier crossing bullet (existing house pattern) routes upgraders to the post's Dart Sass actions.
- Rescopes the provider Sass snippet to Linux x64, pointing other platforms at the dart-sass release assets. - Trues the rendering claim to what the visual suite showed: visually unchanged with single-channel rounding on a few dozen pixels (the dart-sass commit updated six goldens); recheck and changelog wording follow. - Narrows "npm lifecycle hooks are gone" to install + implicit pre/post run-hooks (the theme keeps deliberate pack-time hooks). - Trims the changelog's install-rename and Mermaid entries to house scale, delegating per-mode actions to the post.
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.
Contributes to Release 0.17.0 preparation #2691
Release post (
draft: true): the dart-sass swap, breadcrumb semantic classes, the install-command rename, and the Mermaid pin -- per-mode actions, upgrade checklist, sanity checks. No Hugo companion post this cycle (no Hugo change since v0.16.0).Changelog
#next: adds the breadcrumb breaking entry and the trusted-publishing maintainers line; weaves release-report links; drops the 0.16.1 placeholders.Held for in-flight PRs (TODO-marked in place): links to the semantic-classes conventions page land after Document the td- semantic-class contract and conventions #2727 merges; the warnings-expected clause lands after the Sass own-warnings PR. This PR merges last, per the agreed landing order.
Lychee: draft-cycle excludes per the 0.16 pattern ("Remove after 0.17.0 ships").
Coverage: all 21 commits in
v0.16.0..97bfabeaare routed -- 3 breaking (post sections + changelog entries), 2 user-facing changes, 6 maintainer-facing (For-maintainers summaries), 10 internal (release-notes/milestone only).Preview(s):