Changelog: show the notes published with each release on GitHub - #43
Merged
Merged
Conversation
A new release_notes content collection (src/lib/release-notes.ts) reads the notes of every release at build time and renders them with the site's markdown settings, like the Core documents. - English: the release's notes without the download table, GitHub's list of merged pull requests and Enterprise's image and Helm preamble. - Chinese: ThinkWatch Lite's annotated tags hold the notes in Chinese (the text of its update window), read through the GraphQL API. Their short lines followed by items become headings, and the upgrade notes are set off. The first Lite tags were annotated in English; with no notes on the release, that text is the English note. - Core and Enterprise have English notes only; on the Chinese page those releases carry an EN badge. - Heading ids are prefixed per release, since "upgrade-notes" and the like would otherwise repeat on one page. On the page a release with notes opens in place; a link to a release (the latest tiles, a shared anchor, the old #v0.4.0 anchors) opens it. The written-up Enterprise releases keep their title and highlights in the same place. Core v0.46.0 and earlier have only GitHub's generated pull-request list, so they keep linking to GitHub. When GitHub cannot be reached the build warns and the releases link to GitHub as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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
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 changelog listed 110 releases, but only the four Enterprise releases written up on this site had notes; the rest linked to GitHub. This reads the notes published with each release at build time and shows them under the release.
Source (
src/lib/release-notes.ts, a content loader like the Core documents' loader, rendered with the site's markdown settings)GITHUB_TOKEN; the deploy and check workflows already set it.-items becomes a heading.<strong>.**…**does not close when it ends in a full-width colon right before a character.upgrade-noteswould otherwise repeat on one page.releases.jsonfallback stays lean.Page
#v0.4.0anchors open their release.Checked with a token-backed local build and headless Chromium:
#v0.4.0anchor does too.tsc --noEmitis clean.🤖 Generated with Claude Code