🤖 WIP issue, drafted by Claude during review of #550.
#550 automates release-version and draft-state stamping for the artifacts published to grc.store. The equivalent work for the docs site is still a manual checklist item, and it is what #544/#545 had to clean up after v2026.08.28.
.github/ISSUE_TEMPLATE/release.yaml currently asks a human to:
- line 27 — change
Version: devel to the release number in docs/versions/<VERSION>.md
- line 29 — remove the "not for production use" warning from the same file
- line 40 — update the headers in
docs/versions/<VERSION>-checklist.md and -crosswalk.md
These are the same class of staleness #550 fixes: a value that tracks devel in-repo and has to become the release version in the published output. Doing it by hand is why a release can ship with the wrong version and warning text still in place.
The compiler already takes --artifact-version (line 23 of the same template) to pin mapping-document links to the release tag, so there is an existing seam to extend rather than a new mechanism to invent.
Suggested scope: have baseline-compiler compile derive the version header and drop the pre-release warning from --artifact-version, and delete the corresponding manual steps from the release template.
🤖 WIP issue, drafted by Claude during review of #550.
#550 automates release-version and draft-state stamping for the artifacts published to grc.store. The equivalent work for the docs site is still a manual checklist item, and it is what #544/#545 had to clean up after v2026.08.28.
.github/ISSUE_TEMPLATE/release.yamlcurrently asks a human to:Version: develto the release number indocs/versions/<VERSION>.mddocs/versions/<VERSION>-checklist.mdand-crosswalk.mdThese are the same class of staleness #550 fixes: a value that tracks
develin-repo and has to become the release version in the published output. Doing it by hand is why a release can ship with the wrong version and warning text still in place.The compiler already takes
--artifact-version(line 23 of the same template) to pin mapping-document links to the release tag, so there is an existing seam to extend rather than a new mechanism to invent.Suggested scope: have
baseline-compiler compilederive the version header and drop the pre-release warning from--artifact-version, and delete the corresponding manual steps from the release template.