Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Auto-update channel set to "stable" but updated beyond Stable version to Latest version [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46145•Fetched 2026-04-11 06:27:53
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
sunyzcsunyzc
Participants
github-actions[bot]github-actions[bot]sunyzcsunyzc
Timeline (top)
labeled ×3commented ×2cross-referenced ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • 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").

extent analysis

TL;DR

  • The auto-update channel should be reviewed to ensure it correctly follows the intended "stable" version, and the /doctor output labels should be clarified for accuracy.

Guidance

  • Verify the actual latest stable version of Claude Code to confirm if 2.1.100 is indeed the new stable release.
  • Check the auto-update mechanism to ensure it is correctly set to only update to the stable version, not the latest version.
  • Consider reaching out to the development team to clarify the discrepancy between the "Stable version" and "Latest version" labels in the /doctor output.
  • Review the documentation for the auto-update channel settings to ensure they are correctly configured for the desired update track.

Example

No specific code snippet is applicable in this case, as the issue pertains to the configuration and behavior of the Claude Code auto-update feature.

Notes

  • The issue may stem from a misunderstanding of the versioning and update tracks, emphasizing the need for clear documentation and labeling.
  • Clarification from the development team on the intended behavior of the auto-update feature and the meaning of the labels in the /doctor output is necessary.

Recommendation

  • Apply workaround: Temporarily disable auto-update until the discrepancy between the stable and latest versions is resolved, to prevent unintended updates beyond the desired stable version. This is recommended because it allows for control over the update process while the issue is being addressed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#model loading#dependency error#configuration error#environment variable

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING