chore(release): 11.7.0 (#12414)

This commit is contained in:
Zoltan Kochan
2026-06-15 08:37:08 +02:00
committed by GitHub
parent cd8348c6e9
commit 1e82e001cd
332 changed files with 3173 additions and 438 deletions

View File

@@ -1,19 +1,32 @@
batch-publish-single-request
catalog-range-spec-update-crash
clean-package-manager-registries
clever-rocks-listen
clever-warnings-guide
contain-hoisted-dependency-aliases
deps-status-no-manifest
destroy-windows-dispatchers
deterministic-shared-children-resolution
dollar-overrides-deprecation
fast-repeat-install-restores-lockfile
fix-concurrent-import-partial-pkg
fix-config-globalconfig
fix-interactive-prompt-summary
fix-patch-remove-containment
fix-publish-strict-ssl
fix-windows-recursive-undefined-manifest
frozen-store
fuzzy-color-flags
git-tarball-path-in-lockfile
gvs-rebuild-native-deps
gvs-toggle-detection
hot-schools-speak
locked-peer-pin-no-sibling-leak
lockfile-verification-cached-message
loose-meteors-travel
pacquet-install-engine-identity
pacquet-resolving-install-delegation
parallel-lockfile-verification
pnpr-client-ndjson-resolve
pnpr-forward-credentials
pnpr-forward-optional-deps
@@ -21,17 +34,26 @@ pnpr-inline-only-access
pnpr-lockfile-only
pnpr-resolve-only
prefer-locked-peer-contexts
preserve-user-npm-config-vars
quick-registries-env-auth
quiet-peers-settle
raise-default-network-concurrency
rename-agent-to-pnpr-server
runtime-not-cataloged
scoped-registry-auth
setup-skip-exe-build-scripts
sharp-registry-env-placeholders
short-lamps-relax
slow-windows-lockfile-streams
spicy-pots-wonder
spotty-citrus-fix
stale-stage-tarballs
store-discl
strange-bin-segments
sweet-groups-float
tarball-url-binding
tough-allow-builds-identities
update-dependency-ranges
update-zkochan-cmd-shim
verify-node-runtime-shasums
windows-error-exit-pidtree

View File

@@ -1,6 +0,0 @@
---
"@pnpm/releasing.commands": minor
"pnpm": minor
---
Added a new opt-in `--batch` flag to `pnpm publish --recursive` that sends all selected packages to the registry in a single `PUT /-/pnpm/v1/publish` request instead of one request per package. The target registry has to implement the batch publish endpoint (pnpr does); registries that don't are reported with a clear `ERR_PNPM_BATCH_PUBLISH_UNSUPPORTED` error. The batch is processed all-or-nothing by pnpr: if any package in the batch fails validation, none of the packages are published.

View File

@@ -1,14 +0,0 @@
---
"@pnpm/fs.symlink-dependency": patch
"@pnpm/installing.deps-resolver": patch
"@pnpm/installing.deps-installer": patch
"@pnpm/installing.deps-restorer": patch
"pnpm": patch
---
Reject path-traversal and reserved dependency aliases (such as `../../../escape`, `.bin`, `.pnpm`, or `node_modules`) that come from a lockfile rather than a freshly resolved manifest. A crafted lockfile alias could otherwise be joined directly under a hoisted `node_modules` directory, letting package files be written outside the intended install root or overwrite pnpm-owned layout.
The fix adds two layers:
- The `nodeLinker: hoisted` graph builder now validates each alias at the directory sink (`safeJoinModulesDir`), matching the validation pnpm already performs when resolving aliases from manifests.
- The lockfile verification gate (`verifyLockfileResolutions`) now runs an always-on, policy-independent check that rejects any importer or snapshot dependency alias that is not a valid package name, failing the install early — before any fetch or filesystem work — for every node linker at once.

View File

@@ -1,6 +0,0 @@
---
"@pnpm/installing.deps-resolver": patch
"pnpm": patch
---
Made shared package child resolution deterministic when the same package is reached through multiple contexts. pnpm now chooses the shallowest occurrence, then importer order, then parent path, instead of letting request timing decide the child context and missing-peer report [pnpm/pnpm#12358](https://github.com/pnpm/pnpm/issues/12358).

View File

@@ -1,7 +0,0 @@
---
"@pnpm/installing.commands": patch
"@pnpm/deps.compliance.commands": patch
"pnpm": patch
---
Fix garbled summary line after submitting `pnpm update -i` and `pnpm audit --fix -i`. The interactive checkbox prompt previously printed every selected choice's full table row (label, current/target versions, workspace, URL) joined by commas, producing a wall of text after pressing Enter. The summary now lists only the selected package names (or vulnerability keys) by setting an explicit `short` per choice; the in-progress selection UI is unchanged.

View File

@@ -1,6 +0,0 @@
---
"@pnpm/patching.commands": patch
"pnpm": patch
---
Prevent `pnpm patch-remove` from removing files outside the configured patches directory.

View File

@@ -1,6 +0,0 @@
---
"@pnpm/releasing.commands": patch
"pnpm": patch
---
Fixed `pnpm publish` ignoring `strictSsl: false` when publishing to registries with self-signed certificates. The `strictSSL` option is now forwarded to `libnpmpublish` / `npm-registry-fetch` so that `strict-ssl=false` in `.npmrc` or `strictSsl: false` in `pnpm-workspace.yaml` is respected during publish, the same way it is for `pnpm install` [pnpm/pnpm#12012](https://github.com/pnpm/pnpm/issues/12012).

View File

@@ -1,6 +0,0 @@
---
"@pnpm/installing.commands": patch
"pnpm": patch
---
Fixed `Cannot destructure property 'manifest' of 'manifestsByPath[rootDir]' as it is undefined` regression introduced in 11.6.0 when running `pnpm add <pkg>` outside a workspace on Windows. `selectProjectByDir` was keying the resulting `ProjectsGraph` by `opts.dir` instead of `project.rootDir`, so downstream `manifestsByPath` lookups missed when the two paths normalized differently (typically drive-letter casing). [pnpm/pnpm#12379](https://github.com/pnpm/pnpm/issues/12379)

View File

@@ -1,18 +0,0 @@
---
"@pnpm/config.reader": minor
"@pnpm/store.index": minor
"@pnpm/store.controller": minor
"@pnpm/store.connection-manager": minor
"@pnpm/building.after-install": patch
"@pnpm/building.during-install": patch
"@pnpm/bins.linker": patch
"@pnpm/resolving.npm-resolver": patch
"@pnpm/worker": minor
"@pnpm/installing.package-requester": minor
"@pnpm/installing.context": patch
"@pnpm/installing.deps-installer": minor
"@pnpm/installing.commands": minor
"pnpm": minor
---
Added a new setting `frozenStore` (`--frozen-store`) that lets `pnpm install` run against a package store on a read-only filesystem (e.g. a Nix store, a read-only bind mount, an OCI layer). When enabled, pnpm opens the store's SQLite `index.db` through the `immutable=1` URI — bypassing the WAL/`-shm` sidecar creation that otherwise fails on a read-only directory — and suppresses every store-write path (the `index.db` writer and the project-registry write). Pair it with `--offline --frozen-lockfile` against a fully-populated store. Under the global virtual store, package directories live inside the store, so if the store is missing the build output of a package whose lifecycle scripts are approved (or that has a patch), pnpm fails up front with `ERR_PNPM_FROZEN_STORE_NEEDS_BUILD` rather than crashing mid-build on a read-only write — seed the store with those builds first. Incompatible with `--force` and with a configured pnpr server, since both write into the store; the side-effects cache is likewise not written under `frozenStore`. If the store is missing its content directory, the install fails fast with `ERR_PNPM_FROZEN_STORE_INCOMPLETE` rather than attempting to initialize it. The read-only `immutable=1` open requires Node.js >=22.15.0, >=23.11.0, or >=24.0.0; on older runtimes `--frozen-store` fails with a clear `ERR_PNPM_FROZEN_STORE_UNSUPPORTED_NODE` error. Bin-linking also tolerates a read-only store: under the global virtual store a package's bin source lives inside the store, so the `chmod` that makes it executable would be refused — with `EPERM`/`EACCES`, or with `EROFS` on a genuinely read-only filesystem. That `chmod` is redundant when the seed already ships its bins executable with a normalized shebang, so it is now skipped in that case, while a non-executable bin (or one still carrying a Windows CRLF shebang) on a read-only store still errors.

View File

@@ -1,6 +0,0 @@
---
"@pnpm/lockfile.utils": patch
"pnpm": patch
---
Git dependencies that point to a subdirectory of a repository (`repo#commit&path:/sub/dir`) keep their `path` in the lockfile again. Since the integrity of git-hosted tarballs started being pinned in the lockfile, any install that actually downloaded the tarball rebuilt the lockfile resolution as `{ integrity, tarball, gitHosted }` and dropped the `path` field, while installs served from the store kept it — so the field disappeared seemingly at random. Without `path`, later installs from that lockfile silently unpacked the repository root instead of the subdirectory [#12304](https://github.com/pnpm/pnpm/issues/12304).

View File

@@ -1,5 +0,0 @@
---
"@pnpm/installing.commands": patch
---
Added support for the `--trust-lockfile` flag on `pnpm link`

View File

@@ -1,6 +0,0 @@
---
"@pnpm/installing.deps-resolver": patch
"pnpm": patch
---
Fixed nondeterministic lockfile output that made `pnpm dedupe --check` fail intermittently in CI. When a locked peer provider was pinned for a dependency that has no child dependencies of its own, the pinned provider leaked into the shared parent scope, so siblings resolved after it could pick up an optional peer they should not see. Which siblings were affected depended on resolution order, which varies with network timing.

View File

@@ -1,9 +0,0 @@
---
"@pnpm/installing.commands": minor
"@pnpm/installing.deps-installer": minor
"pnpm": minor
---
When [`pacquet`](https://github.com/pnpm/pnpm/tree/main/pacquet) (the Rust port of pnpm) is declared in `configDependencies`, pnpm now delegates dependency **resolution** to it too — not just materialization — provided the installed pacquet is new enough to support full resolving installs (>= 0.11.7).
Previously pacquet only ran in frozen-install mode: pnpm always resolved the dependency graph itself (writing `pnpm-lock.yaml`) and handed pacquet a finished lockfile to fetch / import / link. With pacquet >= 0.11.7, a non-frozen `pnpm install` (default isolated `nodeLinker`, plain install) is delegated to pacquet end-to-end in a single pass — pacquet resolves the manifests, writes the lockfile, and materializes `node_modules`. pnpm detects the capability from the installed pacquet's version; older pacquet releases keep the resolve-then-materialize split, and `add` / `update` / `remove` still resolve in pnpm (it has to mutate the manifests first). This remains an opt-in preview of the Rust install engine [#11723](https://github.com/pnpm/pnpm/issues/11723).

View File

@@ -1,7 +0,0 @@
---
"@pnpm/installing.deps-installer": patch
"@pnpm/installing.deps-restorer": patch
"pnpm": patch
---
Sped up `pnpm install` with a frozen lockfile by running lockfile verification (the policy revalidation gate added for `minimumReleaseAge`/`trustPolicy` and the tarball-URL anti-tamper check) concurrently with fetching and linking instead of blocking the whole install on it. Dependency lifecycle scripts are still held back until verification succeeds, so no script runs on an unverified lockfile: if verification fails the install aborts before any dependency build, and if linking finishes first the install waits for the verification verdict before completing.

View File

@@ -1,6 +0,0 @@
---
"@pnpm/exec.lifecycle": patch
"pnpm": patch
---
User-defined `npm_config_*` environment variables are now preserved during lifecycle script execution. Previously, all `npm_`-prefixed env vars were stripped, which caused user-set variables like `npm_config_platform_arch` to be lost [pnpm/pnpm#12399](https://github.com/pnpm/pnpm/issues/12399).

View File

@@ -1,34 +0,0 @@
---
"@pnpm/auth.commands": patch
"@pnpm/config.reader": patch
"@pnpm/fetching.tarball-fetcher": patch
"@pnpm/fetching.types": patch
"@pnpm/installing.deps-installer": patch
"@pnpm/network.auth-header": patch
"@pnpm/pnpr.client": patch
"@pnpm/releasing.commands": patch
"@pnpm/resolving.default-resolver": patch
"@pnpm/resolving.npm-resolver": patch
"@pnpm/types": patch
"pnpm": patch
---
pnpm can now use different auth tokens for different package scopes, even when those scopes use the same registry URL.
Previously, auth was selected only by registry URL. If `@org-a` and `@org-b` both used `https://npm.pkg.github.com/`, they had to share the same token. This caused problems for registries that issue tokens per organization or per scope.
Configure a scope-specific token by adding the package scope after the registry URL in the auth key:
```ini
@org-a:registry=https://npm.pkg.github.com/
@org-b:registry=https://npm.pkg.github.com/
//npm.pkg.github.com/:@org-a:_authToken=${ORG_A_TOKEN}
//npm.pkg.github.com/:@org-b:_authToken=${ORG_B_TOKEN}
//npm.pkg.github.com/:_authToken=${FALLBACK_TOKEN}
```
`pnpm login --registry=https://npm.pkg.github.com --scope=@org-a` writes the token to the same scope-specific auth key.
When installing or publishing `@org-a/*`, pnpm uses `ORG_A_TOKEN`. For `@org-b/*`, pnpm uses `ORG_B_TOKEN`. Packages without a matching scope continue to use the registry-wide fallback token.

View File

@@ -1,6 +0,0 @@
---
"@pnpm/engine.pm.commands": patch
"pnpm": patch
---
`pnpm setup` no longer prompts to approve build scripts for `@pnpm/exe` when installing the standalone executable. pnpm links the platform-specific binary itself, so the package's install scripts are skipped during the global self-install [#12377](https://github.com/pnpm/pnpm/issues/12377).

View File

@@ -1,7 +0,0 @@
---
"@pnpm/lockfile.fs": patch
"@pnpm/installing.commands": patch
"pnpm": patch
---
Close lockfile reads deterministically before rewriting lockfiles and keep pacquet's virtual store directory length aligned with pnpm on Windows.

View File

@@ -1,6 +0,0 @@
---
"@pnpm/resolving.npm-resolver": patch
"pnpm": patch
---
A `304 Not Modified` answer from the registry now renews the cached metadata file's mtime, so the `minimumReleaseAge` freshness shortcut keeps serving resolutions from the cache. Previously, once a cached packument grew older than `minimumReleaseAge`, every subsequent install re-validated it against the registry forever, because a 304 never rewrites the file.

View File

@@ -1,5 +0,0 @@
---
"@pnpm/deps.inspection.commands": patch
---
Update value shown in the view command output for the `unpackedSize`.

View File

@@ -1,102 +0,0 @@
---
"@pnpm/auth.commands": patch
"@pnpm/bins.linker": patch
"@pnpm/bins.remover": patch
"@pnpm/building.after-install": patch
"@pnpm/building.commands": patch
"@pnpm/building.during-install": patch
"@pnpm/cache.api": patch
"@pnpm/cache.commands": patch
"@pnpm/cli.commands": patch
"@pnpm/cli.default-reporter": patch
"@pnpm/cli.utils": patch
"@pnpm/config.commands": patch
"@pnpm/config.package-is-installable": patch
"@pnpm/config.reader": patch
"@pnpm/config.version-policy": patch
"@pnpm/core-loggers": patch
"@pnpm/deps.compliance.audit": patch
"@pnpm/deps.compliance.commands": patch
"@pnpm/deps.compliance.license-scanner": patch
"@pnpm/deps.compliance.sbom": patch
"@pnpm/deps.graph-builder": patch
"@pnpm/deps.inspection.commands": patch
"@pnpm/deps.inspection.list": patch
"@pnpm/deps.inspection.outdated": patch
"@pnpm/deps.inspection.peers-checker": patch
"@pnpm/deps.inspection.tree-builder": patch
"@pnpm/deps.path": patch
"@pnpm/deps.peer-range": patch
"@pnpm/deps.security.signatures": patch
"@pnpm/deps.status": patch
"@pnpm/engine.pm.commands": patch
"@pnpm/engine.runtime.bun-resolver": patch
"@pnpm/engine.runtime.commands": patch
"@pnpm/engine.runtime.deno-resolver": patch
"@pnpm/engine.runtime.node-resolver": patch
"@pnpm/engine.runtime.system-version": patch
"@pnpm/exec.commands": patch
"@pnpm/exec.lifecycle": patch
"@pnpm/fetching.directory-fetcher": patch
"@pnpm/fetching.git-fetcher": patch
"@pnpm/fetching.tarball-fetcher": patch
"@pnpm/fs.hard-link-dir": patch
"@pnpm/fs.indexed-pkg-importer": patch
"@pnpm/fs.symlink-dependency": patch
"@pnpm/global.commands": patch
"@pnpm/global.packages": patch
"@pnpm/hooks.pnpmfile": patch
"@pnpm/hooks.read-package-hook": patch
"@pnpm/installing.commands": patch
"@pnpm/installing.context": patch
"@pnpm/installing.deps-installer": patch
"@pnpm/installing.deps-resolver": patch
"@pnpm/installing.deps-restorer": patch
"@pnpm/installing.env-installer": patch
"@pnpm/installing.linking.direct-dep-linker": patch
"@pnpm/installing.linking.hoist": patch
"@pnpm/installing.linking.modules-cleaner": patch
"@pnpm/installing.package-requester": patch
"@pnpm/installing.read-projects-context": patch
"@pnpm/lockfile.filtering": patch
"@pnpm/lockfile.fs": patch
"@pnpm/lockfile.merger": patch
"@pnpm/lockfile.to-pnp": patch
"@pnpm/lockfile.verification": patch
"@pnpm/modules-mounter.daemon": patch
"@pnpm/network.auth-header": patch
"@pnpm/network.fetch": patch
"@pnpm/network.web-auth": patch
"@pnpm/object.key-sorting": patch
"@pnpm/patching.apply-patch": patch
"@pnpm/patching.commands": patch
"@pnpm/patching.config": patch
"@pnpm/pkg-manifest.utils": patch
"@pnpm/registry-access.commands": patch
"@pnpm/releasing.commands": patch
"@pnpm/resolving.git-resolver": patch
"@pnpm/resolving.local-resolver": patch
"@pnpm/resolving.npm-resolver": patch
"@pnpm/resolving.registry.pkg-metadata-filter": patch
"@pnpm/store.cafs": patch
"@pnpm/store.commands": patch
"@pnpm/store.connection-manager": patch
"@pnpm/store.controller": patch
"@pnpm/store.create-cafs-store": patch
"@pnpm/store.index": patch
"@pnpm/worker": patch
"@pnpm/workspace.injected-deps-syncer": patch
"@pnpm/workspace.project-manifest-reader": patch
"@pnpm/workspace.projects-reader": patch
"@pnpm/workspace.range-resolver": patch
"@pnpm/workspace.state": patch
"@pnpm/workspace.workspace-manifest-writer": patch
"pnpm": patch
---
Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.

View File

@@ -1,7 +0,0 @@
---
"@pnpm/bins.linker": patch
"@pnpm/exe": patch
"pnpm": patch
---
Updated `@zkochan/cmd-shim` to v9.0.6.

View File

@@ -1,5 +0,0 @@
---
"pnpm": patch
---
Fixed a Windows-only hang where a failed command could take 2046 seconds to exit. On error, pnpm enumerates descendant processes (via `pidtree`) to terminate them, which on Windows shells out to `wmic`/PowerShell `Get-CimInstance Win32_Process` — a lookup that is extremely slow on some machines. The lookup is now bounded by a short timeout so it can no longer stall the process exit.

View File

@@ -1,5 +1,18 @@
# @pnpm-private/updater
## 1100.0.19
### Patch Changes
- Updated dependencies [681b593]
- Updated dependencies [d50d691]
- Updated dependencies [a31faa7]
- @pnpm/types@1101.3.2
- @pnpm/lockfile.fs@1100.1.5
- @pnpm/object.key-sorting@1100.0.1
- @pnpm/workspace.projects-reader@1101.0.12
- @pnpm/workspace.workspace-manifest-reader@1100.0.8
## 1100.0.18
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm-private/updater",
"version": "1100.0.18",
"version": "1100.0.19",
"private": true,
"type": "module",
"scripts": {

View File

@@ -1,5 +1,16 @@
# @pnpm/assert-project
## 1100.0.16
### Patch Changes
- Updated dependencies [681b593]
- @pnpm/types@1101.3.2
- @pnpm/assert-store@1100.0.16
- @pnpm/installing.modules-yaml@1100.0.9
- @pnpm/lockfile.types@1100.0.11
- @pnpm/testing.registry-mock@1100.0.6
## 1100.0.15
### Patch Changes

View File

@@ -1,7 +1,7 @@
{
"name": "@pnpm/assert-project",
"description": "Utils for testing projects that use pnpm",
"version": "1100.0.15",
"version": "1100.0.16",
"author": {
"name": "Zoltan Kochan",
"email": "z@kochan.io",

View File

@@ -1,5 +1,15 @@
# @pnpm/assert-store
## 1100.0.16
### Patch Changes
- Updated dependencies [61810aa]
- Updated dependencies [a31faa7]
- @pnpm/store.index@1100.2.0
- @pnpm/store.cafs@1100.1.10
- @pnpm/testing.registry-mock@1100.0.6
## 1100.0.15
### Patch Changes

View File

@@ -1,7 +1,7 @@
{
"name": "@pnpm/assert-store",
"description": "Utils for testing pnpm store",
"version": "1100.0.15",
"version": "1100.0.16",
"bugs": {
"url": "https://github.com/pnpm/pnpm/issues"
},

View File

@@ -1,5 +1,14 @@
# @pnpm/jest-config
## 1100.0.16
### Patch Changes
- Updated dependencies [61810aa]
- Updated dependencies [a31faa7]
- @pnpm/worker@1100.2.0
- @pnpm/testing.registry-mock@1100.0.6
## 1100.0.15
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/jest-config",
"version": "1100.0.15",
"version": "1100.0.16",
"private": true,
"main": "jest-preset.js",
"type": "module",

View File

@@ -1,5 +1,13 @@
# @pnpm/prepare
## 1100.0.16
### Patch Changes
- Updated dependencies [681b593]
- @pnpm/types@1101.3.2
- @pnpm/assert-project@1100.0.16
## 1100.0.15
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/prepare",
"version": "1100.0.15",
"version": "1100.0.16",
"main": "lib/index.js",
"types": "lib/index.d.ts",
"type": "module",

View File

@@ -1,5 +1,13 @@
# @pnpm/scripts
## 1100.0.15
### Patch Changes
- Updated dependencies [a31faa7]
- @pnpm/workspace.projects-reader@1101.0.12
- @pnpm/workspace.workspace-manifest-reader@1100.0.8
## 1100.0.14
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/scripts",
"version": "1100.0.14",
"version": "1100.0.15",
"private": true,
"type": "module",
"scripts": {

View File

@@ -1,5 +1,45 @@
# @pnpm/auth.commands
## 1100.2.4
### Patch Changes
- 681b593: pnpm can now use different auth tokens for different package scopes, even when those scopes use the same registry URL.
Previously, auth was selected only by registry URL. If `@org-a` and `@org-b` both used `https://npm.pkg.github.com/`, they had to share the same token. This caused problems for registries that issue tokens per organization or per scope.
Configure a scope-specific token by adding the package scope after the registry URL in the auth key:
```ini
@org-a:registry=https://npm.pkg.github.com/
@org-b:registry=https://npm.pkg.github.com/
//npm.pkg.github.com/:@org-a:_authToken=${ORG_A_TOKEN}
//npm.pkg.github.com/:@org-b:_authToken=${ORG_B_TOKEN}
//npm.pkg.github.com/:_authToken=${FALLBACK_TOKEN}
```
`pnpm login --registry=https://npm.pkg.github.com --scope=@org-a` writes the token to the same scope-specific auth key.
When installing or publishing `@org-a/*`, pnpm uses `ORG_A_TOKEN`. For `@org-b/*`, pnpm uses `ORG_B_TOKEN`. Packages without a matching scope continue to use the registry-wide fallback token.
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [61810aa]
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/config.reader@1101.9.0
- @pnpm/cli.utils@1101.0.12
- @pnpm/network.fetch@1100.1.3
- @pnpm/network.web-auth@1101.1.1
- @pnpm/registry-access.client@1100.1.4
## 1100.2.3
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/auth.commands",
"version": "1100.2.3",
"version": "1100.2.4",
"description": "Commands for authentication with npm registries",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,26 @@
# @pnpm/link-bins
## 1100.0.14
### Patch Changes
- 61810aa: Added a new setting `frozenStore` (`--frozen-store`) that lets `pnpm install` run against a package store on a read-only filesystem (e.g. a Nix store, a read-only bind mount, an OCI layer). When enabled, pnpm opens the store's SQLite `index.db` through the `immutable=1` URI — bypassing the WAL/`-shm` sidecar creation that otherwise fails on a read-only directory — and suppresses every store-write path (the `index.db` writer and the project-registry write). Pair it with `--offline --frozen-lockfile` against a fully-populated store. Under the global virtual store, package directories live inside the store, so if the store is missing the build output of a package whose lifecycle scripts are approved (or that has a patch), pnpm fails up front with `ERR_PNPM_FROZEN_STORE_NEEDS_BUILD` rather than crashing mid-build on a read-only write — seed the store with those builds first. Incompatible with `--force` and with a configured pnpr server, since both write into the store; the side-effects cache is likewise not written under `frozenStore`. If the store is missing its content directory, the install fails fast with `ERR_PNPM_FROZEN_STORE_INCOMPLETE` rather than attempting to initialize it. The read-only `immutable=1` open requires Node.js >=22.15.0, >=23.11.0, or >=24.0.0; on older runtimes `--frozen-store` fails with a clear `ERR_PNPM_FROZEN_STORE_UNSUPPORTED_NODE` error. Bin-linking also tolerates a read-only store: under the global virtual store a package's bin source lives inside the store, so the `chmod` that makes it executable would be refused — with `EPERM`/`EACCES`, or with `EROFS` on a genuinely read-only filesystem. That `chmod` is redundant when the seed already ships its bins executable with a normalized shebang, so it is now skipped in that case, while a non-executable bin (or one still carrying a Windows CRLF shebang) on a read-only store still errors.
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- cd8348c: Updated `@zkochan/cmd-shim` to v9.0.6.
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/types@1101.3.2
- @pnpm/pkg-manifest.utils@1100.2.5
- @pnpm/workspace.project-manifest-reader@1100.0.13
- @pnpm/bins.resolver@1100.0.8
- @pnpm/pkg-manifest.reader@1100.0.8
## 1100.0.13
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/bins.linker",
"version": "1100.0.13",
"version": "1100.0.14",
"description": "Link bins to node_modules/.bin",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,23 @@
# @pnpm/remove-bins
## 1100.0.10
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/types@1101.3.2
- @pnpm/core-loggers@1100.2.1
- @pnpm/bins.resolver@1100.0.8
- @pnpm/pkg-manifest.reader@1100.0.8
## 1100.0.9
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/bins.remover",
"version": "1100.0.9",
"version": "1100.0.10",
"description": "Remove bins from .bin",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,12 @@
# @pnpm/package-bins
## 1100.0.8
### Patch Changes
- Updated dependencies [681b593]
- @pnpm/types@1101.3.2
## 1100.0.7
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/bins.resolver",
"version": "1100.0.7",
"version": "1100.0.8",
"description": "Returns bins of a package",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,45 @@
# @pnpm/building.after-install
## 1102.0.0
### Patch Changes
- 61810aa: Added a new setting `frozenStore` (`--frozen-store`) that lets `pnpm install` run against a package store on a read-only filesystem (e.g. a Nix store, a read-only bind mount, an OCI layer). When enabled, pnpm opens the store's SQLite `index.db` through the `immutable=1` URI — bypassing the WAL/`-shm` sidecar creation that otherwise fails on a read-only directory — and suppresses every store-write path (the `index.db` writer and the project-registry write). Pair it with `--offline --frozen-lockfile` against a fully-populated store. Under the global virtual store, package directories live inside the store, so if the store is missing the build output of a package whose lifecycle scripts are approved (or that has a patch), pnpm fails up front with `ERR_PNPM_FROZEN_STORE_NEEDS_BUILD` rather than crashing mid-build on a read-only write — seed the store with those builds first. Incompatible with `--force` and with a configured pnpr server, since both write into the store; the side-effects cache is likewise not written under `frozenStore`. If the store is missing its content directory, the install fails fast with `ERR_PNPM_FROZEN_STORE_INCOMPLETE` rather than attempting to initialize it. The read-only `immutable=1` open requires Node.js >=22.15.0, >=23.11.0, or >=24.0.0; on older runtimes `--frozen-store` fails with a clear `ERR_PNPM_FROZEN_STORE_UNSUPPORTED_NODE` error. Bin-linking also tolerates a read-only store: under the global virtual store a package's bin source lives inside the store, so the `chmod` that makes it executable would be refused — with `EPERM`/`EACCES`, or with `EROFS` on a genuinely read-only filesystem. That `chmod` is redundant when the seed already ships its bins executable with a normalized shebang, so it is now skipped in that case, while a non-executable bin (or one still carrying a Windows CRLF shebang) on a read-only store still errors.
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [61810aa]
- Updated dependencies [f20ad8f]
- Updated dependencies [23716ed]
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- Updated dependencies [cd8348c]
- @pnpm/config.reader@1101.9.0
- @pnpm/store.index@1100.2.0
- @pnpm/store.connection-manager@1100.3.0
- @pnpm/bins.linker@1100.0.14
- @pnpm/worker@1100.2.0
- @pnpm/installing.context@1100.0.18
- @pnpm/lockfile.utils@1100.0.13
- @pnpm/exec.lifecycle@1100.0.18
- @pnpm/types@1101.3.2
- @pnpm/core-loggers@1100.2.1
- @pnpm/deps.path@1100.0.8
- @pnpm/store.cafs@1100.1.10
- @pnpm/deps.graph-hasher@1100.2.5
- @pnpm/building.pkg-requires-build@1100.0.8
- @pnpm/building.policy@1100.0.10
- @pnpm/config.normalize-registries@1100.0.8
- @pnpm/installing.modules-yaml@1100.0.9
- @pnpm/lockfile.types@1100.0.11
- @pnpm/lockfile.walker@1100.0.11
- @pnpm/pkg-manifest.reader@1100.0.8
- @pnpm/store.controller-types@1100.1.5
## 1101.0.21
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/building.after-install",
"version": "1101.0.21",
"version": "1102.0.0",
"description": "Rebuild packages that are already installed by running their lifecycle scripts",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,36 @@
# @pnpm/building.commands
## 1100.1.5
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [8dcd9a0]
- Updated dependencies [86e70d2]
- Updated dependencies [61810aa]
- Updated dependencies [ab0b7d1]
- Updated dependencies [74a2dc9]
- Updated dependencies [681b593]
- Updated dependencies [d50d691]
- Updated dependencies [a31faa7]
- @pnpm/installing.commands@1100.9.0
- @pnpm/config.reader@1101.9.0
- @pnpm/store.connection-manager@1100.3.0
- @pnpm/building.after-install@1102.0.0
- @pnpm/types@1101.3.2
- @pnpm/cli.utils@1101.0.12
- @pnpm/deps.path@1100.0.8
- @pnpm/building.policy@1100.0.10
- @pnpm/config.writer@1100.0.13
- @pnpm/installing.modules-yaml@1100.0.9
- @pnpm/workspace.projects-sorter@1100.0.7
## 1100.1.4
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/building.commands",
"version": "1100.1.4",
"version": "1100.1.5",
"description": "Commands for rebuilding and managing dependency builds",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,35 @@
# @pnpm/building.during-install
## 1102.0.0
### Patch Changes
- 61810aa: Added a new setting `frozenStore` (`--frozen-store`) that lets `pnpm install` run against a package store on a read-only filesystem (e.g. a Nix store, a read-only bind mount, an OCI layer). When enabled, pnpm opens the store's SQLite `index.db` through the `immutable=1` URI — bypassing the WAL/`-shm` sidecar creation that otherwise fails on a read-only directory — and suppresses every store-write path (the `index.db` writer and the project-registry write). Pair it with `--offline --frozen-lockfile` against a fully-populated store. Under the global virtual store, package directories live inside the store, so if the store is missing the build output of a package whose lifecycle scripts are approved (or that has a patch), pnpm fails up front with `ERR_PNPM_FROZEN_STORE_NEEDS_BUILD` rather than crashing mid-build on a read-only write — seed the store with those builds first. Incompatible with `--force` and with a configured pnpr server, since both write into the store; the side-effects cache is likewise not written under `frozenStore`. If the store is missing its content directory, the install fails fast with `ERR_PNPM_FROZEN_STORE_INCOMPLETE` rather than attempting to initialize it. The read-only `immutable=1` open requires Node.js >=22.15.0, >=23.11.0, or >=24.0.0; on older runtimes `--frozen-store` fails with a clear `ERR_PNPM_FROZEN_STORE_UNSUPPORTED_NODE` error. Bin-linking also tolerates a read-only store: under the global virtual store a package's bin source lives inside the store, so the `chmod` that makes it executable would be refused — with `EPERM`/`EACCES`, or with `EROFS` on a genuinely read-only filesystem. That `chmod` is redundant when the seed already ships its bins executable with a normalized shebang, so it is now skipped in that case, while a non-executable bin (or one still carrying a Windows CRLF shebang) on a read-only store still errors.
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [61810aa]
- Updated dependencies [23716ed]
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- Updated dependencies [cd8348c]
- @pnpm/config.reader@1101.9.0
- @pnpm/bins.linker@1100.0.14
- @pnpm/worker@1100.2.0
- @pnpm/exec.lifecycle@1100.0.18
- @pnpm/types@1101.3.2
- @pnpm/core-loggers@1100.2.1
- @pnpm/deps.path@1100.0.8
- @pnpm/fs.hard-link-dir@1100.0.2
- @pnpm/patching.apply-patch@1100.0.2
- @pnpm/deps.graph-hasher@1100.2.5
- @pnpm/pkg-manifest.reader@1100.0.8
- @pnpm/store.controller-types@1100.1.5
## 1101.0.18
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/building.during-install",
"version": "1101.0.18",
"version": "1102.0.0",
"description": "Build packages in node_modules",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,12 @@
# @pnpm/building.pkg-requires-build
## 1100.0.8
### Patch Changes
- Updated dependencies [681b593]
- @pnpm/types@1101.3.2
## 1100.0.7
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/building.pkg-requires-build",
"version": "1100.0.7",
"version": "1100.0.8",
"description": "Checks if a package requires to be built",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,15 @@
# @pnpm/building.policy
## 1100.0.10
### Patch Changes
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/types@1101.3.2
- @pnpm/config.version-policy@1100.1.5
- @pnpm/deps.path@1100.0.8
## 1100.0.9
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/building.policy",
"version": "1100.0.9",
"version": "1100.0.10",
"description": "Create a function for filtering out dependencies that are not allowed to be built",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,25 @@
# @pnpm/cache.api
## 1100.0.22
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [61810aa]
- Updated dependencies [681b593]
- Updated dependencies [1310ab5]
- Updated dependencies [a31faa7]
- @pnpm/config.reader@1101.9.0
- @pnpm/store.index@1100.2.0
- @pnpm/resolving.npm-resolver@1102.0.0
- @pnpm/store.cafs@1100.1.10
## 1100.0.21
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/cache.api",
"version": "1100.0.21",
"version": "1100.0.22",
"description": "API for controlling the cache",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,23 @@
# @pnpm/cache.commands
## 1100.0.23
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [61810aa]
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/config.reader@1101.9.0
- @pnpm/cache.api@1100.0.22
- @pnpm/cli.utils@1101.0.12
## 1100.0.22
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/cache.commands",
"version": "1100.0.22",
"version": "1100.0.23",
"description": "Commands for controlling the cache",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,24 @@
# @pnpm/cli.commands
## 1100.0.21
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [61810aa]
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/config.reader@1101.9.0
- @pnpm/cli.utils@1101.0.12
- @pnpm/workspace.projects-reader@1101.0.12
- @pnpm/workspace.workspace-manifest-reader@1100.0.8
## 1100.0.20
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/cli.commands",
"version": "1100.0.20",
"version": "1100.0.21",
"description": "Commands for pnpm CLI",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,25 @@
# @pnpm/default-reporter
## 1100.3.1
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [61810aa]
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/config.reader@1101.9.0
- @pnpm/types@1101.3.2
- @pnpm/core-loggers@1100.2.1
- @pnpm/cli.meta@1100.0.8
- @pnpm/deps.inspection.peers-issues-renderer@1100.0.6
## 1100.3.0
### Minor Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/cli.default-reporter",
"version": "1100.3.0",
"version": "1100.3.1",
"description": "The default reporter of pnpm",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,12 @@
# @pnpm/cli-meta
## 1100.0.8
### Patch Changes
- Updated dependencies [681b593]
- @pnpm/types@1101.3.2
## 1100.0.7
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/cli.meta",
"version": "1100.0.7",
"version": "1100.0.8",
"description": "Reads the metainfo of the currently running pnpm instance",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,24 @@
# @pnpm/cli-utils
## 1101.0.12
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/types@1101.3.2
- @pnpm/config.package-is-installable@1100.0.11
- @pnpm/pkg-manifest.utils@1100.2.5
- @pnpm/workspace.project-manifest-reader@1100.0.13
- @pnpm/cli.meta@1100.0.8
## 1101.0.11
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/cli.utils",
"version": "1101.0.11",
"version": "1101.0.12",
"description": "Utils for pnpm commands",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,24 @@
# @pnpm/plugin-commands-config
## 1100.0.22
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [61810aa]
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/config.reader@1101.9.0
- @pnpm/cli.utils@1101.0.12
- @pnpm/object.key-sorting@1100.0.1
- @pnpm/workspace.workspace-manifest-writer@1100.0.13
## 1100.0.21
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/config.commands",
"version": "1100.0.21",
"version": "1100.0.22",
"description": "Commands for reading and writing settings to/from config files",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,12 @@
# @pnpm/normalize-registries
## 1100.0.8
### Patch Changes
- Updated dependencies [681b593]
- @pnpm/types@1101.3.2
## 1100.0.7
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/config.normalize-registries",
"version": "1100.0.7",
"version": "1100.0.8",
"description": "Accepts a mapping of registry URLs and returns a mapping with the same URLs but normalized",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,23 @@
# @pnpm/package-is-installable
## 1100.0.11
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/types@1101.3.2
- @pnpm/core-loggers@1100.2.1
- @pnpm/engine.runtime.system-version@1100.0.3
- @pnpm/cli.meta@1100.0.8
## 1100.0.10
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/config.package-is-installable",
"version": "1100.0.10",
"version": "1100.0.11",
"description": "Checks if a package is installable on the current system",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,12 @@
# @pnpm/pick-registry-for-package
## 1100.0.9
### Patch Changes
- Updated dependencies [681b593]
- @pnpm/types@1101.3.2
## 1100.0.8
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/config.pick-registry-for-package",
"version": "1100.0.8",
"version": "1100.0.9",
"description": "Picks the right registry for the package from a registries config",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,49 @@
# @pnpm/config
## 1101.9.0
### Minor Changes
- 61810aa: Added a new setting `frozenStore` (`--frozen-store`) that lets `pnpm install` run against a package store on a read-only filesystem (e.g. a Nix store, a read-only bind mount, an OCI layer). When enabled, pnpm opens the store's SQLite `index.db` through the `immutable=1` URI — bypassing the WAL/`-shm` sidecar creation that otherwise fails on a read-only directory — and suppresses every store-write path (the `index.db` writer and the project-registry write). Pair it with `--offline --frozen-lockfile` against a fully-populated store. Under the global virtual store, package directories live inside the store, so if the store is missing the build output of a package whose lifecycle scripts are approved (or that has a patch), pnpm fails up front with `ERR_PNPM_FROZEN_STORE_NEEDS_BUILD` rather than crashing mid-build on a read-only write — seed the store with those builds first. Incompatible with `--force` and with a configured pnpr server, since both write into the store; the side-effects cache is likewise not written under `frozenStore`. If the store is missing its content directory, the install fails fast with `ERR_PNPM_FROZEN_STORE_INCOMPLETE` rather than attempting to initialize it. The read-only `immutable=1` open requires Node.js >=22.15.0, >=23.11.0, or >=24.0.0; on older runtimes `--frozen-store` fails with a clear `ERR_PNPM_FROZEN_STORE_UNSUPPORTED_NODE` error. Bin-linking also tolerates a read-only store: under the global virtual store a package's bin source lives inside the store, so the `chmod` that makes it executable would be refused — with `EPERM`/`EACCES`, or with `EROFS` on a genuinely read-only filesystem. That `chmod` is redundant when the seed already ships its bins executable with a normalized shebang, so it is now skipped in that case, while a non-executable bin (or one still carrying a Windows CRLF shebang) on a read-only store still errors.
### Patch Changes
- 681b593: pnpm can now use different auth tokens for different package scopes, even when those scopes use the same registry URL.
Previously, auth was selected only by registry URL. If `@org-a` and `@org-b` both used `https://npm.pkg.github.com/`, they had to share the same token. This caused problems for registries that issue tokens per organization or per scope.
Configure a scope-specific token by adding the package scope after the registry URL in the auth key:
```ini
@org-a:registry=https://npm.pkg.github.com/
@org-b:registry=https://npm.pkg.github.com/
//npm.pkg.github.com/:@org-a:_authToken=${ORG_A_TOKEN}
//npm.pkg.github.com/:@org-b:_authToken=${ORG_B_TOKEN}
//npm.pkg.github.com/:_authToken=${FALLBACK_TOKEN}
```
`pnpm login --registry=https://npm.pkg.github.com --scope=@org-a` writes the token to the same scope-specific auth key.
When installing or publishing `@org-a/*`, pnpm uses `ORG_A_TOKEN`. For `@org-b/*`, pnpm uses `ORG_B_TOKEN`. Packages without a matching scope continue to use the registry-wide fallback token.
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/types@1101.3.2
- @pnpm/hooks.pnpmfile@1100.0.15
- @pnpm/pkg-manifest.utils@1100.2.5
- @pnpm/workspace.project-manifest-reader@1100.0.13
- @pnpm/workspace.workspace-manifest-reader@1100.0.8
- @pnpm/catalogs.config@1100.0.0
## 1101.8.0
### Minor Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/config.reader",
"version": "1101.8.0",
"version": "1101.9.0",
"description": "Gets configuration options for pnpm",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,19 @@
# @pnpm/config.version-policy
## 1100.1.5
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [681b593]
- @pnpm/types@1101.3.2
## 1100.1.4
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/config.version-policy",
"version": "1100.1.4",
"version": "1100.1.5",
"description": "Parses and evaluates package version policy specs and produces package-version matchers",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,14 @@
# @pnpm/config.config-writer
## 1100.0.13
### Patch Changes
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/types@1101.3.2
- @pnpm/workspace.workspace-manifest-writer@1100.0.13
## 1100.0.12
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/config.writer",
"version": "1100.0.12",
"version": "1100.0.13",
"description": "Functions for updating the configuration settings",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,19 @@
# @pnpm/core-loggers
## 1100.2.1
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [681b593]
- @pnpm/types@1101.3.2
## 1100.2.0
### Minor Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/core-loggers",
"version": "1100.2.0",
"version": "1100.2.1",
"description": "Core loggers of pnpm",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,29 @@
# @pnpm/types
## 1101.3.2
### Patch Changes
- 681b593: pnpm can now use different auth tokens for different package scopes, even when those scopes use the same registry URL.
Previously, auth was selected only by registry URL. If `@org-a` and `@org-b` both used `https://npm.pkg.github.com/`, they had to share the same token. This caused problems for registries that issue tokens per organization or per scope.
Configure a scope-specific token by adding the package scope after the registry URL in the auth key:
```ini
@org-a:registry=https://npm.pkg.github.com/
@org-b:registry=https://npm.pkg.github.com/
//npm.pkg.github.com/:@org-a:_authToken=${ORG_A_TOKEN}
//npm.pkg.github.com/:@org-b:_authToken=${ORG_B_TOKEN}
//npm.pkg.github.com/:_authToken=${FALLBACK_TOKEN}
```
`pnpm login --registry=https://npm.pkg.github.com --scope=@org-a` writes the token to the same scope-specific auth key.
When installing or publishing `@org-a/*`, pnpm uses `ORG_A_TOKEN`. For `@org-b/*`, pnpm uses `ORG_B_TOKEN`. Packages without a matching scope continue to use the registry-wide fallback token.
## 1101.3.1
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/types",
"version": "1101.3.1",
"version": "1101.3.2",
"description": "Basic types used by pnpm",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,13 @@
# @pnpm/crypto.shasums-file
## 1100.1.1
### Patch Changes
- Updated dependencies [681b593]
- @pnpm/fetching.types@1100.0.2
- @pnpm/crypto.hash@1100.0.1
## 1100.1.0
### Minor Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/crypto.shasums-file",
"version": "1100.1.0",
"version": "1100.1.1",
"description": "Utils for working with shasums files",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,30 @@
# @pnpm/audit
## 1101.0.16
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [f20ad8f]
- Updated dependencies [681b593]
- Updated dependencies [d50d691]
- Updated dependencies [a31faa7]
- @pnpm/lockfile.utils@1100.0.13
- @pnpm/fetching.types@1100.0.2
- @pnpm/types@1101.3.2
- @pnpm/lockfile.fs@1100.1.5
- @pnpm/deps.path@1100.0.8
- @pnpm/network.fetch@1100.1.3
- @pnpm/lockfile.detect-dep-types@1100.0.11
- @pnpm/lockfile.types@1100.0.11
- @pnpm/lockfile.walker@1100.0.11
## 1101.0.15
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/deps.compliance.audit",
"version": "1101.0.15",
"version": "1101.0.16",
"description": "Audit a lockfile",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,45 @@
# @pnpm/deps.compliance.commands
## 1101.3.5
### Patch Changes
- 8dcd9a0: Fix garbled summary line after submitting `pnpm update -i` and `pnpm audit --fix -i`. The interactive checkbox prompt previously printed every selected choice's full table row (label, current/target versions, workspace, URL) joined by commas, producing a wall of text after pressing Enter. The summary now lists only the selected package names (or vulnerability keys) by setting an explicit `short` per choice; the in-progress selection UI is unchanged.
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [8dcd9a0]
- Updated dependencies [86e70d2]
- Updated dependencies [61810aa]
- Updated dependencies [f20ad8f]
- Updated dependencies [ab0b7d1]
- Updated dependencies [74a2dc9]
- Updated dependencies [681b593]
- Updated dependencies [d50d691]
- Updated dependencies [a31faa7]
- @pnpm/installing.commands@1100.9.0
- @pnpm/config.reader@1101.9.0
- @pnpm/lockfile.utils@1100.0.13
- @pnpm/network.auth-header@1101.1.2
- @pnpm/types@1101.3.2
- @pnpm/lockfile.fs@1100.1.5
- @pnpm/cli.utils@1101.0.12
- @pnpm/deps.compliance.audit@1101.0.16
- @pnpm/deps.compliance.license-scanner@1100.0.19
- @pnpm/deps.compliance.sbom@1100.1.9
- @pnpm/deps.security.signatures@1101.2.2
- @pnpm/object.key-sorting@1100.0.1
- @pnpm/workspace.project-manifest-reader@1100.0.13
- @pnpm/cli.meta@1100.0.8
- @pnpm/config.pick-registry-for-package@1100.0.9
- @pnpm/config.writer@1100.0.13
- @pnpm/lockfile.types@1100.0.11
- @pnpm/lockfile.walker@1100.0.11
## 1101.3.4
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/deps.compliance.commands",
"version": "1101.3.4",
"version": "1101.3.5",
"description": "pnpm commands for audit, licenses, and sbom",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,33 @@
# @pnpm/license-scanner
## 1100.0.19
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [61810aa]
- Updated dependencies [f20ad8f]
- Updated dependencies [681b593]
- Updated dependencies [d50d691]
- Updated dependencies [a31faa7]
- @pnpm/store.index@1100.2.0
- @pnpm/lockfile.utils@1100.0.13
- @pnpm/types@1101.3.2
- @pnpm/lockfile.fs@1100.1.5
- @pnpm/config.package-is-installable@1100.0.11
- @pnpm/deps.path@1100.0.8
- @pnpm/store.pkg-finder@1100.0.17
- @pnpm/lockfile.detect-dep-types@1100.0.11
- @pnpm/lockfile.types@1100.0.11
- @pnpm/lockfile.walker@1100.0.11
- @pnpm/pkg-manifest.reader@1100.0.8
## 1100.0.18
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/deps.compliance.license-scanner",
"version": "1100.0.18",
"version": "1100.0.19",
"description": "Check for licenses packages",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,30 @@
# @pnpm/deps.compliance.sbom
## 1100.1.9
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [61810aa]
- Updated dependencies [f20ad8f]
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/store.index@1100.2.0
- @pnpm/lockfile.utils@1100.0.13
- @pnpm/types@1101.3.2
- @pnpm/store.pkg-finder@1100.0.17
- @pnpm/lockfile.detect-dep-types@1100.0.11
- @pnpm/lockfile.types@1100.0.11
- @pnpm/lockfile.walker@1100.0.11
- @pnpm/pkg-manifest.reader@1100.0.8
- @pnpm/resolving.resolver-base@1100.4.2
## 1100.1.8
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/deps.compliance.sbom",
"version": "1100.1.8",
"version": "1100.1.9",
"description": "Generate SBOM from pnpm lockfile",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,32 @@
# @pnpm/deps.graph-builder
## 1100.0.16
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [f20ad8f]
- Updated dependencies [681b593]
- Updated dependencies [d50d691]
- Updated dependencies [a31faa7]
- @pnpm/lockfile.utils@1100.0.13
- @pnpm/types@1101.3.2
- @pnpm/lockfile.fs@1100.1.5
- @pnpm/config.package-is-installable@1100.0.11
- @pnpm/core-loggers@1100.2.1
- @pnpm/deps.path@1100.0.8
- @pnpm/patching.config@1100.0.8
- @pnpm/deps.graph-hasher@1100.2.5
- @pnpm/hooks.types@1100.0.12
- @pnpm/installing.modules-yaml@1100.0.9
- @pnpm/store.controller-types@1100.1.5
## 1100.0.15
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/deps.graph-builder",
"version": "1100.0.15",
"version": "1100.0.16",
"description": "A package for building a dependency graph from a lockfile",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,19 @@
# @pnpm/calc-dep-state
## 1100.2.5
### Patch Changes
- Updated dependencies [f20ad8f]
- Updated dependencies [681b593]
- Updated dependencies [a31faa7]
- @pnpm/lockfile.utils@1100.0.13
- @pnpm/types@1101.3.2
- @pnpm/deps.path@1100.0.8
- @pnpm/engine.runtime.system-version@1100.0.3
- @pnpm/lockfile.types@1100.0.11
- @pnpm/resolving.resolver-base@1100.4.2
## 1100.2.4
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/deps.graph-hasher",
"version": "1100.2.4",
"version": "1100.2.5",
"description": "Calculates the state of a dependency",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,40 @@
# @pnpm/deps.inspection.commands
## 1100.3.7
### Patch Changes
- da248c3: Update value shown in the view command output for the `unpackedSize`.
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [61810aa]
- Updated dependencies [681b593]
- Updated dependencies [d50d691]
- Updated dependencies [1310ab5]
- Updated dependencies [a31faa7]
- @pnpm/config.reader@1101.9.0
- @pnpm/resolving.npm-resolver@1102.0.0
- @pnpm/network.auth-header@1101.1.2
- @pnpm/resolving.default-resolver@1100.3.8
- @pnpm/types@1101.3.2
- @pnpm/lockfile.fs@1100.1.5
- @pnpm/cli.utils@1101.0.12
- @pnpm/deps.inspection.list@1100.0.18
- @pnpm/deps.inspection.outdated@1100.1.8
- @pnpm/deps.inspection.peers-checker@1100.0.14
- @pnpm/global.commands@1100.0.28
- @pnpm/global.packages@1100.0.8
- @pnpm/network.fetch@1100.1.3
- @pnpm/config.pick-registry-for-package@1100.0.9
- @pnpm/deps.inspection.peers-issues-renderer@1100.0.6
- @pnpm/installing.modules-yaml@1100.0.9
- @pnpm/resolving.registry.types@1100.1.3
## 1100.3.6
### Patch Changes

View File

@@ -1,6 +1,6 @@
{
"name": "@pnpm/deps.inspection.commands",
"version": "1100.3.6",
"version": "1100.3.7",
"description": "The list, ll, why, and outdated commands of pnpm",
"keywords": [
"pnpm",

View File

@@ -1,5 +1,25 @@
# @pnpm/list
## 1100.0.18
### Patch Changes
- a31faa7: Updated dependency ranges. Notably:
- `@pnpm/logger` peer dependency range moved to `^1100.0.0`.
- `msgpackr` 1.11.8 → 2.0.4 (store index files remain byte-compatible in both directions).
- `open` ^7.4.2 → ^11.0.0, `memoize` ^10 → ^11, `cli-truncate` ^5 → ^6, `pidtree` ^0.6 → ^1.
- `@yarnpkg/core` 4.5.0 → 4.8.0, `@rushstack/worker-pool` 0.7.7 → 0.7.18, `@cyclonedx/cyclonedx-library` 10.0.0 → 10.1.0, `@pnpm/config.nerf-dart` ^1 → ^2, `@pnpm/log.group` 3.0.2 → 4.0.1, `@pnpm/util.lex-comparator` ^3 → ^4.
- Updated dependencies [681b593]
- Updated dependencies [d50d691]
- Updated dependencies [a31faa7]
- @pnpm/types@1101.3.2
- @pnpm/lockfile.fs@1100.1.5
- @pnpm/deps.inspection.tree-builder@1100.0.15
- @pnpm/workspace.project-manifest-reader@1100.0.13
- @pnpm/pkg-manifest.reader@1100.0.8
## 1100.0.17
### Patch Changes

Some files were not shown because too many files have changed in this diff Show More