Skip to content

docs: add workaround for false-positive update banner on brew/winget#33351

Open
SebTardif wants to merge 2 commits intoanthropics:mainfrom
SebTardif:fix-18047-doc-known-issue
Open

docs: add workaround for false-positive update banner on brew/winget#33351
SebTardif wants to merge 2 commits intoanthropics:mainfrom
SebTardif:fix-18047-doc-known-issue

Conversation

@SebTardif
Copy link
Copy Markdown

@SebTardif SebTardif commented Mar 11, 2026

Summary

  • adds a known-issue note for false-positive Update available banners on Homebrew and WinGet installs
  • explains the version-channel mismatch (npm latest vs package manager registry lag)
  • documents temporary workaround: DISABLE_AUTOUPDATER=1

Context

Fixes confusion reported in #18047 (and related duplicates) where users see an update prompt but brew upgrade or winget upgrade reports no newer package version.

Why docs

The public repository currently does not include the runtime updater implementation, so this change provides immediate user guidance while a runtime fix is developed in the appropriate codebase.

Copilot AI review requested due to automatic review settings March 11, 2026 20:43
@SebTardif
Copy link
Copy Markdown
Author

Corrected data point from my machine (Linux + Homebrew in WSL):

  • At startup on Claude Code version 2.1.72, the app showed: Update available! Run: brew upgrade claude-code
  • At that moment, this can still be a mismatch window where update guidance appears noisy
  • Shortly after, Homebrew cask advanced and brew upgrade --cask claude-code upgraded 2.1.72 -> 2.1.73
  • claude --version now reports 2.1.73 (Claude Code)

This supports the channel-lag hypothesis: npm/runtime may advertise newer availability before downstream package registries fully converge.

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds user-facing documentation to reduce confusion when Claude Code shows an “Update available” prompt despite Homebrew/WinGet reporting no newer package version (issue #18047), by explaining the npm vs package-registry lag and providing a temporary opt-out.

Changes:

  • Documented a known issue where update banners can be false-positive for Homebrew/WinGet installs.
  • Explained the underlying version-channel mismatch (npm latest vs Homebrew/WinGet lag).
  • Added a temporary workaround using DISABLE_AUTOUPDATER=1, with bash and PowerShell examples.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@SebTardif
Copy link
Copy Markdown
Author

Addressed the formatting review items in commit 3cf7b57:

  • Updated heading style to match README conventions:
    • ## Known issue with false-positive update banner (Homebrew/WinGet)
  • Expanded workaround safety guidance:
    • Added warning that DISABLE_AUTOUPDATER=1 also suppresses legitimate update notifications
    • Added explicit re-enable commands for both bash and PowerShell

Please re-review when convenient.

@SebTardif SebTardif force-pushed the fix-18047-doc-known-issue branch from 9208a46 to a30807e Compare March 11, 2026 20:59
@SebTardif
Copy link
Copy Markdown
Author

Scope cleanup: removed unrelated /commit-push-pr instruction/doc changes from this PR.

PR #33351 now contains only README.md updates related to issue #18047.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants