As suggested in #3334, a CHANGELOG.md file makes it easy for newcomers and occasional users to see the status of the nightly builds versus the stable, released version.

My advice is that the CHANGELOG contain user-facing changes (updates to SQLite, new features, bug fixes, etc) but not changes to the documentation, build process, etc. since they're not as interesting to casual users. Other developers can always check the PR logs to see exactly what has changed.

The beauty of keeping this file up to date is that when the time comes to release a new version, it's fairly straightforward to review and update the Unreleased - nightly section to produce the first cut of the announcement for the new version.