Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Corepack install -g doesn't update known good releases #503

Open
robigan opened this issue Jun 17, 2024 · 0 comments
Open

Corepack install -g doesn't update known good releases #503

robigan opened this issue Jun 17, 2024 · 0 comments

Comments

@robigan
Copy link

robigan commented Jun 17, 2024

The documentation states that the known good releases of system wide binaries can be updated using corepack install -g:

Known Good Releases
When running Corepack within projects that don't list a supported package manager, it will default to a set of Known Good Releases.
If there is no Known Good Release for the requested package manager, Corepack looks up the npm registry for the latest available version and cache it for future use.
The Known Good Releases can be updated system-wide using corepack install -g. When Corepack downloads a new version of a given package manager on the same major line as the Known Good Release, it auto-updates it by default.

and

Package managers thus installed will be configured as the new default when calling their respective binaries outside of projects defining the packageManager field.

Yet when I tell corepack to install [email protected] globally, and try to invoke yarn --version it tells me that yarn is using [email protected]. I have cleaned my cache and attempted to install [email protected] globally and then attempt to invoke yarn before the default would get downloaded but I get a prompt telling me to use [email protected].

image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant