fix(js): trust exit code for pnpm >= 11 in release-publish executor

[comp615]

Current Behavior

nx release publish silently fails when the workspace uses pnpm 11+:

• pnpm 11 reimplemented pnpm publish natively (feat!: replace npm publish with libnpmpublish pnpm/pnpm#10591). It no longer delegates to the npm CLI.
• The new implementation accepts --json but writes nothing to stdout on success (the publish handler returns undefined; --json only suppresses the human-readable reporter).
• release-publish.impl.ts runs the publish command and parses stdout via extractNpmPublishJsonData. With empty stdout the extractor returns { jsonData: null }, the executor logs "The pnpm publish output data could not be extracted" and returns success: false.
• Combined with the default --nx-bail=true, this aborts the rest of a release after the first parallel batch: tarballs reach the registry for the packages that were attempted, but Nx marks the task failed and skips the remaining packages. Releases look "passed" in CI but are partial.

Tracked at:

• pnpm publish --json produces empty stdout in pnpm 11 (regression from pnpm 10) pnpm/pnpm#11476 — pnpm publish --json produces empty stdout in pnpm 11 (regression from pnpm 10)
• nx release publish marks every task failed under pnpm 11 ("could not be extracted") because pnpm 11's native publish writes nothing to stdout #35575 — Nx-side report

Expected Behavior

When pm === 'pnpm' and the detected pnpm major version is >= 11, trust the exit code: execSync already throws on non-zero exit, so reaching this branch means the publish succeeded. Print a minimal summary line and return { success: true }, matching the existing pm === 'bun' branch precedent (added in #34835).

This intentionally drops the verbose === Tarball Details === table for pnpm >= 11. Once pnpm restores --json stdout output (pnpm/pnpm#11476), the JSON extraction path will succeed again and this short-circuit becomes a no-op that can be removed.

The official pnpm-side workaround for users who need the npm-CLI semantics today is pnpm pack && npm publish *.tgz (documented in the changeset for pnpm/pnpm#10591).

Verification of no duplicate PRs

Before opening, I searched open Nx PRs for extract-npm-publish-json-data, release-publish.impl, and #35575 — no open PRs touch this code path.

Related Issue(s)

Refs #35575
Refs pnpm/pnpm#11476
Refs pnpm/pnpm#10591

🤖 Authored with assistance from Amp.

[netlify]

👷 Deploy request for nx-docs pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	9cd1b6a

[netlify]

👷 Deploy request for nx-dev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	9cd1b6a

[comp615]

I think since the pnpm fix got in so quick, we might be able to avoid this and just have some pnpm versions that don't work

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 9cd1b6a

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e,e2e-c...	⛔ Cancelled	4m 2s	View ↗
nx run-many -t check-imports check-lock-files c...	✅ Succeeded	3s	View ↗
nx-cloud record -- pnpm nx-cloud conformance:check	✅ Succeeded	17s	View ↗
nx build workspace-plugin	✅ Succeeded	<1s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	24s	View ↗
nx-cloud record -- nx format:check	✅ Succeeded	6s	View ↗

---

☁️ Nx Cloud last updated this comment at 2026-05-06 17:49:47 UTC