Change8

Migrating to pnpm v12.0.0-alpha.21

Version v12.0.0-alpha.21 introduces 1 breaking change. This guide details how to update your code.

Released: 7/24/2026

1
Breaking Changes
1
Migration Steps
4
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

`pnpm setup``pnpm outdated``pnpm update``pnpm update --latest`

Breaking Changes

Issue #1

Previously, `pnpm update --latest` would overwrite dependency specifiers for `runtime:`, `git:`, `github:`, or remote tarball URLs with versions from unrelated packages found in the npm registry. This behavior has been corrected, and these dependencies will now be kept in their declared form. This might be a breaking change if you relied on the incorrect overwriting behavior.

Migration Steps

  1. 1
    To include GitHub Actions dependencies in `pnpm outdated` or `pnpm update`, use the `--include-github-actions` flag or set `update.githubActions` to `true` in `pnpm-workspace.yaml`.

Release Summary

This release makes GitHub Actions dependency updates opt-in by default and improves how `pnpm update --latest` handles various dependency types. `pnpm setup` also now better integrates with GitHub Actions environments.

Need More Details?

View the full release notes and all changes for pnpm v12.0.0-alpha.21.

View Full Changelog