Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

In progress
36874
5351b58d fix(js): resolve the registry version without a shell `readCurrentVersionFromRegistry` interpolated the same registry and tag into an `exec` command string, so `nx release version` reached a shell with them on every platform when `currentVersionResolver` is `registry`. Run it through `safeSpawn` with argv, matching the publish path, and cover the method - it had no test before. `cwd` stays unset so npm still reads the same .npmrc `exec` gave it.
by Craigory C...
Failed
36874
5351b58d fix(js): resolve the registry version without a shell `readCurrentVersionFromRegistry` interpolated the same registry and tag into an `exec` command string, so `nx release version` reached a shell with them on every platform when `currentVersionResolver` is `registry`. Run it through `safeSpawn` with argv, matching the publish path, and cover the method - it had no test before. `cwd` stays unset so npm still reads the same .npmrc `exec` gave it.
by Craigory C...
Succeeded
36874
d3cbc233 fix(js): resolve the registry version without a shell `readCurrentVersionFromRegistry` interpolated the same registry and tag into an `exec` command string, so `nx release version` reached a shell with them on every platform when `currentVersionResolver` is `registry`. Run it through `safeSpawn` with argv, matching the publish path, and cover the method - it had no test before. `cwd` stays unset so npm still reads the same .npmrc `exec` gave it.
by Craigory C...
Failed
36874
Flaky task→
d3cbc233 fix(js): resolve the registry version without a shell `readCurrentVersionFromRegistry` interpolated the same registry and tag into an `exec` command string, so `nx release version` reached a shell with them on every platform when `currentVersionResolver` is `registry`. Run it through `safeSpawn` with argv, matching the publish path, and cover the method - it had no test before. `cwd` stays unset so npm still reads the same .npmrc `exec` gave it.
by Craigory C...