Repository navigation
Bring KiteModels' changelog to the release convention #328
Description
Activity
Review on #329, finding by finding, no code change:
- v0.6.15/v0.6.10/v0.6.9 have no section header: not fixed. Their notes mix added, fixed and changed in one list, so giving them sections means splitting and moving note text, and this issue rewrites headers only. rules/release does not read them. The card now says so.
- v0.11.4/v0.11.1/v0.11.0 order sections Changed/Fixed/Added: not fixed. Reordering moves note text too. The card now says so.
- CI on 9cb0f9c is green: CI (reuse-lint, Link checker) passes. Test on PRs runs only on src/, test/, *.toml, so it does not run for this change.
44 remaining items
Question from
KiteModels.jl-328Should #328 be closed as won't-do, now that @ufechner7 closed #329 and asked for no more of these pull requests?
- Close it: KiteModels.jl stays on its own changelog layout (
### KiteModels vX.Y.Z YYYY-MM-DD), andagent releasekeeps refusing on this repo until a maintainer agrees to a format. - Keep it open: nothing happens until Uwe agrees. The branch
agent/328-bring-kitemodels-changelog-to-the-releasstays pushed as it is (82e3558), and I open no new pull request from it.
My recommendation: close it, and leave it to Uwe whether the changelog format changes. I have stopped and will push nothing more.
- Close it: KiteModels.jl stays on its own changelog layout (
Bring KiteModels' 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
### KiteModels vX.Y.Z YYYY-MM-DDwith no##line in the file, so a bump would put the new section at the end of the file.