Repository navigation
Bring WinchControllers' changelog to the release convention #39
Description
Activity
Rewriting CHANGELOG.md headers only: releases become
## WinchControllers vX.Y.Z YYYY-MM-DD(v0.5.2 gets its tag date 2025-05-29) and groups drop to###. The pending v0.6.5 note moves unchanged to changelog.d/, so the top##matches Project.toml. This repo's bin/release gets the matching##grep. The broken bin/install -y belongs to #38 and stays out of this PR.
Bring WinchControllers' 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 are
###headers with no##line in the file, and pending notes sit under### WinchControllers v0.6.5 (unreleased).