nx
Nx
GitHub
Nx
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
gh-36236
Runs and Agents
Timeline
Configuration
Self-Healing CI
Project Graph
Resource Usage
Analysis
Conformance
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
fix(js): parse pnpm/npm publish JSON containing braces in file paths nx release publish marked a successful publish as failed when a published file path contained curly braces (e.g. templates/{{name}}/file.txt). The publish summary was located with a fixed-depth brace-counting regex that treated braces inside JSON string values as structure, so the top-level summary object never matched and extraction returned null, surfacing "The pnpm publish output data could not be extracted" after the package had already been published to the registry. Replace the regex with a scanner that pairs each '{' with its matching '}' while treating JSON string content as opaque, so braces and quotes inside a string value no longer affect the pairing. Publish output is plain JSON mixed with arbitrary lifecycle-script text, so the scanner does not treat '//' or '/*' as comments and ends a string at a raw newline (which a valid JSON string never contains); stray quotes, globs, and comment-like text in that output no longer hide the summary. Balanced objects are scanned left to right and the summary is unwrapped (flat, or nested one level under the package name).
nx run-many -t check-imports check-lock-files check-codeowners --parallel=1 --no-dte
⌘K
Succeeded
nx run-many -t check-imports check-lock-files check-codeowners --parallel=1 --no-dte
Click to copy
Linux
4 CPU cores
80c71aef
36241
Get faster results
Learn how to enable distribution.
Atomizer enabled
1 group of tasks optimized.