Commit Graph
47 Commits
Author SHA1 Message Date
sam 17d3917e68 docs(news): regenerate release notes from the changelog 2026-10-19 10:05:23 +11:00
sam 5a45e9614f docs: edit guides, PRDs and security notes, regenerate release news 2026-10-19 10:04:36 +11:00
sam a762bae61e chore(release): v1.55.0 2026-10-16 03:57:48 +11:00
sam 3ff826744b chore(release): v1.54.3 2026-10-16 03:46:35 +11:00
sam deac6bcc3d chore(release): v1.54.2 2026-10-16 03:33:58 +11:00
sam 9e80470ce7 chore(release): v1.54.1 2026-10-16 03:11:22 +11:00
sam 83916bc8e3 chore(release): v1.54.0 2026-10-16 03:00:32 +11:00
sam 7e32554a9d chore(release): v1.53.0 2026-10-11 04:23:10 +11:00
sam cd35bb9da1 chore(release): v1.52.0 2026-10-09 13:09:59 +11:00
sam 5ec332ac19 chore(release): v1.51.1 2026-10-08 01:42:29 +11:00
sam 3895f5e3d5 chore(release): v1.51.0 2026-10-08 01:37:28 +11:00
sam 001e5c7e56 chore(release): v1.50.1 2026-10-08 00:40:03 +11:00
sam 60b9d9a05e chore(release): v1.50.0 2026-10-08 00:25:35 +11:00
sam 39f670c61d chore(release): v1.49.4 2026-10-07 23:58:52 +11:00
sam 45d6c8f9a0 chore(release): v1.49.3 2026-10-07 23:34:21 +11:00
sam 4b98826b96 chore(release): v1.49.2 2026-10-07 23:18:11 +11:00
sam e57a0ff6c2 chore(release): v1.49.1 2026-10-07 23:10:38 +11:00
sam 866ebe8ac3 chore(release): v1.49.0 2026-10-07 22:17:00 +11:00
sam 923d3a4496 chore(release): v1.48.1 2026-10-07 01:00:30 +11:00
sam e2cbd7de89 chore(release): v1.48.0 2026-10-07 00:57:07 +11:00
sam 7ce11f842d chore(release): v1.47.3 2026-10-07 00:33:23 +11:00
sam 3759a88c05 chore(release): v1.47.2 2026-10-06 03:25:44 +11:00
sam 6605e0f46a chore(release): v1.47.1 2026-10-06 03:05:39 +11:00
sam b67b7286d8 docs(news): regenerate for the corrected 1.47.0 notes 2026-10-06 03:04:35 +11:00
sam 563c83c27e chore(release): v1.47.0 2026-10-06 02:03:15 +11:00
sam d52cdf7cc8 chore(release): v1.46.0 2026-10-02 13:03:00 +10:00
sam 3ae705c77f chore(release): v1.45.0 2026-09-30 11:44:01 +10:00
sam 54356fc184 chore(release): v1.44.1 2026-09-29 15:41:53 +10:00
sam 9bb3340dce chore(release): v1.44.0 2026-09-29 02:04:40 +10:00
sam 621cfb30a0 chore(release): v1.43.0 2026-09-28 02:13:34 +10:00
sam 7ae8e31358 chore(release): v1.42.0 2026-09-26 10:32:39 +10:00
sam 3aea627f55 chore(release): v1.41.2 2026-09-25 01:58:54 +10:00
sam b42663938a chore(release): v1.41.1 2026-09-25 01:29:59 +10:00
sam 6a8555665e chore(release): v1.41.0 2026-09-25 01:12:45 +10:00
sam ac4e435e07 chore(release): v1.40.0 2026-09-23 13:30:57 +10:00
sam c347a2b80e chore(release): v1.39.0 2026-09-23 12:53:48 +10:00
sam 8c83f7d322 chore(release): v1.38.0 2026-09-23 03:36:31 +10:00
sam 05b69a7e1a chore(release): v1.37.1 2026-09-22 21:45:18 +10:00
sam 0b408017e0 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
sam c43bd46ecb docs(news): state what a reader gets, and move the design where it is read
The v1.36.0 release note carried four things a reader cannot use. The dashboard's
seven in-browser tools and the installtype fix stay; the withheld judgement verbs,
the consequentialHint limitation and the two silent-failure notes are removed from
the release feed and moved to where an implementer looks.

  - The four verbs are withheld because an agent that can approve can approve its
    own work. That is settled design, so it now sits in docs/architecture/identity.md,
    beside the approval-path conflict it belongs with, stated as the constraint it is:
    attribution, not capability, is what releasing them depends on.
  - The browser-tool surface had no home in docs/architecture, so it has one now:
    docs/architecture/dashboard-agent-tools.md holds what a tool call can be
    attributed to, why confirmation is a signal rather than a control, and the two
    ways the surface fails silently.

Audited 1.35.0, 1.36.0 and 1.37.0 for the same class. 1.37.0 is clean. 1.35.0 carried
two build notes: a bullet recounting that a guard had never been written because it
failed, and a clause about a manager "finally" having a production writer. Both are
gone; the capabilities they were attached to remain.

RELEASING.md now carries the rule so the next release reads it: release notes state
what a reader gets, and design constraints, withheld capabilities and failure modes
belong in docs/architecture/, because a note about an absence reads as a feature to
someone who never had the thing.

docs/news/** is regenerated by task news, never hand-edited. task check passed before
this commit: the chain runs it, so a failing gate commits nothing.
2026-09-22 16:53:27 +10:00
sam 1b67340ce3 chore(release): archied v1.37.0 2026-09-22 15:05:30 +10:00
sam e08ff1b4ba chore(release): archied v1.36.0 2026-09-22 14:22:21 +10:00
sam 958dcd1329 chore(release): archied v1.35.0 archie v1.35.0 2026-09-22 09:52:14 +10:00
sam 1eed805fa5 chore(release): archied v1.34.0 2026-09-22 07:14:25 +10:00
sam 67ffed9d1e chore(release): archied v1.33.0 2026-09-22 05:59:16 +10:00
sam 001a27fb15 chore(release): archied v1.32.1 2026-09-22 05:43:46 +10:00
sam eaa53df4d8 feat(docs): publish generated news and per-version release notes
Derive a public news page and one release-notes page per component version
from CHANGELOG.archied.md and CHANGELOG.archie.md, the notes the release
process already freezes.

- tools/newsgen writes docs/news/releases.json, the canonical artifact a host
  renders from, plus the MkDocs pages. Check mode fails when the committed
  files lag a changelog edit, and runs in task check; tools/release.sh --tag
  regenerates and stages them in the release commit, skipping files already
  current.
- mkdocs.yml keeps the version pages out of the derived navigation without
  excluding them from the site.
2026-09-22 05:03:29 +10:00