Commit Graph
38 Commits
Author SHA1 Message Date
sam 5a9d223a63 docs(news): regenerate release notes from the changelog 2026-10-19 10:05:23 +11:00
sam 9cd1495838 docs: edit guides, PRDs and security notes, regenerate release news 2026-10-19 10:04:36 +11:00
sam 6c488f29c9 chore(release): v1.55.0 2026-10-16 03:57:48 +11:00
sam 2c49fa5a55 chore(release): v1.54.3 2026-10-16 03:46:35 +11:00
sam 90557a6d50 chore(release): v1.54.2 2026-10-16 03:33:58 +11:00
sam 198c6a6a05 chore(release): v1.54.1 2026-10-16 03:11:22 +11:00
sam 4c8988cc3e chore(release): v1.54.0 2026-10-16 03:00:32 +11:00
sam 7389efc797 chore(release): v1.53.0 2026-10-11 04:23:10 +11:00
sam 8c13485652 chore(release): v1.52.0 2026-10-09 13:09:59 +11:00
sam 22f44dac93 chore(release): v1.51.1 2026-10-08 01:42:29 +11:00
sam 269327831f chore(release): v1.51.0 2026-10-08 01:37:28 +11:00
sam cccb20b435 chore(release): v1.50.1 2026-10-08 00:40:03 +11:00
sam 0bd24bda64 chore(release): v1.50.0 2026-10-08 00:25:35 +11:00
sam eb835d9096 chore(release): v1.49.4 2026-10-07 23:58:52 +11:00
sam fee2609def chore(release): v1.49.3 2026-10-07 23:34:21 +11:00
sam c11068816f chore(release): v1.49.2 2026-10-07 23:18:11 +11:00
sam 22d38ce435 chore(release): v1.49.1 2026-10-07 23:10:38 +11:00
sam 7dd5b0930c chore(release): v1.49.0 2026-10-07 22:17:00 +11:00
sam ceb25b95f7 chore(release): v1.48.1 2026-10-07 01:00:30 +11:00
sam a4f3a10f69 chore(release): v1.48.0 2026-10-07 00:57:07 +11:00
sam 41bd098bc7 chore(release): v1.47.3 2026-10-07 00:33:23 +11:00
sam 4a7fd4ab9c chore(release): v1.47.2 2026-10-06 03:25:44 +11:00
sam 95ca1cd303 chore(release): v1.47.1 2026-10-06 03:05:39 +11:00
sam fe892b5c3e chore(release): v1.47.0 2026-10-06 02:03:15 +11:00
sam b7d7a9ea74 chore(release): v1.46.0 2026-10-02 13:03:00 +10:00
sam e190e58c3d chore(release): v1.45.0 2026-09-30 11:44:01 +10:00
sam 2fb6a0c071 chore(release): v1.44.1 2026-09-29 15:41:53 +10:00
sam 831772c45e chore(release): v1.44.0 2026-09-29 02:04:40 +10:00
sam 6f7bfc6dd6 chore(release): v1.43.0 2026-09-28 02:13:34 +10:00
sam d61dff55bf chore(release): v1.42.0 2026-09-26 10:32:39 +10:00
sam d675f4b1fe chore(release): v1.41.2 2026-09-25 01:58:54 +10:00
sam fe4e9aa32b chore(release): v1.41.1 2026-09-25 01:29:59 +10:00
sam 51093598b1 chore(release): v1.41.0 2026-09-25 01:12:45 +10:00
sam 93995239e3 chore(release): v1.40.0 2026-09-23 13:30:57 +10:00
sam cbdc83ac73 chore(release): v1.39.0 2026-09-23 12:53:48 +10:00
sam aab8b8d435 chore(release): v1.38.0 2026-09-23 03:36:31 +10:00
sam 2d9724c1ec chore(release): v1.37.1 2026-09-22 21:45:18 +10:00
sam cd2ab7f2cb feat(release): one release stream, one version, one page per version
CHANGELOG.archied.md and CHANGELOG.archie.md were two version streams that
drifted: a release that moved both components had two numbers, two pages and
two tags, and a reader had to visit two files to learn what shipped.

The merged history holds 65 versions from 64 archied and 34 archie sections --
33 that both components released, 31 only archied, one only archie -- so 98
published pages become 65. A version's date is the newest of its sections'
dates, and a component whose own date differs carries it on its label, because
the history has two dates and the merge must not invent one. `## [Unreleased]`
is not a release: it gets no page, and it stays at the top of the file.

A level-two heading is where the merge could silently drop a section, so the
merge is verified by content rather than by the generator: section counts per
source, the merged version set against the exact union, and every source `###`
title present both as a substring and, after stripping the component prefix, as
an identical heading. Counting `##` headings rather than releases overcounts by
one here, which is how the empty `[Unreleased]` block was caught.

- newsgen reads one file and writes `docs/news/<version>.md`, the index, the
  canonical `releases.json`, and `docs/news/redirects.json`. The redirect table
  is what keeps the retired `/news/<component>/<version>/` URLs alive; it is
  generated beside the pages so it cannot drift from them.
- release.sh takes one `--version`, keeps commit and tag (the Woodpecker
  pipeline that will own them does not exist yet), and exits 3 when the commit
  set justifies no release, so a pipeline can finish green without tagging.
- The consumers of the two files follow: the deploy workflow's tag gate and
  release-notes extraction, the zip contents, the update check's changelog
  links, the packaged-path note, the docs skill, and newsgen's tests.

The per-component detail survives as labelled sections inside each release, so
a reader still learns whether archied or the agent changed; what goes away is
the separate numbers and the separate pages.
2026-09-22 17:18:06 +10:00