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.
This commit is contained in:
134 files changed
+3189
-3241
No files matched your search
@@ -171,7 +171,7 @@ cat <<EOF
|
||||
"Installed": "$(esc "$daemon_installed")",
|
||||
"Available": "$(esc "$daemon_available")",
|
||||
"Reference": "$(esc "$(reference_for archie-core "$daemon_available" "$daemon_artifacts")")",
|
||||
"Changelog": "https://github.com/${REPO_SLUG}/blob/main/CHANGELOG.archied.md"
|
||||
"Changelog": "https://github.com/${REPO_SLUG}/blob/main/CHANGELOG.md"
|
||||
},
|
||||
{
|
||||
"ID": "agent",
|
||||
@@ -179,7 +179,7 @@ cat <<EOF
|
||||
"Installed": "$(esc "$agent_installed")",
|
||||
"Available": "$(esc "$agent_available")",
|
||||
"Reference": "$(esc "$(reference_for archie-runtime "$agent_available" "$agent_artifacts")")",
|
||||
"Changelog": "https://github.com/${REPO_SLUG}/blob/main/CHANGELOG.archie.md"
|
||||
"Changelog": "https://github.com/${REPO_SLUG}/blob/main/CHANGELOG.md"
|
||||
}
|
||||
],
|
||||
"Deferred": false
|
||||
|
||||
Reference in new issue
Block a user