Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
35682
2da1a308 chore(repo): update lockfile after rebase
by FrozenPandaz
Canceled
35778
403130d2 cleanup(core): require task.cache and drop isCacheableTask task.cache is now always an explicit boolean, so flip the Rust struct field from Option<bool> to bool and remove the dead isCacheableTask fallback. Internal call sites read task.cache directly. Remove the now-unused cacheableOperations / cacheableTargets from DefaultTasksRunnerOptions; the legacy nx.json fields are still consumed via the raw tasksRunnerOptions[runner].options in run-command.
by FrozenPandaz
Succeeded
22.7.x
f5e74caa chore(repo): loosen root webpack pins to allow dedupe with plugin peers
by FrozenPandaz
Canceled
35778
889851e0 fix(nx): always emit task.cache as an explicit boolean Tasks whose target config has no `cache` property serialise as `cache: null` via NAPI (Option<bool> → None). Nx Cloud DTE V4 uses a Kotlin filter `depTask.cache \!= false` to decide whether to materialise cached artifacts; `null \!= false` is `true` in Kotlin, so non-cacheable run-commands targets are incorrectly treated as potentially cacheable, causing a fatal "Task dependency not found while downloading artifacts". Fix: a single `?? false` in `createTask`: cache: project.data.targets[target].cache ?? false, This makes every Task's `cache` field a concrete boolean. `utils.ts` is untouched — `isCacheableTask` keeps its original `\!== undefined` guard as harmless defensive code. The legacy `cacheableOperations`/`cacheableTargets` fallback inside that function is effectively unreachable from the `createTaskGraph` path now that `cache` is always set, but it remains available for any Task constructed outside of `createTaskGraph`. In practice `cacheableOperations` has been dead since the Nx 17 migration `use-minimal-config-for-tasks-runner-options` rewrites each entry to `targetDefaults.<target>.cache = true` and removes the field. Test fixtures updated: all 68 expected Task objects in `create-task-graph.spec.ts` now include `cache: false` to match the normalised output.
by FrozenPandaz
Canceled
35778
11c1ba69 fix(nx): always emit task.cache as an explicit boolean Tasks whose target config has no `cache` property serialise as `cache: null` via NAPI (Option<bool> → None). Nx Cloud DTE V4 uses a Kotlin filter `depTask.cache \!= false` to decide whether to materialise cached artifacts; `null \!= false` evaluates to `true` in Kotlin, so non-cacheable run-commands targets are incorrectly treated as cacheable, causing a fatal "Task dependency not found while downloading artifacts". Fix: resolve `cache` to a concrete boolean inside `createTask` using the `??` operator. When the target has no explicit `cache` property the fallback checks `legacyCacheableTargets` — a pre-extracted list derived from the runner's `cacheableOperations` / `cacheableTargets` option so that pre-migration workspaces keep working. `utils.ts` is untouched: `isCacheableTask` retains its original `\!== undefined` guard, which now acts purely as defence for `Task` objects constructed outside of `createTaskGraph`. Changes: - `create-task-graph.ts`: add optional `legacyCacheableTargets` param to `createTaskGraph` and `ProcessTasks`; resolve `cache` inline - `run-command.ts`: extract the legacy list from nxJson runner options once in `ensureWorkspaceIsInSyncAndGetGraphs` and thread it through `createTaskGraphAndRunValidations` → `createTaskGraph` - `create-task-graph.spec.ts`: add 4 focused tests covering explicit `true`/`false`, default `false`, and legacy-list resolution
by FrozenPandaz
Canceled
35778
476fa80a fix(nx): always emit task.cache as an explicit boolean Tasks whose target config has no `cache` property serialise as `cache: null` via NAPI (Option<bool> → None). Nx Cloud DTE V4 uses a Kotlin filter `depTask.cache \!= false` to decide whether to materialise cached artifacts; `null \!= false` evaluates to `true` in Kotlin, so non-cacheable run-commands targets are incorrectly treated as cacheable, causing a fatal "Task dependency not found while downloading artifacts" error on the client. Fix: normalise `undefined | null → false` with `?? false` at the single point in `createTask` where the field is written. Also update `isCacheableTask` so the legacy `cacheableOperations` / `cacheableTargets` fallback is still honoured for workspaces that pre-date per-target `cache` config (the old check `\!== undefined` is replaced with `=== true` so the fallback fires whenever `cache` is `false`). Test expectations updated to include the now-explicit `cache: false`.
by FrozenPandaz
Succeeded
35743
249ae274 chore(testing): bump rewrite-internal-subpath-imports migration to 23.0.0-beta.19
by FrozenPandaz
Succeeded
35772
602a21d5 chore(repo): migrate pnpm settings to pnpm-workspace.yaml for pnpm 11 pnpm 11 no longer reads the `pnpm` field in package.json. Move the overrides into the existing `overrides:` block in pnpm-workspace.yaml, and configure `allowBuilds:` for the install scripts that were previously allowed via `onlyBuiltDependencies`. Regenerate the lockfile.
by FrozenPandaz
Failed
35772
602a21d5 chore(repo): migrate pnpm settings to pnpm-workspace.yaml for pnpm 11 pnpm 11 no longer reads the `pnpm` field in package.json. Move the overrides into the existing `overrides:` block in pnpm-workspace.yaml, and configure `allowBuilds:` for the install scripts that were previously allowed via `onlyBuiltDependencies`. Regenerate the lockfile.
by FrozenPandaz
Failed
35743
Flaky task→
249ae274 chore(testing): bump rewrite-internal-subpath-imports migration to 23.0.0-beta.19
by FrozenPandaz
Succeeded
35775
8a764594 chore(repo): set pnpm minimumReleaseAge to 1 day with nx exclusions Adds a 1-day minimum release age to mitigate supply-chain attacks like the node-ipc compromise. Excludes nx-published packages (nx, @nx/*, @nrwl/*, create-nx-workspace, create-nx-plugin) so freshly released Nx packages don't block install flows. Refs NXC-4466
by FrozenPandaz
Failed
35772
Flaky task→
602a21d5 chore(repo): migrate pnpm settings to pnpm-workspace.yaml for pnpm 11 pnpm 11 no longer reads the `pnpm` field in package.json. Move the overrides into the existing `overrides:` block in pnpm-workspace.yaml, and configure `allowBuilds:` for the install scripts that were previously allowed via `onlyBuiltDependencies`. Regenerate the lockfile.
by FrozenPandaz
Succeeded
35774
edb1c8a7 fix(repo): run dotnet restore before macos e2e job
by FrozenPandaz
Succeeded
35743
18cb13f9 chore(testing): bump rewrite-internal-subpath-imports migration to 23.0.0-beta.19
by FrozenPandaz
Succeeded
35772
c355ea97 chore(repo): migrate pnpm settings to pnpm-workspace.yaml for pnpm 11 pnpm 11 no longer reads the `pnpm` field in package.json. Move the overrides into the existing `overrides:` block in pnpm-workspace.yaml, and configure `allowBuilds:` for the install scripts that were previously allowed via `onlyBuiltDependencies`. Regenerate the lockfile.
by FrozenPandaz
Failed
35774
Flaky task→
edb1c8a7 fix(repo): run dotnet restore before macos e2e job
by FrozenPandaz
Failed
35772
Flaky task→
c355ea97 chore(repo): migrate pnpm settings to pnpm-workspace.yaml for pnpm 11 pnpm 11 no longer reads the `pnpm` field in package.json. Move the overrides into the existing `overrides:` block in pnpm-workspace.yaml, and configure `allowBuilds:` for the install scripts that were previously allowed via `onlyBuiltDependencies`. Regenerate the lockfile.
by FrozenPandaz
Failed
35682
Flaky task→
18b27140 chore(repo): update lockfile after rebase
by FrozenPandaz
Canceled
35772
8080c394 chore(repo): migrate pnpm settings to pnpm-workspace.yaml for pnpm 11 pnpm 11 no longer reads the `pnpm` field in package.json. Move the overrides into the existing `overrides:` block in pnpm-workspace.yaml, and configure `allowBuilds:` for the install scripts that were previously allowed via `onlyBuiltDependencies`. Regenerate the lockfile.
by FrozenPandaz
Canceled
35772
f432b37d chore(repo): migrate pnpm settings to pnpm-workspace.yaml for pnpm 11 pnpm 11 no longer reads the `pnpm` field in package.json. Move the overrides into the existing `overrides:` block in pnpm-workspace.yaml, and configure `allowBuilds:` for the install scripts that were previously allowed via `onlyBuiltDependencies`. Regenerate the lockfile.
by FrozenPandaz