# pnpm pnpr@0.1.0-alpha.9 — pnpr 0.1.0-alpha.9

- Product: pnpm (https://whatsnew.fyi/product/pnpm)
- Vendor: pnpm
- Date: 2026-08-29
- Version: pnpr@0.1.0-alpha.9
- Original notes: https://github.com/pnpm/pnpm/releases/tag/pnpr%400.1.0-alpha.9
- Permalink: https://whatsnew.fyi/product/pnpm/releases/pnpr-0.1.0-alpha.9
- Labels: Pre-release

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **added** — Made the signed shared-artifact cache horizontally scalable with S3-compatible storage and an independent top-level artifacts feature toggle
- **changed** — Generalized the experimental shared-artifact protocol so candidates and signed payloads identify a discriminated subject, with dependency side effects using package and source-integrity subjects, and workspace tasks using project and task subjects
- **changed** — Published build artifacts are now immutable: one input key and one set of compatibility constraints admit one artifact, with republishing a different one answering 409 Conflict
- **changed** — Published build artifacts are now immutable for every consumer they can reach, not only for the exact compatibility constraints they declare
- **fixed** — pnpr reclaims unreferenced shared artifact blobs after ambiguous object-storage write failures once active publications drain
- **fixed** — Recognize pnpm install --fix-lockfile, including filtered installs, and regenerate broken lockfile metadata while preserving compatible locked versions
- **fixed** — pnpr retains shared artifact quota after object storage reports an ambiguous write failure

##### Minor Changes

- Made the signed shared-artifact cache horizontally scalable with S3-compatible storage and an independent top-level `artifacts` feature toggle.

- Generalized the experimental shared-artifact protocol so candidates and signed payloads identify a discriminated subject. Dependency side effects use package and source-integrity subjects, while workspace tasks use project and task subjects.

  This changes shared-artifact request bodies and signed payloads. A pnpr server and its clients have to be on matching versions.

##### Patch Changes

- A published build artifact is now immutable: one input key and one set of compatibility constraints admit one artifact, so publishing a different one over it answers `409 Conflict`, the same as a re-published `name@version`. Republishing the identical artifact still succeeds. Artifacts already stored by an earlier version keep their slot, so upgrading a populated registry does not leave them replaceable.

- A published build artifact is now immutable for every consumer it can reach, not only for the exact compatibility constraints it declares. Publishing an artifact that reaches a machine an existing one already reaches answers `409 Conflict`, so a later universal, broader, or higher-floor build can no longer take precedence over the artifact a consumer already receives. Publishing across a platform matrix is unaffected: artifacts for different operating systems, architectures, or Node majors reach no machine in common and coexist as before.

- pnpr reclaims unreferenced shared artifact blobs after ambiguous object-storage write failures once active publications drain.

- Recognize `pnpm install --fix-lockfile`, including filtered installs, and regenerate broken lockfile metadata while preserving compatible locked versions [pnpm/pnpm#14250](https://github.com/pnpm/pnpm/issues/14250).

- pnpr retains shared artifact quota after object storage reports an ambiguous write failure.