pnpm 12 Alpha 21
- pnpm outdated accepts the --include-github-actions option
- pnpm setup now appends PNPM_HOME and the global bin directory to the GitHub Actions environment files (GITHUB_ENV and GITHUB_PATH), so later steps in the same job can run pnpm add --global and other global commands
- Checking GitHub Actions dependencies for updates is now opt-in for every command via --include-github-actions flag or update.githubActions setting in pnpm-workspace.yaml
- pnpm update --latest now keeps dependencies that the npm registry does not serve in the form they were declared instead of overwriting their specifier
- pnpm update --latest no longer rewrites package.json when a dependency is already at its latest version
Minor Changes
pnpm setupnow appendsPNPM_HOMEand the global bin directory to the GitHub Actions environment files (GITHUB_ENVandGITHUB_PATH), so later steps in the same job can runpnpm add --globaland other global commands #9191.
Patch Changes
-
Checking GitHub Actions dependencies for updates is now opt-in for every command. Neither
pnpm outdatednorpnpm updatereads the workflow files unless--include-github-actionsis passed orupdate.githubActionsis set totrueinpnpm-workspace.yaml. Reading them runsgit ls-remoteagainst every referenced repository, which fails in environments where GitHub is not reachable the way pnpm assumes (a GitHub Enterprise Server, a custom certificate authority, or an offline network) #13254.pnpm outdatedaccepts the--include-github-actionsoption too. -
pnpm update --latestnow keeps dependencies that the npm registry does not serve in the form they were declared. Aruntime:dependency (such as"node": "runtime:26.5.0"), agit/github:URL, or a remote tarball URL previously had its name looked up on the npm registry and its specifier overwritten with that unrelated package's version.pnpm update --latestalso no longer rewritespackage.jsonwhen a dependency is already at its latest version.