Current Behavior

If any of the commands that are run from within the nx-release-publish executor fail, some errors won't be surfaced properly as the executor assumes the output is JSON. This makes it impossible to fix the actual root cause as there is no way to determine the underlying issue that made the command fail.

Expected Behavior

Errors from the commands are properly surfaced no matter the shape of them.

GitHub Repo

No response

Steps to Reproduce

1. Adding a prepublishOnly script that refers to another non-existing script, e.g. "prepublishOnly": "pnpm run does-not-exist"
2. Create a release and try to publish it.

Nx Report

Node           : 24.13.1
OS             : darwin-arm64
Native Target  : aarch64-macos
pnpm           : 10.30.0
daemon         : Disabled

nx                 : 22.5.1
@nx/js             : 22.5.1
@nx/eslint         : 22.5.1
@nx/workspace      : 22.5.1
@nx/jest           : 22.5.1
@nx/devkit         : 22.5.1
@nx/esbuild        : 22.5.1
@nx/eslint-plugin  : 22.5.1
@nx/node           : 22.5.1
@nx/vitest         : 22.5.1
@nx/docker         : 22.5.1
typescript         : 5.9.3
---------------------------------------
Registered Plugins:
@contentful/nx
---------------------------------------
Community plugins:
@contentful/nx : 0.42.3
---------------------------------------
Cache Usage: 13.62 KB / 46.04 GB

Failure Logs

Package Manager Version

No response

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

No response