Repository navigation
Conversation
pederbe
marked this pull request as ready for review
November 4, 2026 10:15
This branch has not been deployed
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
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.
Repositories with exact version pins currently prompt to install each missing version, even when a newer version of the same major is already installed.
Add
--fallback-to-latest-in-majorto opt into the latest newer installed stable version whenfnm usereads a missing exact stable version from a file. For example, a missing.nvmrcpin of20.6.1can select an installed20.20.0. Enable it alongside automatic switching:Exact installed matches still win. Explicit version arguments, aliases, prerelease requests, engines ranges and other commands keep their existing behavior. Fallback stays within the requested major and does not download a version. The selection message identifies both versions.
The existing Corepack alias test now uses a named LTS that bundles Corepack. Its previous
lts/*fixture fails on the unchanged base because the latest LTS no longer includes the executable. The adjacent test still covers latest-LTS alias installation.Closes #1500.