Charlie Croom a99ffe0893 fix: also preserve relative symlinks in copy-artifacts.ts (release tarballs) (#11408) ...

#11399 fixed the fs.cpSync call in pnpm/artifacts/exe/scripts/build-artifacts.ts,
which controls the dist/ shipped inside the npm-published @pnpm/exe package.

But the GitHub release tarballs (pnpm-{darwin,linux}-{x64,arm64}.tar.gz) are
produced by a different script — __utils__/scripts/src/copy-artifacts.ts, run
via 'pn copy-artifacts' in the release workflow. That script has the same
fs.cpSync(...) call without verbatimSymlinks: true, so the broken absolute
symlinks under dist/node_modules/.bin/ pointing at /home/runner/work/pnpm/
pnpm/... still made it into the v11.0.2 GitHub release tarballs.

Apply the same one-line fix to that script so the next release ships clean
relative symlinks.

Follow-up to #11398.

🤖 Generated with [Amp](https://ampcode.com)

Amp-Thread-ID: https://ampcode.com/threads/T-019dda79-b947-742f-8711-b6f83bcda9ff

Co-authored-by: Amp <amp@ampcode.com>

2026-04-30 22:59:07 +02:00

..

copy-artifacts.ts

fix: also preserve relative symlinks in copy-artifacts.ts (release tarballs) (#11408)

2026-04-30 22:59:07 +02:00

typecheck-only.ts

chore(typescript): make typecheck threading configurable (#11057)

2026-03-22 00:14:40 +01:00

worktree-new.ts

chore(typescript): make typecheck threading configurable (#11057)

2026-03-22 00:14:40 +01:00