Repository navigation
corepack installs pnpm pre-releases if there exists any with a version superior than latest #473
Description
When running corepack up on a project that uses pnpm v9, it seems to update to a pre-release version, 9.1.0-0
When running corepack up on a project that uses pnpm v9, it seems to update to a pre-release version, 9.1.0-0
Activity
SuperchupuDev commentedon May 6, 2024
This no longer happens now that pnpm
9.1.0is out, but there's no reason to believe it won't happen in future pnpm pre-releases[-]corepack installs pre-release version of pnpm `9.1.0-0`[/-][+]corepack installs pnpm pre-releases if there exists any with a version superior than latest[/+]SuperchupuDev commentedon Jun 28, 2024
9.5.0-beta.0is out and this is still happening btwhyunbinseo commentedon Dec 15, 2024
It's currently installing
pnpm@10.0.0-beta.3version. This is not desirable.corepack install --global pnpm # Installing pnpm@10.0.0-beta.3...magicdawn commentedon Jul 25, 2025
specify
@latesttag will not allow pre-releasefor example
corepack use pnpm@latestackvf commentedon Dec 10, 2025
using
corepack use pnpmwithout the@latestwill install latest. This is what I got.smac89 commentedon Jul 19, 2026
Rather than blindly specifying
@latest, use the major version of the latest version you need, and that seems to solve the problem.MikeMcC399 commentedon Jul 19, 2026
corepack enable pnpm corepack install pnpm -gshould install a working non-pre-release version. Instead it installs
pnpm@12.0.0-alpha.15pnpm@12.0.0-rc.6.pnpm@12.0.0-alpha.15doesn't work (see issue #873 & pnpm/pnpm#13018).The pnpm version selected by
corepack install pnpmorcorepack use pnpmshould be the same one displayed by:which is currently
pnpm@11.15.0.At the moment, this issue affects only pnpm.
corepack install pnpm -gselectspnpm@12.0.0-alpha.15pnpm@12.0.0-rc.6corepack install npm -gselectsnpm@12.0.2corepack install yarn -gselectsyarn@4.18.0This issue has been open for some time now, and it seems that nobody is available to address it. It resurfaces as a problem every time there is a pre-release phase of npm or pnpm when pre-release versions are published to the npm registry.
The pnpm@12 pre-release phase started with https://www.npmjs.com/package/pnpm/v/12.0.0-alpha.0 on Jul 5, 2026.
MikeMcC399 commentedon Jul 20, 2026
A possible temporary workaround to get the latest non-pre-release version of pnpm (currently
pnpm@11.15.1) could be:corepack install pnpm@$(npm view pnpm version) -gor
corepack use pnpm@$(npm view pnpm version)It does not solve the original issue with
corepack up, however I don't see this problem occurring at the moment because the highest pre-release is forpnpm@12.0.0. It can however potentially happen again in future, if there is a mixture ofpnpm@12pre-release and non-prerelease versions published.corepack uppnpm@9.0.0pnpm@9.15.9pnpm@10.0.0pnpm@10.34.5pnpm@11.0.0pnpm@11.15.1pnpm@12.0.0-alpha.0pnpm@12.0.0-alpha.16