Conversation
mx update reported the registry's advertised latest (`latestInMajor`) as the version it "updated to", assuming `npm i` installs exactly what `npm view` advertises and treating exit 0 as proof. Those disagree behind a lagging mirror or virtual-repo proxy: the registry can advertise a version whose tarball it can't yet serve, so `npm i -g` reinstalls the same version and still exits 0 — and mx claimed the upgrade (e.g. "Updated to v4.7.0" while 4.6.0 actually installed), then ran a pointless auto-sync. After the install, re-read the version actually on disk via `npm ls -g` and report that. `updated` is now true only when a genuinely newer version landed (so the auto-sync is skipped otherwise). When a newer version was advertised but didn't install, surface a `staleRegistry` state that names both versions and points at a direct `--registry https://registry.npmjs.org` install. Adds `installedVersion` and `staleRegistry` to the porcelain output. Bump 4.7.1. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
mx updatereported the registry's advertised latest as the version it "updated to", trusting thatnpm iinstalls whatnpm viewadvertises and that exit 0 proves it. Behind a lagging mirror / virtual-repo proxy those disagree (registry advertises a version whose tarball it can't serve;npm ireinstalls the same version, exits 0) — so mx falsely claimed the upgrade and ran a pointless auto-sync.Now it re-reads the actually-installed version via
npm ls -gand reports that;updatedis true only on a genuine upgrade (auto-sync skipped otherwise). A newstaleRegistrystate names both versions and points at a direct--registry https://registry.npmjs.orginstall. AddsinstalledVersion/staleRegistryto porcelain.Bump 4.7.1.