Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

In progress
36086
3ab7b794 fix(core): comma-split pnpm minimumReleaseAgeExclude from .npmrc and npm_config_* pnpm v10 reads these settings via @pnpm/npm-conf, which treats array-typed values as comma-separated lists (trimming each entry). nx read the whole line as a single entry, so a valid config like 'minimum-release-age-exclude=nx,@nx/*' parsed as one invalid pattern, the policy went ambiguous, and migrate fell back to a package-manager install instead of honoring the exclusion. Comma-split and trim the v10 npm-conf surfaces to match pnpm. v11's pnpm_config_* schema is JSON-or-single and is intentionally left unchanged.
by FrozenPandaz
Failed
36086
Environment issue→
93907fed fix(core): keep a non-empty packages field in temp pnpm-workspace.yaml during migrate nx migrate copies pnpm-workspace.yaml into a temp install dir and previously stripped the `packages` field entirely. pnpm <10.5 (and corepack's bundled default pnpm, which runs in the temp dir because it has no packageManager pin) reject a workspace manifest whose packages field is missing or empty, failing with "packages field missing or empty" and breaking migration fetching. Replace the member globs with a self-reference ('.') so the field stays non-empty and resolves only the temp root.
by FrozenPandaz
Canceled
36086
93907fed fix(core): keep a non-empty packages field in temp pnpm-workspace.yaml during migrate nx migrate copies pnpm-workspace.yaml into a temp install dir and previously stripped the `packages` field entirely. pnpm <10.5 (and corepack's bundled default pnpm, which runs in the temp dir because it has no packageManager pin) reject a workspace manifest whose packages field is missing or empty, failing with "packages field missing or empty" and breaking migration fetching. Replace the member globs with a self-reference ('.') so the field stays non-empty and resolves only the temp root.
by FrozenPandaz
Failed
36086
Flaky task→
93907fed fix(core): keep a non-empty packages field in temp pnpm-workspace.yaml during migrate nx migrate copies pnpm-workspace.yaml into a temp install dir and previously stripped the `packages` field entirely. pnpm <10.5 (and corepack's bundled default pnpm, which runs in the temp dir because it has no packageManager pin) reject a workspace manifest whose packages field is missing or empty, failing with "packages field missing or empty" and breaking migration fetching. Replace the member globs with a self-reference ('.') so the field stays non-empty and resolves only the temp root.
by FrozenPandaz