[BUG] Hard to trace changes in releases
Status Fixed / completed
Maintainer reply ✓ Yes — bcherny
Activity 7 comments · opened Aug 8, 2025 · closed Aug 9, 2025
💡 Likely answer: A maintainer (bcherny, collaborator)
responded on this thread — see the highlighted reply below.
Environment
- Platform (select one):
- [ ] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [x] Other: <!-- specify -->
- Claude CLI version: 1.0.72
- Operating System: Macos 14.5
- Terminal: zsh
Bug Description
Who knows what 1.0.72 has bring looking at github? Big riddle.
Steps to Reproduce
- Update to newest version of anthropic
- Run claude --verision and read version
- Try to find out over Internet what has changed
Expected Behavior
You see clear message of what is going on
Actual Behavior
Dev/null - maybe Martians already hacked Claude code, but you won't find out in anyway
Additional Context
Be descriptive in Github, in change long, in claude code it self (let --version print changes below the version print)
7 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Anthropic has a tendency of pushing updates to NPM and then after a period of time (hours/days) only updating the official release notes (both in Claude Code) and official release notes website.
There's always a lag.
Hi! The changelog is auto-published with each release: https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md
Knowing what I'm updating would be nice. We've had like 3 updates today. CHANGELOG.md is still way behind.
@bcherny your statement does not seem to match reality. The changelog is as of now 6 releases behind.
I don't grasp this situation. You're developing a coding agent that leverages LLMs designed for summarization and reasoning - essentially knowledge synthesis. This agent is supposed to automate work. Yet as a company, you can't automate changelog generation. Perhaps this small contradiction will make Claude Code even stronger. You might discover certain limitations in your product that prevent changelog automation. Or maybe this situation reveals a problem in your development process - changes without business coverage or justification? Consider this feedback as an opportunity, not an issue.
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.