Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

In progress
34521
1c6f00ac docs(misc): add initial style guide and fix up getting started pages
4 minutes ago by jaysoo
In progress
34589
Environment issue→
167a9f04 feat(gradle): use glob patterns for task inputs Refactor task input processing to use glob patterns instead of individual file paths. This improves cache efficiency by grouping source files by their source roots and using {projectRoot}/**/* and {workspaceRoot}/**/* patterns. Also improves NxProjectReportTask to use buffered file comparison instead of loading entire JSON into memory for comparison.
16 minutes ago by lourw
In progress
34588
60e16181 fix(core): reject pending promises directly when plugin worker exits unexpectedly When a plugin worker process exits unexpectedly, the exit handler previously sent synthetic `loadResult` messages to all pending response handlers. If any handler was waiting for a different result type (e.g. `createNodesResult`), the type validation would reject with a confusing "Expected createNodesResult, got loadResult" error instead of surfacing the actual cause. Split response handlers into `onMessage` / `onError` callbacks so the exit handler can reject each pending promise directly with a clear "Plugin worker exited unexpectedly" error. Also use unique transaction IDs for `load` messages (via `generateTxId`) to avoid potential handler overwrites during worker restarts. Fixes #34564
31 minutes ago by AgentEnder
Failed
34587
Environment issue→
397b9055 chore(gradle): update gradle project configuration - Update gradle project.json configuration - Modify CI workflow and nx.json
32 minutes ago by FrozenPandaz
Canceled
34587
f482e69d chore(gradle): restore batch-runner project.json and update project-graph - Restore batch-runner project.json with proper configuration - Update project-graph project.json
36 minutes ago by FrozenPandaz
In progress
master
f42976f8 fix(repo): remove chalk from e2e tests (#34570)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
43 minutes ago by meeroslav
In progress
34358
a39f7fb4 fix(core): properly pipe stderr in runCLI for redirectStderr option Co-authored-by: AgentEnder <AgentEnder@users.noreply.github.com>
46 minutes ago by nx-cloud[bot]
Canceled
34587
410d9c81 chore(gradle): clean up project.json configurations - Remove batch-runner project.json (consolidated into parent) - Remove duplicate targets from project-graph project.json - Fix implicit dependency syntax to use project name format - Remove unnecessary implicitDependencies from e2e/gradle
56 minutes ago by FrozenPandaz
Failed
34586
Generating fix→
8578e4b8 chore(gradle): clean up project.json configurations - Remove batch-runner project.json (consolidated into parent) - Remove duplicate targets from project-graph project.json - Fix implicit dependency syntax to use project name format - Remove unnecessary implicitDependencies from e2e/gradle
57 minutes ago by FrozenPandaz
In progress
34558
8f373d94 fix(nx-dev): ensure ai is resolvable during nx-dev next build [Self-Healing CI Rerun]
58 minutes ago by nx-cloud[bot]
Failed
master
7f7bba63 fix(bundling): add docs link to generatePackageJson error message (#34562) ## Current Behavior When users hit the `generatePackageJson: true` error with TS Solution Setup, the error tells them to "unset the option" but gives no guidance on the replacement workflow. ## Expected Behavior The error message now includes a link to the pruning guide at https://nx.dev/docs/technologies/node/guides/deploying-node-projects so users can immediately find the migration steps. ## Related Issue(s) Related #30146
1 hour ago by jaysoo
In progress
34171
adfda341 fix(release): allow null values in schema of dockerVersion
1 hour ago by mpsanchis
In progress
34585
31abd2df fix(nx-dev): correct interpolate sub command for cli reference also adding e2e
1 hour ago by barbados-c...
In progress
34582
274f22ee fix(core): skip writing deps cache if already up-to-date
1 hour ago by AgentEnder
In progress
34583
28689fb8 fix(bundling): fix regression on process.env usage for webpack When we optimized the `process.env` values to not embed the full object unnecessarily, we also regressed in cases where users do use `process.env` instead of `process.env["NX_PUBLIC_FOO"]`. ## Current behavior Users cannot use `process.env` and must access each key individuall. Although the serializing the full object can bloat bundle sizes, we also don't want to break existing apps unnecessarily. ## Expected behavior Existing apps should continue to work as usual. ## Related issues Fixes #34279
1 hour ago by jaysoo
Canceled
34582
8af63d5b fix(core): skip writing deps cache if already up-to-date
1 hour ago by AgentEnder
Failed
34581
Environment issue→
f0f1db0e chore(gradle): bump version to 0.1.13 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 hour ago by lourw
Succeeded
543
4a952d64
2 hours ago
u
Succeeded
34580
8e004b5c feat(core): add explicit cloud opt-out to create-nx-workspace The CNW cloud prompt previously only offered Yes/Skip, making it impossible to distinguish "not now" from "never." This adds a third option so we can respect user intent and stop prompting opted-out users. Prompt choices: Yes / Skip for now / No, don't ask again - Yes: connects workspace to Nx Cloud (writes nxCloudId to nx.json) - Skip for now: deferred connection, shows setup URL (existing behavior) - No, don't ask again: sets neverConnectToCloud: true in nx.json, suppresses all cloud messaging CLI: --nxCloud=yes|skip|never. Non-interactive defaults to skip. Also fixes "set up" → "setup" typo in completion banner.
2 hours ago by jaysoo
Succeeded
master
6d905722 fix(core): show the correct status for stopped continuous tasks (#34226) ## Current Behavior ### 1. Continuous tasks missing from `postTasksExecution` hook When running continuous tasks (e.g., `nx serve app`) and stopping them with Ctrl+C, the `postTasksExecution` lifecycle hook does not include them in `taskResults`. This breaks plugins that rely on post-run statistics (e.g., uploading task stats to DataDog). ### 2. Confusing TUI status when sibling continuous task exits When multiple continuous tasks run together and one exits unexpectedly, its sibling is marked as "failed" even though it was intentionally terminated/stopped by the task orchestrator. ## Expected Behavior 1. All tasks, including continuous ones, are included in `taskResults` for the `postTasksExecution` hook 2. Continuous tasks that are intentionally stopped (because dependent tasks completed or during graceful shutdown) report as `success` with `Stopped` display status 3. Continuous tasks that exit unexpectedly (crash) report as `failure` 4. TUI summary shows correct status: success when all tasks completed successfully, square icon for stopped tasks ## Related Issue(s) Fixes https://github.com/nrwl/nx/issues/33561 Supersedes: - https://github.com/nrwl/nx/pull/33562 - https://github.com/nrwl/nx/pull/34132
2 hours ago by AgentEnder