Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
35954
Environment issue→
d868437d cleanup(core): consolidate registry config helpers and add upstream links [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
35954
Flaky task→
bb08d4b3 cleanup(core): consolidate registry config helpers and add upstream links - reuse fileutils readYamlFile in readPnpmYamlConfig instead of re-requiring @zkochan/js-yaml - remove the home.ts homedir wrapper and call os.homedir() directly - add commit-pinned permalinks to the upstream sources the parsers mimic (ini, npm, pnpm, yarn, bun) - de-ephemeralize the pnpm resolution comment references
by Leosvel Pé...
Failed
35954
Flaky task→
bb08d4b3 cleanup(core): consolidate registry config helpers and add upstream links - reuse fileutils readYamlFile in readPnpmYamlConfig instead of re-requiring @zkochan/js-yaml - remove the home.ts homedir wrapper and call os.homedir() directly - add commit-pinned permalinks to the upstream sources the parsers mimic (ini, npm, pnpm, yarn, bun) - de-ephemeralize the pnpm resolution comment references
by Leosvel Pé...
Succeeded
35954
690cf0d5 fix(core): expand env var references in yarn berry registry config nx migrate spawns npm to resolve and fetch packages, with an npm_config_* env overlay reproducing the workspace package manager's registry/auth/TLS resolution. The yarn berry resolver consumed raw .yarnrc.yml values, but berry expands ${VAR}/${VAR-default}/${VAR:-default} in every string setting at parse time. So a registry like `npmRegistryServer: "${REGISTRY}"` was nerf-darted as the literal placeholder (its URL parse fails), emitting no auth/TLS key for the real host, and `npmAuthIdent: "${IDENT}"` had its base64 decision made on the unexpanded value. Expand env var references on the registry URL (top-level and scoped), npmAuthToken, npmAuthIdent, and proxies before any URL parse, nerf-dart, or base64, matching berry. Also: - Run `npm pack` from the workspace root with --pack-destination so it reads the workspace .npmrc natively, matching packageRegistryView (previously a token in the workspace .npmrc was honored by view but not by pack). - Warn once when the yarn version cannot be determined and registry config is skipped, so the silent fall back to npm's default registry is diagnosable.
by Leosvel Pé...
Failed
35954
Environment issue→
690cf0d5 fix(core): expand env var references in yarn berry registry config nx migrate spawns npm to resolve and fetch packages, with an npm_config_* env overlay reproducing the workspace package manager's registry/auth/TLS resolution. The yarn berry resolver consumed raw .yarnrc.yml values, but berry expands ${VAR}/${VAR-default}/${VAR:-default} in every string setting at parse time. So a registry like `npmRegistryServer: "${REGISTRY}"` was nerf-darted as the literal placeholder (its URL parse fails), emitting no auth/TLS key for the real host, and `npmAuthIdent: "${IDENT}"` had its base64 decision made on the unexpanded value. Expand env var references on the registry URL (top-level and scoped), npmAuthToken, npmAuthIdent, and proxies before any URL parse, nerf-dart, or base64, matching berry. Also: - Run `npm pack` from the workspace root with --pack-destination so it reads the workspace .npmrc natively, matching packageRegistryView (previously a token in the workspace .npmrc was honored by view but not by pack). - Warn once when the yarn version cannot be determined and registry config is skipped, so the silent fall back to npm's default registry is diagnosable.
by Leosvel Pé...