[Bug]: Native Claude update reports "still outdated" while the native release feed lags npm's latest tag #27942

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Related, not a duplicate: #26400 and its fix #26518 cover native Claude on the stable channel. This report is the latest channel, which #26518 leaves on main's behaviour.

Area

apps/server

Steps to reproduce

1. Install Claude Code with the native installer, so claude resolves to ~/.local/bin/claude(.exe).
2. Keep "autoUpdatesChannel": "latest" in ~/.claude/settings.json (or leave it unset).
3. Wait for a release that npm's latest dist-tag has but the native release feed does not have yet. At the time of this report:
   • npm: latest 2.1.316
   • native feed claude-code-releases/latest (the GCS bucket claude update reads): 2.1.314
4. Open Settings → Providers. Claude shows an update. Click Update now.

Expected behavior

For a native install, T3 compares the installed version against the native release feed that claude update installs from. 2.1.314 is the newest build that channel offers, so T3 shows Claude as current and offers no update.

Actual behavior

claude update prints "Claude Code is up to date (2.1.314)" and exits 0. T3 probes again, still compares 2.1.314 against npm's 2.1.316, and shows "Update command completed, but T3 Code still detects an outdated provider version." Every retry gives the same result until Anthropic publishes the build to the native feed.

The cause is the same as #26400. fetchNpmLatestVersion (packages/provider-core/src/server/maintenanceResolver.ts:820) reads registry.npmjs.org/@anthropic-ai/claude-code/latest, while the native resolver in apps/server/src/provider/Drivers/ClaudeDriver.ts runs claude update. npm publishes before the native feed, so this happens on the latest channel too, for hours after each npm release.

One possible fix: in the native lookupLatestVersion that #26518 adds, read claude-code-releases/{latest,stable} from the native feed instead of the npm dist-tag. That covers both channels with one lookup. The stable channel lags the same way: npm stable is 2.1.309 while the native feed's stable is 2.1.308, so the npm stable dist-tag in #26518 would still give a false update here.

Impact

Minor bug or occasional failure

Version or commit

T3 Code v0.1.6-nightly.20261029.3892; main @ 960d576 still reads npm latest

Environment

Windows 11 Pro (AKIRA-PC) and two Linux hosts, all with the same result. Claude Code 2.1.314 native install, autoUpdatesChannel: latest.

Logs or stack traces

$ claude update
Current version: 2.1.314
Checking for updates to latest version...
Claude Code is up to date (2.1.314)

$ npm view @anthropic-ai/claude-code dist-tags
{ "stable": "2.1.309", "next": "2.1.316", "latest": "2.1.316" }

$ curl -s https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/latest
2.1.314
$ curl -s https://storage.googleapis.com/claude-code-dist-86c565f3-f756-42ad-8dfa-d59b1c096819/claude-code-releases/stable
2.1.308

T3 toast, on all three hosts:

Update failed
AKIRA-PC · Claude: Update command completed, but T3 Code still detects an outdated provider version.
proxima · Claude: Update command completed, but T3 Code still detects an outdated provider version.
vivobook · Claude: Update command completed, but T3 Code still detects an outdated provider version.

Workaround

None needed. The warning clears once the native feed catches up to npm.