BUG/REQUEST - CHANGELOG missing entries, not always up to date

Resolved 💬 3 comments Opened Jun 19, 2025 by hesreallyhim Closed Jun 19, 2025

The CHANGELOG published on this repo and the info that Claude Code prints on /release-notes is (i) not immediately updated when there is a release; (ii) there are just releases that are skipped.

Is this a reason for not documenting releases? Even an obligatory "Internal refactors" or something would be nice.

E.g. there is no entry for 1.0.26

It would be great to have a complete CHANGELOG that's updated as part of the release cadence.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗