fix(@angular/cli): correctly handle yarn classic tag manifest fetching #32025
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.
Introduces a
requiresManifestVersionLookupproperty toPackageManagerDescriptorto control whether a package manager needs an explicit metadata lookup for tags, ranges, or when nofetchSpecis provided before attempting to fetch the full registry manifest.This change optimizes manifest fetching by enabling a preliminary metadata lookup for package managers like
yarn-classicthat require it to resolve tags and ranges to concrete versions.