[BUG] Outdated CHANGELOG

Status Fixed / completed
Maintainer reply ✓ Yes — dicksontsai
Activity 7 comments · opened Jun 19, 2025 · closed Jun 26, 2025
💡 Likely answer: A maintainer (dicksontsai, collaborator) responded on this thread — see the highlighted reply below.

Despite CC being at version 1.0.30, the /release-notes ends the journey at 1.0.27

View original on GitHub ↗

7 Comments

hesreallyhim · 1 year ago

@MarcinOrlowski can you consider amending this as a bug/feature request or something to ask that CHANGELOGs should be updated when there is a release? I was going to file an Issue anyway.
https://keepachangelog.com/en/1.1.0/
thanks

hesreallyhim · 1 year ago

actually another question is why are they skipping releases in the CHANGELOG, ~~does the changelog only document public-facing updates?~~ Actually, if there's a release the changelog should show it, even like "internal refactor" or something, this is bad practice IMO

ktnyt · 1 year ago

This needs to be addressed ASAP imo.

Users are left in the dark to figure out updates by themselves which is not good development practice.
Especially when auto-updates are de-facto enabled and destructive changes such as the bug fixed in 1.0.31 are a possibility.
https://github.com/anthropics/claude-code/blob/21cf5c2293f4e0c517320d585589b85e29fb9c7f/CHANGELOG.md?plain=1#L3-L5

The semantic versioning scheme is currently untrustworthy too, as 1.0.28 was a backwards-incompatible change (the move from ~/.claude to $XDG_CONFIG_HOME/claude) yet update was only in the patch version.

While I appreciate the immense amount of effort in development, the governance and quality control aspects of the project seems to be lacking in the moment.

dicksontsai collaborator · 1 year ago
The semantic versioning scheme is currently untrustworthy too

We do not guarantee semantic versioning for our version numbers. Each version simply represents a new release (usually once a day, sometimes more).

why are they skipping releases in the CHANGELOG

No specific reason. We try to keep it up to date with noteworthy changes but may not be able to keep it _perfectly_ up to date. You can assume that versions without changelog entries have nothing noteworthy (e.g. minor bug fixes like https://github.com/anthropics/claude-code/issues/2200).

MarcinOrlowski · 1 year ago

Please do not release without entry in changelog - its dev tool and i guess majority would like to know what changed regardless its minor or major change.

PS: Can you also datestamp releases?

hesreallyhim · 1 year ago

@dicksontsai thank you for the reply. I'm not sure I'm convinced, since a changelog isn't the same thing as holding a press conference, it doesn't matter if the release is just a small fix. I think a bigger value would be that people would feel more trust in the application, and not feel sometimes like it's shifting all the time, which undermines confidence in the reliability of a developer's workflow.

github-actions[bot] · 1 year ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.