Commit Graph
10 Commits
Author SHA1 Message Date
sam d10b070a2e chore(release): v1.43.0
deploy / gate (push) Failing after 3m35s
deploy / build-and-push (push) Skipped
deploy / dist-zip (push) Skipped
2026-09-28 02:13:34 +10:00
sam 4242d94676 chore(release): v1.42.0
deploy / gate (push) Failing after 5m36s
deploy / build-and-push (push) Skipped
deploy / dist-zip (push) Skipped
2026-09-26 10:32:39 +10:00
sam a4d98786a1 chore(release): v1.41.2
deploy / gate (push) Failing after 3m35s
deploy / build-and-push (push) Skipped
deploy / dist-zip (push) Skipped
2026-09-25 01:58:54 +10:00
sam be1b3aa6a1 chore(release): v1.41.1
deploy / gate (push) Failing after 5m34s
deploy / build-and-push (push) Skipped
deploy / dist-zip (push) Skipped
2026-09-25 01:29:59 +10:00
sam a22030bd65 chore(release): v1.41.0
deploy / gate (push) Failing after 3m29s
deploy / build-and-push (push) Skipped
deploy / dist-zip (push) Skipped
2026-09-25 01:12:45 +10:00
sam 19cf9ae2ab chore(release): v1.40.0
deploy / gate (push) Failing after 5m33s
deploy / build-and-push (push) Skipped
deploy / dist-zip (push) Skipped
2026-09-23 13:30:57 +10:00
sam ee78bfa7bc chore(release): v1.39.0
deploy / gate (push) Failing after 5m48s
deploy / build-and-push (push) Skipped
deploy / dist-zip (push) Skipped
2026-09-23 12:53:48 +10:00
sam 91691fde93 chore(release): v1.38.0 2026-09-23 03:36:31 +10:00
sam 69c1e59e41 chore(release): v1.37.1
deploy / gate (push) Failing after 5m42s
deploy / build-and-push (push) Skipped
deploy / dist-zip (push) Skipped
2026-09-22 21:45:18 +10:00
sam 83c06b6aff 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