Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

In progress
master
511cf698 fix(core): restore nx/src/index entrypoint for Nx Cloud client compatibility (#35712) ## Current Behavior Under Nx 23.0.0, the Nx Cloud agent client crashes when running tasks: ``` TypeError: runContinuousTasks is not a function at AgentTaskManager.invokeContinuousTasks at AgentTaskManager.reconcileContinuousTasks at AgentTaskManager.invokeTasks at executeTasksV3 ``` The Nx Cloud client probes the nx task APIs by `require`-ing `nx/src/index` (for the legacy `initTasksRunner`) and `nx/src/tasks-runner/init-tasks-runner` (for the modern `runDiscreteTasks` / `runContinuousTasks`) inside a single shared `try/catch`. PR #35708 removed the deprecated `initTasksRunner` API and **deleted `packages/nx/src/index.ts` entirely** — even though that PR's own commit message stated the file would be kept as an empty module so the `nx/src` subpath export mapping stays valid. With the file gone, `nx/src/index` no longer resolves (`./src/*` maps to `./dist/src/index.js`, which is never built). The `require('nx/src/index')` throws, the client's shared `catch` swallows it, and `runContinuousTasks` is never assigned — later crashing when invoked. `runContinuousTasks` itself was never removed; it still lives in `packages/nx/src/tasks-runner/init-tasks-runner.ts` and is unreachable here only because the earlier `nx/src/index` probe throws. ## Expected Behavior `packages/nx/src/index.ts` is restored as an empty ES module, so the `nx/src/index` entrypoint resolves again via the existing `./src/*` mapping in `package.json` exports (no `package.json` change needed). The deprecated `initTasksRunner` export stays removed — consumers still get `undefined` for it — but the `require` no longer throws, so the Nx Cloud client proceeds to load `runContinuousTasks` / `runDiscreteTasks` correctly. This restores compatibility for already-published/cached Nx Cloud client bundles without requiring them to be updated. ## Related Issue(s) Internal: NXC-4307 (follow-up to #35708)  --- [View session information ↗](https://snapshot.app.trypolygraph.com/orgs/69cdc268b6aa527e4129c2b4/sessions/master-1efdcf12-fbbd-49c0-954c-3637c415400a-d8a02644)  --------- Co-authored-by: Jason Jean <jasonjean1993@gmail.com> Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
by polygraph-...
Succeeded
35715
39656fea chore(repo): replace glob with tinyglobby
by Leosvel Pé...
Failed
35631
Fix ready→
7245558d fix(core): handle local plugin subpath dist fallback
by Leosvel Pé...
Failed
35671
Fix available→
398101e0 chore(testing): refine vitest 3/4 AI migration prompts for accuracy and steering - correct vitest 4 browser provider example (function from per-provider package) - fix pool options example: singleFork:true -> maxWorkers:1, isolate:false - add vitest 4 prerequisites (Vite >=6, Node >=20) and exclude-defaults narrowing - add Nx-specific notes (inferred plugin targets, shared base config, Analog) - cover transformMode -> viteEnvironment, deps.optimizer.web -> .client - snapshot section: correct printShadowRoot placement, add Snapshots import, vi.fn string change - reporter API: include all five removed callbacks with concrete replacements - vitest 3: clarify v3.2 workspace option rename vs v4 file removal - vitest 3: clarify browser.name/providerOptions deprecation vs removal - correct mockRestore wording (single-spy mockRestore still works in v4)
by Leosvel Pé...
Failed
35688
Environment issue→
6f6ee0b7 chore(misc): apply nx-plugin-checks rule to migrations.json in nuxt, vite, vitest These plugins' eslint configs didn't include ./migrations.json in the files block for @nx/nx-plugin-checks, so the rule never ran on them. Aligns lint coverage with next/expo/storybook.
by Leosvel Pé...
Succeeded
733
cf4a8c91
by pull[bot]
Succeeded
master
511cf698 fix(core): restore nx/src/index entrypoint for Nx Cloud client compatibility (#35712) ## Current Behavior Under Nx 23.0.0, the Nx Cloud agent client crashes when running tasks: ``` TypeError: runContinuousTasks is not a function at AgentTaskManager.invokeContinuousTasks at AgentTaskManager.reconcileContinuousTasks at AgentTaskManager.invokeTasks at executeTasksV3 ``` The Nx Cloud client probes the nx task APIs by `require`-ing `nx/src/index` (for the legacy `initTasksRunner`) and `nx/src/tasks-runner/init-tasks-runner` (for the modern `runDiscreteTasks` / `runContinuousTasks`) inside a single shared `try/catch`. PR #35708 removed the deprecated `initTasksRunner` API and **deleted `packages/nx/src/index.ts` entirely** — even though that PR's own commit message stated the file would be kept as an empty module so the `nx/src` subpath export mapping stays valid. With the file gone, `nx/src/index` no longer resolves (`./src/*` maps to `./dist/src/index.js`, which is never built). The `require('nx/src/index')` throws, the client's shared `catch` swallows it, and `runContinuousTasks` is never assigned — later crashing when invoked. `runContinuousTasks` itself was never removed; it still lives in `packages/nx/src/tasks-runner/init-tasks-runner.ts` and is unreachable here only because the earlier `nx/src/index` probe throws. ## Expected Behavior `packages/nx/src/index.ts` is restored as an empty ES module, so the `nx/src/index` entrypoint resolves again via the existing `./src/*` mapping in `package.json` exports (no `package.json` change needed). The deprecated `initTasksRunner` export stays removed — consumers still get `undefined` for it — but the `require` no longer throws, so the Nx Cloud client proceeds to load `runContinuousTasks` / `runDiscreteTasks` correctly. This restores compatibility for already-published/cached Nx Cloud client bundles without requiring them to be updated. ## Related Issue(s) Internal: NXC-4307 (follow-up to #35708)  --- [View session information ↗](https://snapshot.app.trypolygraph.com/orgs/69cdc268b6aa527e4129c2b4/sessions/master-1efdcf12-fbbd-49c0-954c-3637c415400a-d8a02644)  --------- Co-authored-by: Jason Jean <jasonjean1993@gmail.com> Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
by polygraph-...
Failed
35705
Flaky task→
45d196f6 chore(core): log watcher event age at debug for flake diagnosis
by Jason Jean
Failed
master
511cf698 fix(core): restore nx/src/index entrypoint for Nx Cloud client compatibility (#35712) ## Current Behavior Under Nx 23.0.0, the Nx Cloud agent client crashes when running tasks: ``` TypeError: runContinuousTasks is not a function at AgentTaskManager.invokeContinuousTasks at AgentTaskManager.reconcileContinuousTasks at AgentTaskManager.invokeTasks at executeTasksV3 ``` The Nx Cloud client probes the nx task APIs by `require`-ing `nx/src/index` (for the legacy `initTasksRunner`) and `nx/src/tasks-runner/init-tasks-runner` (for the modern `runDiscreteTasks` / `runContinuousTasks`) inside a single shared `try/catch`. PR #35708 removed the deprecated `initTasksRunner` API and **deleted `packages/nx/src/index.ts` entirely** — even though that PR's own commit message stated the file would be kept as an empty module so the `nx/src` subpath export mapping stays valid. With the file gone, `nx/src/index` no longer resolves (`./src/*` maps to `./dist/src/index.js`, which is never built). The `require('nx/src/index')` throws, the client's shared `catch` swallows it, and `runContinuousTasks` is never assigned — later crashing when invoked. `runContinuousTasks` itself was never removed; it still lives in `packages/nx/src/tasks-runner/init-tasks-runner.ts` and is unreachable here only because the earlier `nx/src/index` probe throws. ## Expected Behavior `packages/nx/src/index.ts` is restored as an empty ES module, so the `nx/src/index` entrypoint resolves again via the existing `./src/*` mapping in `package.json` exports (no `package.json` change needed). The deprecated `initTasksRunner` export stays removed — consumers still get `undefined` for it — but the `require` no longer throws, so the Nx Cloud client proceeds to load `runContinuousTasks` / `runDiscreteTasks` correctly. This restores compatibility for already-published/cached Nx Cloud client bundles without requiring them to be updated. ## Related Issue(s) Internal: NXC-4307 (follow-up to #35708)  --- [View session information ↗](https://snapshot.app.trypolygraph.com/orgs/69cdc268b6aa527e4129c2b4/sessions/master-1efdcf12-fbbd-49c0-954c-3637c415400a-d8a02644)  --------- Co-authored-by: Jason Jean <jasonjean1993@gmail.com> Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
by polygraph-...
Succeeded
master
511cf698 fix(core): restore nx/src/index entrypoint for Nx Cloud client compatibility (#35712) ## Current Behavior Under Nx 23.0.0, the Nx Cloud agent client crashes when running tasks: ``` TypeError: runContinuousTasks is not a function at AgentTaskManager.invokeContinuousTasks at AgentTaskManager.reconcileContinuousTasks at AgentTaskManager.invokeTasks at executeTasksV3 ``` The Nx Cloud client probes the nx task APIs by `require`-ing `nx/src/index` (for the legacy `initTasksRunner`) and `nx/src/tasks-runner/init-tasks-runner` (for the modern `runDiscreteTasks` / `runContinuousTasks`) inside a single shared `try/catch`. PR #35708 removed the deprecated `initTasksRunner` API and **deleted `packages/nx/src/index.ts` entirely** — even though that PR's own commit message stated the file would be kept as an empty module so the `nx/src` subpath export mapping stays valid. With the file gone, `nx/src/index` no longer resolves (`./src/*` maps to `./dist/src/index.js`, which is never built). The `require('nx/src/index')` throws, the client's shared `catch` swallows it, and `runContinuousTasks` is never assigned — later crashing when invoked. `runContinuousTasks` itself was never removed; it still lives in `packages/nx/src/tasks-runner/init-tasks-runner.ts` and is unreachable here only because the earlier `nx/src/index` probe throws. ## Expected Behavior `packages/nx/src/index.ts` is restored as an empty ES module, so the `nx/src/index` entrypoint resolves again via the existing `./src/*` mapping in `package.json` exports (no `package.json` change needed). The deprecated `initTasksRunner` export stays removed — consumers still get `undefined` for it — but the `require` no longer throws, so the Nx Cloud client proceeds to load `runContinuousTasks` / `runDiscreteTasks` correctly. This restores compatibility for already-published/cached Nx Cloud client bundles without requiring them to be updated. ## Related Issue(s) Internal: NXC-4307 (follow-up to #35708)  --- [View session information ↗](https://snapshot.app.trypolygraph.com/orgs/69cdc268b6aa527e4129c2b4/sessions/master-1efdcf12-fbbd-49c0-954c-3637c415400a-d8a02644)  --------- Co-authored-by: Jason Jean <jasonjean1993@gmail.com> Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
by polygraph-...
Failed
35705
Flaky task→
45d196f6 chore(core): log watcher event age at debug for flake diagnosis
by Jason Jean
Succeeded
732
9f99425a
by pull[bot]
Succeeded
35709
ed87f14c fix(core): nest releaseTagPattern under releaseTag and correct migration version The flat release.releaseTagPattern property was removed in Nx 23, so the workspace's own nx.json must use the nested releaseTag.pattern form. Also bump the 23-0-0-consolidate-release-tag-config migration version from 23.0.0-beta.0 to 23.0.0-beta.16. The breaking removal shipped in 23.0.0-beta.13, so users already on a 23.0.0 beta past beta.0 would skip the migration yet still hit the hard error.
by Jason Jean
Failed
34951
Environment issue→
d71808d2 cleanup(core): cover shell completion fixes and add NX_COMPLETE_DEBUG Addresses the attempt-2 review follow-ups: - Regression tests for the two critical fixes: resolveWorkspaceRoot() is exported and tested directly (env-var case, nx.json walk-up from a nested cwd, no-nx.json fallback); DESC_SEPARATOR is asserted to be a TAB; scripts.spec.ts now asserts the zsh wrapper uses `compadd -d` and never invokes `_describe`, the bash/zsh/fish walk-up, and the PowerShell nx.cmd walk-up. - NX_COMPLETE_DEBUG: the four wrapper scripts hid completion stderr unconditionally, so a fatal startup regression was invisible. They now surface stderr when NX_COMPLETE_DEBUG is set. Documented in the environment-variables reference. - formatDescription collapses literal TABs to spaces so a plugin-supplied description cannot break the zsh value/description split.
by Jason Jean
Succeeded
623
3b2f15e5
by pull[bot]
Failed
34951
Flaky task→
fcdc6d39 fix(core): correct shell completion from subdirectories and in zsh Addresses the two critical findings from the deep PR review: 1. Project/target/generator completion returned nothing unless TAB was pressed at the workspace root. Completion runs without the normal workspace bootstrap, so NX_WORKSPACE_ROOT_PATH was unset and the graph lookup used process.cwd(). completion-providers.ts now walks up from cwd to the nearest nx.json to resolve the workspace root. 2. zsh two-stage `project:target` / `plugin:generator` completion never worked: the wrapper fed values to `_describe`, which splits on the first colon. The binary now emits `value<TAB>description` for zsh and the wrapper uses `compadd -d` so values are inserted literally. Also: move the completion trigger check inline in bin/nx.ts so no import runs before the protective try/catch; add the local-nx walk-up to the PowerShell wrapper; fix comment rot referencing the removed yargs path.
by Jason Jean
Failed
35303
Flaky task→
53b3869a chore(testing): dial e2e-ci parallelism back to 3/6 [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
35303
Flaky task→
023ccec9 chore(testing): dial e2e-ci parallelism back to 3/6 [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
34951
Flaky task→
fcdc6d39 fix(core): correct shell completion from subdirectories and in zsh Addresses the two critical findings from the deep PR review: 1. Project/target/generator completion returned nothing unless TAB was pressed at the workspace root. Completion runs without the normal workspace bootstrap, so NX_WORKSPACE_ROOT_PATH was unset and the graph lookup used process.cwd(). completion-providers.ts now walks up from cwd to the nearest nx.json to resolve the workspace root. 2. zsh two-stage `project:target` / `plugin:generator` completion never worked: the wrapper fed values to `_describe`, which splits on the first colon. The binary now emits `value<TAB>description` for zsh and the wrapper uses `compadd -d` so values are inserted literally. Also: move the completion trigger check inline in bin/nx.ts so no import runs before the protective try/catch; add the local-nx walk-up to the PowerShell wrapper; fix comment rot referencing the removed yargs path.
by Jason Jean
Failed
35303
Flaky task→
a1f8adad chore(testing): dial e2e-ci parallelism back to 3/6 4/8 oversubscribed the agents — workspace creation ran 6-9x slower than normal, causing build/release orchestration to hang. drop non-MF e2e-ci to 3/6. (the module federation isolation rule is unchanged.)
by Jason Jean