[BUG] autoUpdatesChannel: "stable" ignored - updates to latest instead
Resolved 💬 3 comments Opened Feb 6, 2026 by cxr344 Closed Feb 11, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
The autoUpdatesChannel: "stable" setting in settings.json is correctly recognized by claude doctor but ignored during the actual update operation. Claude updates to the latest version instead of the stable version. In this case I was starting from 2.1.5 w/ autoupdates disabled, and was upgraded straight to 2.1.34 instead of 2.1.25.
What Should Happen?
Should update to the stable version (2.1.25 at time of report)
Error Messages/Logs
Diagnostics
└ Currently running: npm-global (2.1.34)
Updates
└ Auto-updates: enabled
└ Update permissions: Yes
└ Auto-update channel: stable <-- Setting is recognized
└ Stable version: 2.1.25 <-- But this was ignored
└ Latest version: 2.1.34 <-- Updated to this instead
Steps to Reproduce
- Configure
~/.claude/settings.json:
```json
{
"autoUpdatesChannel": "stable"
}
- Be on an older version (I was on 2.1.5)
- Run claude doctor or allow auto-update to trigger
Claude Model
Opus
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.34
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Windows Terminal
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗