Bring KiteViewers' 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: a stale 2024 ## Unreleased at line 135 between the v0.4.x sections is where the bump would put the next release; fold it into the release it belongs to. Releases use vX.Y.Z - YYYY-MM-DD, one is v 0.5.2, and Project.toml (0.6.1) is ahead of the top header (v0.6.0): say on the thread whether 0.6.1 was released.
Bring KiteViewers' 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: a stale 2024
## Unreleasedat line 135 between the v0.4.x sections is where the bump would put the next release; fold it into the release it belongs to. Releases usevX.Y.Z - YYYY-MM-DD, one isv 0.5.2, and Project.toml (0.6.1) is ahead of the top header (v0.6.0): say on the thread whether 0.6.1 was released.