Release 0.16.0 preparation - #2694
Merged
Merged
Conversation
…re release post
- Adopts the 0.15.0 lead-link shape (blog link on the bolded term), dropping the per-entry "See [0.16.0 release report]" sentences - Strips upgrade advice and mechanics homed in the release post (install commands, applies-if prose, reassurances) - Drops the redundant theme-minimum restatement from the Hugo-build entry; links the cached-sidebar entry to the post - Drops the google#2677 PR cite per the key-issues-only rule
Release post: - Settles one home per repeated fact: upgrade-Hugo-first order (Ready to upgrade), prefer-0.164.0 (Hugo Actions), experimental flag and full-is-default (section body), PostCSS opt-in config glob (Actions) - Delegates the 0.159.2-0.160.0 regression examples to the Hugo guide, which owns them - Cuts dead pointers, the nested-tag background clause, and the component-oriented vision clause - Links the multilingual sanity check to the Hugo guide language-API renames; rewords the upgrade bullet to kill the wrong parse Hugo post: - Keeps the Docsy-minimum apposition at its first mention only (amp-escaping section) - Cuts the amp-escaping exposure analysis: over-serves the section's brief-0.159.2-deployers gate - Merges the duplicated 0.160.1-fixed-regressions statement in template-module-cleanup - Nests the imaging example block under its bullet, dropping the redundant "For example" lead-in
- Chrome page: intro keeps the bare problem statement, the benefits list owns the cost/benefit specifics; drops the closing reachability clause restating its own section - Other options: drops the Hugo 0.110 config-filename TIP, which filters nobody at a 0.160.1 minimum
- Names the three install modes and the routing condition instead of restating "setup"; fixes the "Docsy site with Docsy" stutter and the pre-registry "Git or NPM" framing - Refreshes the get-started md-output golden accordingly
- Reworks the intro into a conditional plus one bare link per option: headings and section openers already carry the choice discriminators, with the clone rationale homed in Option 2 - Moves the migration pointer to Option 1, its audience's section - Drops the historical example-site note and the instructions-below dead pointer
…e test procedure - Release post: promote the order-of-steps pointer to a first bullet in both upgrade landings (deliberate WET, justified in a comment) - Maintainer notes: restructure steps 8/11 around a new appendix, 'Consumer-site test procedure' (pin per install mode, applies-if audit before first build, zero-warnings build, test suite, A/B diff with at-least-one-difference guard)
- Step 11: drop the examples-page bullet (homed in § Docsy example release) - Step 8: drop the push reminder restating the run-edit cycle - Test procedure: two-branch A/B baseline setup, recommending public/ as a git repository (make:public)
The official-release definition's home is the support policy; the post paragraph restated it. Keep only the delta -- registry releases are official -- and link the policy for the definition.
…ping, snippet cd fix, changelog tense - Notes: new step 15 publishes @docsy/theme before the deploy that takes the release post live (the post recommends the package); steps 15-23 -> 16-24 - Notes: HUGO_MODULE_REPLACEMENTS as an executable MODULE -> DIR mapping, verified via hugo mod graph - Notes: submodule snippet cd .. -> cd ../.. (git add ran from themes/) - Changelog: three 0.16.0 entries lead with past-tense verbs per the file's guidelines
- Notes: npm file: pin per npm sub-mode (GitHub root vs registry /theme) - Wrapup: drop the stale not-yet-in-notes clause (nested tag is steps 13-14) - Post: dash sweep on three pre-existing lines; description states favicon removal; theme-folder Actions scoped to the order of steps; two sanity checks added (theme path landed, module SCSS build); agent-ready highlight moved last; blog-index golden refreshed
…t before A pre-0.16 site imports github.com/google/docsy; the replacement targets .../docsy/theme, so hugo mod graph can't report it until the theme-folder action updates the import path. Also: targeted grep over head -3.
chalin
marked this pull request as ready for review
July 29, 2026 18:41
…easures Sweep the repo for release-scoped markers (Remove after / TODO(0.x)); delete the lychee exclusion block and confirm the link check passes over the now-live URLs; leave markers naming a later release.
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.
UNRELEASEDheading tov0.16.0, and re-points the tag-dependent links (compare, changelog anchor)TODO(tag-time)sites); inlines the 0.12.0 post's linkset:version: root + theme manifests, docsy.dev configs) and refreshes the md-output golden it renders intov0.15.0...v0.16.0compare URL in the Lychee config's remove-after-0.16.0-ships block (404 until the tag exists)69e597cc; tag-time checklist gains the refresh-loop gate item