Files
cozystack/docs/agents
Myasnikov Daniil 6395ca1759 docs(release): check changelog claims against the code
The generator writes each entry from the opening of the PR text, one PR
at a time, and nothing in its instructions asks it to check a statement
against the tree it ships. The v1.7.0 draft had every author and PR
number right and still carried 22 wrong or missing statements, several
in the breaking-changes section, where a wrong instruction breaks an
upgrade: a companion-repository fix credited to a tag that does not
contain it, worker pools said to survive a migration that never pins
their template, migrations said to run on a variant that disables them.

The checks that would have caught them live in docs/release.md, which
the model is never pointed at, and the detailed rules it does read are
about bookkeeping. Add the semantic half: read the whole release note,
describe the final state at the upper-bound tag, compare with the
previous release, take identifiers, migration behaviour and variant
scope from the code, collect required actions beyond `!` commits, pin
companion changes to a tag, and run the pre-publish checks and the
validator on the written file before exiting.

The pre-publish checks name the file after $NEW, which in the promotion
configuration is the rc tag, so they are told to read the stable file
name; otherwise the reference and link checks read a file that does
not exist and report nothing. A minor release's versioned docs are not
live until it publishes, so those links are checked against the
website tree rather than expected to answer 200.

Assisted-by: LLM
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
2026-10-16 08:18:34 +00:00
..