mirror of
https://github.com/pnpm/pnpm.git
synced 2026-07-30 09:27:16 -04:00
5819fc671e
* chore(release): drop the packing workarounds now that pacquet 12.0.0-alpha.19 is pinned The pinned pacquet now carries the fs-packlist fix from https://github.com/pnpm/pnpm/pull/13231, so a files allowlist wins over workspace-inherited ignore rules and the release workflow no longer needs to neutralize them: remove the empty pnpm11/pnpm/.npmignore override, the temporary root .gitignore shadow, and the pre-publish payload verification step (with its script) that guarded against the now-fixed empty-tarball packing bug. The payload-verify step was also what broke the v11.17.0 release: its filtered pn list fired a verifyDepsBeforeRun auto-install that pruned the excluded pnpm project's node_modules, so the darwin-arm64 artifact's prepublishOnly could no longer resolve symlink-dir. `@pnpm/prepare` and `@pnpm/prepare-temp-dir` were the only publishable packages without a files allowlist; their lib/ payload survived packing only through the .gitignore shadow. Give them files allowlists so their tarballs no longer depend on workspace ignore state. * chore: record the pacquet 12.0.0-alpha.19 pin in the lockfile * chore: drop the changeset - both files-allowlist fixes ship without a new version The pending `@pnpm/prepare` 1100.0.22 is not on npm yet, so the rerun of the v11.17.0 release publishes it with the files allowlist already in place. `@pnpm/prepare-temp-dir` 1100.0.1 is already published with correct tarball content (packed under the .gitignore shadow), so its manifest-only change needs no republish. A changeset would only schedule a patch release whose sole delta is the manifest field.