The repo has releases (`v0.4.0`, `v0.4.1`, `v0.5.0`) but no CHANGELOG.md, which makes it hard for users to track what changed between versions. ## Acceptance criteria - [ ] `CHANGELOG.md` at the repo root using the [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) format - [ ] Sections for `v0.4.0`, `v0.4.1`, `v0.5.0` populated from `git log` between tags - [ ] An `Unreleased` section at the top - [ ] `CONTRIBUTING.md` updated to require a CHANGELOG entry per PR ## Suggested categories `Added`, `Changed`, `Deprecated`, `Removed`, `Fixed`, `Security`
The repo has releases (
v0.4.0,v0.4.1,v0.5.0) but no CHANGELOG.md, which makes it hard for users to track what changed between versions.Acceptance criteria
CHANGELOG.mdat the repo root using the Keep a Changelog formatv0.4.0,v0.4.1,v0.5.0populated fromgit logbetween tagsUnreleasedsection at the topCONTRIBUTING.mdupdated to require a CHANGELOG entry per PRSuggested categories
Added,Changed,Deprecated,Removed,Fixed,Security