Bring KiteControllers' changelog to the release convention
Bring CHANGELOG.md to the one convention the box releases from, so agent release / "release " on Slack opens the bump PR without a refusal (1-Bart-1/Agents#608). Pending notes sit under one ## Unreleased header above every release (or as files in changelog.d/), grouped under ### Added / ### Fixed / ### Changed. Every released section is headed ## <PackageName> vX.Y.Z YYYY-MM-DD: ## level, v before the version, ISO date, no dash, no brackets, no "(unreleased)". Rewrite headers only; leave the note text as it is. Check: bin/release --dry-run (the box copy, rules/release in 1-Bart-1/Agents) on the PR head reads the version and the notes.
In this repo: releases use vX.Y.Z - YYYY-MM-DD (drop the dash); there is no ## Unreleased yet, add an empty one.
Bring KiteControllers' changelog to the release convention
Bring CHANGELOG.md to the one convention the box releases from, so
agent release/ "release " on Slack opens the bump PR without a refusal (1-Bart-1/Agents#608). Pending notes sit under one## Unreleasedheader above every release (or as files inchangelog.d/), grouped under### Added/### Fixed/### Changed. Every released section is headed## <PackageName> vX.Y.Z YYYY-MM-DD:##level,vbefore the version, ISO date, no dash, no brackets, no "(unreleased)". Rewrite headers only; leave the note text as it is. Check:bin/release --dry-run(the box copy,rules/releasein 1-Bart-1/Agents) on the PR head reads the version and the notes.In this repo: releases use
vX.Y.Z - YYYY-MM-DD(drop the dash); there is no## Unreleasedyet, add an empty one.