0xrsydn 809966925e docs: keep a CHANGELOG.md, with one entry file per PR ... Release notes were written by hand on GitHub at tag time, so the contents of a stacked release had to be pieced together from every PR, and output changes that scripts and agents rely on were easy to miss. - CHANGELOG.md backfills every published release (0.2.0 to 0.4.0) from its GitHub notes, verbatim. - A PR adds changes/unreleased/<branch-name>.md instead of editing CHANGELOG.md, so stacked PRs never conflict. changes/README.md gives the sections, including Output Changes for JSON, MCP and error-code changes. - scripts/changelog.sh: `check` validates entries and CHANGELOG.md, `release X.Y.Z` folds the entries into a new section (ordered by PR), and `notes X.Y.Z` prints a section as GitHub release notes. - The release workflow sets the GitHub notes from the tag's section. - New flake check `changelog` runs scripts/changelog-test.sh; both scripts are shellchecked. - Entries for 0.5.0: #73, #74, #75, #78, #79, #80, #81 and this PR. Claude-Session: https://claude.ai/code/session_01RqPPVeVDrnLoP7NUZmLRxY		2026-11-04 19:48:58 +07:00
..
ci.yml	fix(publisher): require the jq and bash it uses; pin CI actions	2026-10-18 02:16:18 +00:00
publish-ownership-snapshot.yml	fix(release): robust publisher fields, WAL-safe copy, installer tag order, pinned actions	2026-10-18 02:16:18 +00:00
pullfrog.yml	chore: add Pullfrog workflow file	2026-08-18 11:30:20 +00:00
release.yml	docs: keep a CHANGELOG.md, with one entry file per PR	2026-11-04 19:48:58 +07:00