[BUG] claude update reports up-to-date on 2.1.104 while 2.1.116 is latest stable
Status Fixed / completed
Reported on v2.1.104
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 3 comments · opened Apr 21, 2026 · closed Apr 21, 2026
Bug Description
claude update and the install script (curl -fsSL https://claude.ai/install.sh | bash) both resolve the latest stable version as 2.1.104, while the changelog shows 2.1.116 as the latest release.
Steps to Reproduce
- Run
claude update:
````
Current version: 2.1.104
Checking for updates to stable version...
Claude Code is up to date (2.1.104)
- Re-install via the install script:
``bash`
curl -fsSL https://claude.ai/install.sh | bash
`
Output:
``
Setting up Claude Code...
✔ Claude Code successfully installed!
Version: 2.1.104
- Both report 2.1.104 as latest, but https://code.claude.com/docs/en/changelog shows 2.1.116.
Workaround
Passing the version explicitly to the install script works:
curl -fsSL https://claude.ai/install.sh | bash -s -- 2.1.116
This bypasses the version resolution and installs 2.1.116 correctly.
Expected Behavior
claude update and the install script should resolve to 2.1.116 (or whatever the actual latest stable release is).
Environment
- Platform: macOS (Apple Silicon)
- Installation method: Native binary via install.sh
- Current version: 2.1.104 (reports as up-to-date)
- Actual latest: 2.1.116
3 Comments
Additional investigation
The version resolver is working correctly — the issue is that the
stablechannel endpoint hasn't been updated past 2.1.104.Evidence:
The install script always downloads the
latestbinary (for the installer itself), then delegates toclaude installwhich respects the channel. Soclaude updateon thestablechannel correctly resolves to 2.1.104 per the server.The changelog at https://code.claude.com/docs/en/changelog doesn't distinguish between stable and latest channels, which creates the impression that 2.1.116 is the latest stable when it's actually only on the
latestchannel.Workaround: Switch to the
latestchannel in~/.claude/settings.json:Or install a specific version explicitly:
Additional symlink bug: When using the explicit version workaround (
bash -s -- 2.1.116), the install script may not update the symlink at~/.local/bin/claude— it can remain pointing to the old version. Manual fix:ln -sf ~/.local/share/claude/versions/2.1.116 ~/.local/bin/claudeClosing — this is not a bug in the version resolver.
Root cause: The
stablenpm dist-tag (and the correspondinghttps://downloads.claude.ai/claude-code-releases/stableendpoint) genuinely points to 2.1.104. The updater is working correctly.The confusion comes from the changelog not distinguishing stable vs latest channel — it lists all versions without labels, making it look like 2.1.116 should be available on stable.
Workaround: Switch to the
latestchannel in~/.claude/settings.json: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.