Commit Graph
19 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 0d35e753b5 refactor: format markdown files using prettier, fix spelling concerns, reduce Taskfile bloat 2026-09-25 01:10:28 +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
sam 96314fb237 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 cba7a14f77 chore(release): archied v1.37.0
deploy / gate (push) Failing after 5m25s
deploy / build-and-push (push) Skipped
deploy / dist-zip (push) Skipped
2026-09-22 15:05:30 +10:00
sam 576718c32f chore(release): archied v1.36.0
deploy / gate (push) Failing after 3m24s
deploy / build-and-push (push) Skipped
deploy / dist-zip (push) Skipped
2026-09-22 14:22:21 +10:00
sam f9a5e205d8 chore(release): archied v1.35.0 archie v1.35.0
deploy / gate (push) Failing after 3m33s
deploy / build-and-push (push) Skipped
deploy / dist-zip (push) Skipped
2026-09-22 09:52:14 +10:00
sam db886f15b1 chore(release): archied v1.34.0
deploy / dist-zip (push) Skipped
deploy / gate (push) Failing after 6m14s
deploy / build-and-push (push) Skipped
2026-09-22 07:14:25 +10:00
sam 1db7cb98e3 chore(release): archied v1.33.0
deploy / gate (push) Canceled after 0s
deploy / build-and-push (push) Canceled after 0s
deploy / dist-zip (push) Canceled after 0s
2026-09-22 05:59:16 +10:00
sam 31060cc8a5 chore(release): archied v1.32.1
deploy / gate (push) Canceled after 0s
deploy / build-and-push (push) Canceled after 0s
deploy / dist-zip (push) Canceled after 0s
2026-09-22 05:43:46 +10:00
sam 93418801e9 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