Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36241
eb616c06 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).
by Leosvel Pé...
Canceled
36241
eb616c06 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).
by Leosvel Pé...
Canceled
36241
adce214b 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 jsonc-parser's JSON scanner to pair each '{' with its matching '}': string values are tokenized as single units, so braces and quotes inside them (and a stray quote in lifecycle-script output) never throw off the pairing. The balanced objects are then scanned left to right and the summary is unwrapped (flat, or nested one level under the package name). This handles arbitrary braces in string values and arbitrary nesting depth.
by Leosvel Pé...
Succeeded
36241
a2b25b31 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 single string-aware pass that pairs each '{' with its matching '}', ignoring braces and quotes inside string literals, then scan the balanced objects left to right. This handles arbitrary braces in string values and arbitrary nesting depth, and stray unbalanced braces in surrounding lifecycle-script output no longer prevent the summary from being found.
by Leosvel Pé...
Failed
36241
Generating fix→
6c237d15 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 single string-aware pass that pairs each '{' with its matching '}', ignoring braces and quotes inside string literals, then scan the balanced objects left to right. This handles arbitrary braces in string values and arbitrary nesting depth, and stray unbalanced braces in surrounding lifecycle-script output no longer prevent the summary from being found.
by Leosvel Pé...