mirror/pnpm
1
0
Fork 0
mirror of https://github.com/pnpm/pnpm.git synced 2026-06-28 09:55:39 -04:00
Code Issues Packages Projects Releases Wiki Activity
Files
8928aed6a9a0e0271dc541d8140fbcbaaaf65521
pnpm/pnpm11/patching/apply-patch/CHANGELOG.md
Zoltan Kochan fc2f33912e refactor: move the TypeScript pnpm CLI into a pnpm11/ directory (#12537) 
The TypeScript pnpm CLI freezes at v11; pnpm 12 will be the Rust pacquet
port. To make that split legible, all TypeScript source, test, and build
directories move under a new top-level pnpm11/ directory. The name states
the version boundary rather than implying a behavioral fork, since the two
stacks are meant to behave identically.

Scope is source-only: the shared workspace root stays at the repo root.
pnpm-workspace.yaml, package.json, pnpm-lock.yaml, .pnpmfile.cjs,
.meta-updater, __patches__, .changeset, .husky, and the lint/spell configs
remain in place, so one pnpm workspace and one Cargo workspace still span
all three products. pnpr/client and pacquet/tasks/registry-mock stay as
cross-product workspace members.

Rewiring the move required:
- pnpm-workspace.yaml globs prefixed with pnpm11/
- root package.json script paths, eslint.config.mjs, tsconfig.lint.json,
  .gitignore, and CODEOWNERS updated
- .meta-updater/src/index.ts literals repointed (pnpm11/pnpm/package.json,
  pnpm11/__utils__, pnpm11/__typings__, and the main package directory)
- regenerated every moved package's repository/homepage URL via meta-updater
- pnpm11/pnpm/bundle-deps.ts and __utils__/scripts/src/typecheck-only.ts
  climb one more level to reach the repo root

.meta-updater stays at the repo root because @pnpm/meta-updater resolves
its config at <cwd>/.meta-updater/main.mjs.

TS CI (.github/workflows/ci.yml) now only runs when pnpm11/-relevant paths
change, via a dorny/paths-filter changes job plus a TS CI / Success
aggregate gate; branch protection should require only that gate.
2026-06-20 14:36:25 +02:00

4.3 KiB
Raw Blame History

@pnpm/patching.apply-patch

1100.0.2

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.

1100.0.1

Patch Changes

  • 26a7d63: Reject patch files whose diff --git headers reference paths outside the patched package directory. Previously a malicious .patch file added via a pull request could write, delete, or rename arbitrary files reachable by the user running pnpm install.

1001.0.0

Major Changes

  • 491a84f: This package is now pure ESM.
  • 7d2fd48: Node.js v18, 19, 20, and 21 support discontinued.
  • 7b1c189: Removed the deprecated allowNonAppliedPatches completely in favor of allowUnusedPatches. Remove ignorePatchFailures so all patch application failures should throw an error.

Patch Changes

  • a0e3a21: Import @pnpm/patch-package/dist/applyPatches using .js extension for ESM compatibility. This fixes an ERR_MODULE_NOT_FOUND error.
  • Updated dependencies [491a84f]
  • Updated dependencies [7d2fd48]
  • Updated dependencies [831f574]
    • @pnpm/error@1001.0.0

1000.0.7

Patch Changes

  • @pnpm/error@1000.0.5

1000.0.6

Patch Changes

  • @pnpm/error@1000.0.4

1000.0.5

Patch Changes

  • @pnpm/error@1000.0.3

1000.0.4

Patch Changes

  • 09cf46f: Update @pnpm/logger in peer dependencies.

1000.0.3

Patch Changes

  • 453a18a: Update @pnpm/patch-package to v0.0.1.

1000.0.2

Patch Changes

  • @pnpm/error@1000.0.2

1000.0.1

Patch Changes

  • @pnpm/error@1000.0.1

3.1.2

Patch Changes

  • @pnpm/error@6.0.3

3.1.1

Patch Changes

  • @pnpm/error@6.0.2

3.1.0

Minor Changes

  • cb006df: Add ability to apply patch to all versions: If the key of pnpm.patchedDependencies is a package name without a version (e.g. pkg), pnpm will attempt to apply the patch to all versions of the package, failure will be skipped. If it is a package name and an exact version (e.g. pkg@x.y.z), pnpm will attempt to apply the patch to that exact version only, failure will cause pnpm to fail.

    If there's only one version of pkg installed, pnpm patch pkg and subsequent pnpm patch-commit $edit_dir will create an entry named pkg in pnpm.patchedDependencies. And pnpm will attempt to apply this patch to other versions of pkg in the future.

    If there's multiple versions of pkg installed, pnpm patch pkg will ask which version to edit and whether to attempt to apply the patch to all. If the user chooses to apply the patch to all, pnpm patch-commit $edit_dir would create a pkg entry in pnpm.patchedDependencies. If the user chooses not to apply the patch to all, pnpm patch-commit $edit_dir would create a pkg@x.y.z entry in pnpm.patchedDependencies with x.y.z being the version the user chose to edit.

    If the user runs pnpm patch pkg@x.y.z with x.y.z being the exact version of pkg that has been installed, pnpm patch-commit $edit_dir will always create a pkg@x.y.z entry in pnpm.patchedDependencies.

3.0.1

Patch Changes

  • Updated dependencies [a7aef51]
    • @pnpm/error@6.0.1

3.0.0

Major Changes

  • 43cdd87: Node.js v16 support dropped. Use at least Node.js v18.12.

Patch Changes

  • Updated dependencies [3ded840]
  • Updated dependencies [43cdd87]
    • @pnpm/error@6.0.0

2.0.5

Patch Changes

  • 512d71254: pnpm patch should write patch files with a trailing newline #6905.

2.0.4

Patch Changes

  • 3b6930263: Throw a meaningful error when applying a patch to a dependency fails.

2.0.3

Patch Changes

  • @pnpm/error@5.0.2

2.0.2

Patch Changes

2.0.1

Patch Changes

  • @pnpm/error@5.0.1

2.0.0

Major Changes

Patch Changes

  • Updated dependencies [eceaa8b8b]
    • @pnpm/error@5.0.0

1.0.0

Major Changes

Reference in New Issue View Git Blame Copy Permalink