Zoltan Kochan
290bb5bd38
Version tags were created in CI with `git tag "$tag" "$SHA"` — a lightweight tag, which has no tag object to carry a signature. Since v11.18.0 that made `git verify-tag` fail with "cannot verify a non-tag object of type commit", breaking downstream packagers who verify the tag before building. Signing those tags in CI would restore verify-tag but not the property that makes it worth verifying: the key would live in Actions secrets, inside the same trust boundary the signature is meant to attest independently of. Cut tags from a maintainer machine instead, and have release.yml verify the tag before any publish job runs. verify-release-tag imports the public keys committed under .github/release-keys into a throwaway GNUPGHOME and runs `git verify-tag` on the pushed tag. Every publish path descends from `plan` and `plan` descends from that job, so one edge gates all three products. Verified against a signed tag, a lightweight tag, an annotated unsigned tag, and a tag signed by a key outside the directory: only the first proceeds. The keyring is isolated so verification cannot succeed against a key already on the runner, and checkout sets fetch-tags because a tag push checks out the commit while the signature lives on the tag object. The non-tag verify_ts_release dispatch exits from inside the step rather than a job-level `if`, since a skipped job skips everything that needs it. This guards against unsigned tags, not against an actor who can push arbitrary ones: a tag push runs the workflow file and checks out the tree from the pushed tag. Restricting creation of v* and pnpr@* tags is a repository ruleset concern. RELEASING.md documents the manual procedure: tag an explicit commit, verify every tag before pushing, and retag at the fixed commit to retry a failed release. Related to pnpm/pnpm#13578
简体中文 | 日本語 | 한국어 | Italiano | Português Brasileiro
Fast, disk space efficient package manager:
- Fast. Up to 2x faster than the alternatives (see benchmark).
- Efficient. Files inside
node_modulesare linked from a single content-addressable storage. - Great for monorepos.
- Strict. A package can access only dependencies that are specified in its
package.json. - Deterministic. Has a lockfile called
pnpm-lock.yaml. - Works as a Node.js version manager. See pnpm runtime.
- Works everywhere. Supports Windows, Linux, and macOS.
- Battle-tested. Used in production by teams of all sizes since 2016.
- Experimental Rust port. Includes pacquet, an experimental port of the CLI written in Rust.
- See the full feature comparison with npm and Yarn.
To quote the Rush team:
Microsoft uses pnpm in Rush repos with hundreds of projects and hundreds of PRs per day, and we’ve found it to be very fast and reliable.
Platinum Sponsors
|
|
Gold Sponsors
|
|
|
|
|
|
|
|
Silver Sponsors
|
|
|
|
|
|
|
|
|
| ⏱️ Time.now |
Support this project by becoming a sponsor.
Background
pnpm uses a content-addressable filesystem to store all files from all module directories on a disk. When using npm, if you have 100 projects using lodash, you will have 100 copies of lodash on disk. With pnpm, lodash will be stored in a content-addressable storage, so:
- If you depend on different versions of lodash, only the files that differ are added to the store.
If lodash has 100 files, and a new version has a change only in one of those files,
pnpm updatewill only add 1 new file to the storage. - All the files are saved in a single place on the disk. When packages are installed, their files are linked from that single place consuming no additional disk space. Linking is performed using either hard-links or reflinks (copy-on-write).
As a result, you save gigabytes of space on your disk and you have a lot faster installations!
If you'd like more details about the unique node_modules structure that pnpm creates and
why it works fine with the Node.js ecosystem, read this small article: Flat node_modules is not the only way.
💖 Like this project? Let people know with a tweet
Getting Started
Benchmark
pnpm is up to 2x faster than npm and Yarn classic. See all benchmarks here.
Benchmarks on an app with lots of dependencies:
License
MIT, except the pnpr/ directory, which is source-available under the PolyForm Shield License 1.0.0.