[BUG] Auto-update channel set to "stable" but updated beyond Stable version to Latest version

Resolved 💬 4 comments Opened Apr 10, 2026 by sunyzc Closed May 24, 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?

Auto-update channel is set to stable, but Claude Code auto-updated to 2.1.100, which is beyond the reported Stable version (2.1.89).

/doctor output:

  • Currently running: npm-global (2.1.100)
  • Auto-update channel: stable
  • Stable version: 2.1.89
  • Latest version: 2.1.100

What Should Happen?

When auto-update channel is set to stable, Claude Code should only update to the version reported as "Stable version" in /doctor.

If 2.1.100 is indeed the new stable release, then the Stable version label in /doctor should reflect 2.1.100, not 2.1.89. The current display is misleading.

Error Messages/Logs

Steps to Reproduce

  1. Install Claude Code at version 2.1.89 with auto-update channel set to "stable"
  2. Wait for auto-update to trigger
  3. Run /doctor — observe that "Currently running" shows 2.1.100, but "Stable version" still shows 2.1.89

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

2.1.99

Claude Code Version

2.1.100

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

The /doctor display labels are confusing:

  • "Stable version: 2.1.89" reads as "the current stable release is 2.1.89"
  • "Latest version: 2.1.100" reads as a separate, newer track

If both are actually the same track, the labels should be clarified (e.g., "Installed version" vs "Latest stable version").

View original on GitHub ↗

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