claude-code - 💡(How to fix) Fix `/release-notes` should indicate which version is current stable (per `/doctor`)

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…
RAW_BUFFERClick to expand / collapse

/doctor distinguishes a "stable" version from the newest version on npm. /release-notes does not — it lists every version sequentially with no marker for which one /doctor would currently recommend.

Result: users reading /release-notes have no signal about update safety and tend to upgrade on every release, even when stable is significantly behind.

Concrete example from today (2026-05-07): /doctor reports stable = 2.1.119, latest = 2.1.132 — a 12-version gap. Nothing in /release-notes between 119 and 132 indicates this. Several intermediate releases contain regressions that were only fixed in 132 (e.g., the --resume emoji-surrogate corruption fix in 132 implies a real bug in 120–131).

Suggested fix: mark the current stable version in /release-notes output, or visually separate "stable and below" from "newer than stable." Aligning the two surfaces would let users make informed cadence decisions.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING