Run AI upgrades with the latest official canary (#98870)
### Why? `next@canary` can reuse a cached `canary.33` even after `canary.35` is published, causing `next upgrade --ai` to run outdated upgrade logic. ### How? Resolve the latest official canary from public npm, then reuse the running CLI if it matches or launch and verify that exact version. Keep pnpm installation errors visible so failed launches are diagnosable. The lookup does not use package-manager registry, proxy, or CA settings: public npm must be reachable, and installation can fail if a configured mirror lacks the selected version. <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment