Skip to content

Release 0.17.0 preparation - #2770

Merged
chalin merged 19 commits into
google:mainfrom
chalin:release-0.17.0-prep
Aug 30, 2026
Merged

Release 0.17.0 preparation#2770
chalin merged 19 commits into
google:mainfrom
chalin:release-0.17.0-prep

Conversation

@chalin

@chalin chalin commented Aug 30, 2026

Copy link
Copy Markdown
Collaborator

chalin added 4 commits August 30, 2026 13:03
- Flips the release post out of draft, dated 2026-08-30
- Changelog: v0.17.0 section final (UNRELEASED note out, anchor #next -> #v0.17.0)
- Points compare links at v0.16.0...v0.17.0
- Stamps version 0.17.0 (set:version; next dev v0.17.1-dev)
- Adds creating the next release's draft report post to the post-release
  followup, giving next-cycle changes a single landing home during release prep
- Rides the existing Remove-after-0.17.0-ships exclude block
@chalin chalin added this to the 0.17.0 milestone Aug 30, 2026
chalin added 11 commits August 30, 2026 14:29
- 0.17 post: names the npm-rebuild pattern that now silently no-ops (GitHub-npm
  action), favicons.html in the overrides review for 0.16 crossings, agent
  directive safe to add unconditionally
- Update docs: stepwise multi-release recommendation; 0.15 bullet includes the
  0.16 favicon move; npm-package GitHub-mode rerun line
- 0.16 post: adds the missing applies-if gate for sites with icons under
  static/favicons/ (silent icon loss otherwise)
- Replaces the lychee.toml exclude: the cache is self-cleaning on regeneration,
  no post-release sweep to remember
- The favicon gate's condition lives in the 0.16 post's applies-if (one home);
  the bullet now just names the two action sets
- The stepwise rule now routes crossings to each post's actions, whose
  applies-if gates own the does-this-concern-you detail (owner call: the
  narrowing shortcuts were the WET copy that let the favicon gap through)
- Retires the 0.18-ish TODO scheduled for the 0.15 bullet's removal
- Post bullet keeps only the new fact (rebuild silently no-ops); the
  replacement action is the bullet above
- npm-package.md names install:theme-deps and routes to other-options, which
  owns the command form and rerun rule
- The gate's first bullet already states the class-level change and action;
  the idiom-specific case was provenance, not reader need
- Crossers reach the fact via the 0.16 post's favicon gates; a 0.16-relative
  post carries no crossing detail
- Discovery location and consequence are derivable from the section prose;
  matches the sibling gates' condition-plus-action register
- Scopes the static/favicons/ gate to non-overriders (an overrider moving
  files would break their hardcoded links)
- Routes the delete-the-override path to the Add-your-favicons guide
@chalin
chalin marked this pull request as ready for review August 30, 2026 19:41
chalin added 4 commits August 30, 2026 15:49
- Modernizes-and-strengthens matches the enumeration (pins are hardening);
  breadcrumb exclamation folded into the series
- Evergreen homes added: favicon discovery is top-of-static only
  (iconsimages), the upgrade-post baseline contract and the 206-seed
  convention (maintainer notes)
- Update-order step 1 generalized to any named build prerequisite
- Trims: llms reassurance already owned by section prose, stale half of the
  frozen-params comment, duplicate favicon link def, wordy notes tail,
  rerun spelling
- iconsimages states top-of-static discovery without release references
  (Content placement: site docs are Docsy as it is now)
- 0.16 post gates carry the location reminder; link defs re-sorted
@chalin
chalin merged commit 8d38d5f into google:main Aug 30, 2026
18 checks passed
@chalin
chalin deleted the release-0.17.0-prep branch August 30, 2026 20:22
@chalin chalin mentioned this pull request Aug 31, 2026
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant