Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
35866
75ff3ba4 fix(core): trust workspace addDev in installPackageToTmp so pnpm `-w` is preserved The hardcoded `addCommand = 'pnpm add -D'` override stripped `-w` from `pmCommands.addDev`. That was correct when the temp dir had no `pnpm-workspace.yaml`, but the recent fix to copy a sanitized `pnpm-workspace.yaml` into the temp dir promotes it to a workspace root and pnpm rejects `pnpm add -D` (no `-w`) there. Use `pmCommands.addDev` verbatim and thread the resolved package manager through `installPackageToTmp` / `installPackageToTmpAsync` / `preparePackageInstallation` so callers (init-v2, configure-ai-agents, latest-nx, set-up-ai-agents, devkit's ensurePackage) pass the right detection root rather than the function re-detecting from `workspaceRoot` by default.
by Jason Jean
Failed
35866
Flaky task→
75ff3ba4 fix(core): trust workspace addDev in installPackageToTmp so pnpm `-w` is preserved The hardcoded `addCommand = 'pnpm add -D'` override stripped `-w` from `pmCommands.addDev`. That was correct when the temp dir had no `pnpm-workspace.yaml`, but the recent fix to copy a sanitized `pnpm-workspace.yaml` into the temp dir promotes it to a workspace root and pnpm rejects `pnpm add -D` (no `-w`) there. Use `pmCommands.addDev` verbatim and thread the resolved package manager through `installPackageToTmp` / `installPackageToTmpAsync` / `preparePackageInstallation` so callers (init-v2, configure-ai-agents, latest-nx, set-up-ai-agents, devkit's ensurePackage) pass the right detection root rather than the function re-detecting from `workspaceRoot` by default.
by Jason Jean
Failed
35866
Fix available→
3e84c772 fix(core): copy a sanitized pnpm-workspace.yaml into the migration temp install [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
35866
Flaky task→
8e307ef9 fix(core): copy a sanitized pnpm-workspace.yaml into the migration temp install For pnpm workspaces the temporary migration-fetch install runs `pnpm add -w`, which fails with "--workspace-root may only be used inside a workspace" unless a pnpm-workspace.yaml is present in the directory. Copy one into the temp dir, sanitized to fit the new location: drop `packages` (workspace member globs) and `patchedDependencies` (relative patch-file paths), which only resolve in the real workspace, and keep the rest (registry, auth, minimumReleaseAge, ...). This also lets the install honor the workspace's registry/auth and release-age settings instead of silently bypassing them.
by FrozenPandaz
Failed
35866
Environment issue→
8e307ef9 fix(core): copy a sanitized pnpm-workspace.yaml into the migration temp install For pnpm workspaces the temporary migration-fetch install runs `pnpm add -w`, which fails with "--workspace-root may only be used inside a workspace" unless a pnpm-workspace.yaml is present in the directory. Copy one into the temp dir, sanitized to fit the new location: drop `packages` (workspace member globs) and `patchedDependencies` (relative patch-file paths), which only resolve in the real workspace, and keep the rest (registry, auth, minimumReleaseAge, ...). This also lets the install honor the workspace's registry/auth and release-age settings instead of silently bypassing them.
by FrozenPandaz
Failed
35866
Flaky task→
8e307ef9 fix(core): copy a sanitized pnpm-workspace.yaml into the migration temp install For pnpm workspaces the temporary migration-fetch install runs `pnpm add -w`, which fails with "--workspace-root may only be used inside a workspace" unless a pnpm-workspace.yaml is present in the directory. Copy one into the temp dir, sanitized to fit the new location: drop `packages` (workspace member globs) and `patchedDependencies` (relative patch-file paths), which only resolve in the real workspace, and keep the rest (registry, auth, minimumReleaseAge, ...). This also lets the install honor the workspace's registry/auth and release-age settings instead of silently bypassing them.
by FrozenPandaz
Failed
35866
Environment issue→
4f732bd8 fix(core): use workspace package manager when fetching migrations via install When `nx migrate` falls back to installing a package in a temporary directory to read its migrations, the install detected the package manager from that empty temp directory. With no lock file there, detection fell back to npm even in yarn/pnpm/bun workspaces, so the install ran with npm and ignored the workspace package manager's registry/auth configuration. The package manager is already resolved in `generateMigrationsJsonAndUpdatePackageJson` before the fetcher is created, so thread that value through `createFetcher` into the install fallback instead of re-detecting it against the temp directory.
by FrozenPandaz
Canceled
35866
4f732bd8 fix(core): use workspace package manager when fetching migrations via install When `nx migrate` falls back to installing a package in a temporary directory to read its migrations, the install detected the package manager from that empty temp directory. With no lock file there, detection fell back to npm even in yarn/pnpm/bun workspaces, so the install ran with npm and ignored the workspace package manager's registry/auth configuration. The package manager is already resolved in `generateMigrationsJsonAndUpdatePackageJson` before the fetcher is created, so thread that value through `createFetcher` into the install fallback instead of re-detecting it against the temp directory.
by FrozenPandaz