Keep a Changelog
Semantic pull requests [0] + conventional-changelog [1] + squashing PRs and you get almost the same results (and more) with great automation and self-documentation for the whole process:* you'll never forget to add something to changelog* you get links to PRs in your changelog* it's much faster to make edits to PR messages compared to editing files* outside contributors get familiarized with the practice much faster (imagine getting new contributors to update changelogs)We recently adopted this practice at Pyroscope and it's been working out pretty well for us [2], I can certainly recommend it.[0] - https://github.com/apps/semantic-pull-requests[1] - https://github.com/conventional-changelog/conventional-chang...[2] - https://github.com/pyroscope-io/pyroscope/blob/main/CHANGELO...