Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
master
1afb96b7 fix(gradle): always check disk cache for gradle project graph reports (#34873) ## Current Behavior The Gradle plugin uses an in-memory `gradleCurrentConfigHash` variable to decide whether to skip re-running `./gradlew nxProjectGraph`. Since plugin workers shut down between graph computations, this variable resets to `undefined` each time. The `??=` operator on the disk cache read means it's only read once per worker lifetime, and the `!gradleCurrentConfigHash` check always evaluates to `true` on fresh workers — making the in-memory hash comparison dead code. This means the caching logic works despite itself (via disk cache), but is fragile and could cause unnecessary Gradle invocations or stale cache hits if worker lifecycle assumptions change. There was also another issue with hashing options when calculating the project graph for nodes and dependencies. Options were not normalized when hashing which you did not get deterministic hashing when calling dependencies after createNodes. ## Expected Behavior Always read the disk cache and compare hashes directly. If the hash matches, skip running Gradle. If not, run Gradle and update the disk cache. No in-memory state needed between worker restarts. Options are normalized before hashing to ensure that regardless of createNodes or dependencies, we will get a deterministic hash. ## Related Issue(s)  --------- Co-authored-by: lourw <56288712+lourw@users.noreply.github.com>
60 minutes ago by Jason Jean
Succeeded
34873
d9d49056 fix(gradle): ensure that hashed options are always normalized
1 hour ago by lourw
Failed
master
332671d2 chore(core): update nx to 22.6.0-rc.0 (#34872) ## Current Behavior Nx packages are pinned to 22.6.0-beta.13. ## Expected Behavior Nx packages updated to the latest pre-release 22.6.0-rc.0. ## Related Issue(s) N/A - routine version bump  --- [View session information on Nx Cloud ↗](https://staging.nx.app/orgs/62d013d4d26f260059f7765e/agent-sessions/update-00367) **Related PRs:** > - https://github.com/nrwl/nx-examples/pull/426  Co-authored-by: FrozenPandaz <jasonjean1993@gmail.com>
2 hours ago by nx-cloud[bot]
Succeeded
master
35930fd0 fix(core): add .claude/settings.local.json to .gitignore (#34870) ## Current Behavior When configuring AI agents via `nx polygraph`, a `.claude/settings.local.json` file is created containing user-specific settings. This file is not gitignored by Nx, so it can accidentally be committed to the repository. ## Expected Behavior `.claude/settings.local.json` should be gitignored by default, similar to how `.claude/worktrees` is already handled. ## Changes - Added a migration that adds `.claude/settings.local.json` to existing workspaces' `.gitignore` - Updated all three `.gitignore` templates so new workspaces include it from the start - Follows the same pattern as the existing `add-claude-worktrees-to-git-ignore` migration
3 hours ago by Jason Jean
Succeeded
508
151a7905
3 hours ago by pull[bot]
Succeeded
34873
3707e3d7 fix(gradle): always check disk cache for gradle project graph reports The in-memory gradleCurrentConfigHash variable was unreliable because plugin workers shut down between graph computations, resetting module state. This could cause stale cache hits or missed cache opportunities. Replace the broken two-layer caching (in-memory + disk) with a simple disk-only check: always read the disk cache and compare hashes directly.
3 hours ago by FrozenPandaz
Succeeded
master
35930fd0 fix(core): add .claude/settings.local.json to .gitignore (#34870) ## Current Behavior When configuring AI agents via `nx polygraph`, a `.claude/settings.local.json` file is created containing user-specific settings. This file is not gitignored by Nx, so it can accidentally be committed to the repository. ## Expected Behavior `.claude/settings.local.json` should be gitignored by default, similar to how `.claude/worktrees` is already handled. ## Changes - Added a migration that adds `.claude/settings.local.json` to existing workspaces' `.gitignore` - Updated all three `.gitignore` templates so new workspaces include it from the start - Follows the same pattern as the existing `add-claude-worktrees-to-git-ignore` migration
3 hours ago by Jason Jean
Succeeded
551
c8a285a2
3 hours ago by pull[bot]
Succeeded
master
35930fd0 fix(core): add .claude/settings.local.json to .gitignore (#34870) ## Current Behavior When configuring AI agents via `nx polygraph`, a `.claude/settings.local.json` file is created containing user-specific settings. This file is not gitignored by Nx, so it can accidentally be committed to the repository. ## Expected Behavior `.claude/settings.local.json` should be gitignored by default, similar to how `.claude/worktrees` is already handled. ## Changes - Added a migration that adds `.claude/settings.local.json` to existing workspaces' `.gitignore` - Updated all three `.gitignore` templates so new workspaces include it from the start - Follows the same pattern as the existing `add-claude-worktrees-to-git-ignore` migration
3 hours ago by Jason Jean
Succeeded
492
844eab1b
3 hours ago by pull[bot]
Succeeded
master
ded713ff Revert "fix(core): ensure postTasksExecution fires on SIGINT for continuous tasks (#34623)" (#34869) ## Current Behavior After #34623, when continuous tasks are killed (Ctrl+C), the nx process stays alive during async cleanup instead of exiting immediately. This causes the `RunningTasksService` SQLite entry to persist with a still-alive PID. When a new `nx` process starts during this cleanup window, `is_task_running()` finds the stale entry, confirms the PID is still alive (old process cleaning up), and creates a `SharedRunningTask` — incorrectly printing: ``` Waiting for @nrwl/ocean:local-registry in another nx process ``` The root cause: #34623 removed `process.exit()` from SIGINT handlers in `running-tasks.ts`, widening the window where the old process is alive but the task is no longer actually running. ## Expected Behavior After killing continuous tasks, a new `nx` invocation should not see stale "Waiting for ... in another nx process" messages. This reverts #34623 while a proper fix is designed that achieves both goals: reliable `postTasksExecution` firing AND prompt DB cleanup. ## Related Issue(s) Reverts #34623 --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
3 hours ago by Jason Jean
Succeeded
34815
Generating fix→
1866a14e chore(workspace): format remove-project-references spec Co-authored-by: barbados-clemens <barbados-clemens@users.noreply.github.com>
3 hours ago by nx-cloud[bot]
Succeeded
34872
Generating fix→
9d9e7b05 chore(misc): remove nx and nx-examples from update-all-repos target These repos are now updated via a different method.
3 hours ago by FrozenPandaz
Failed
34815
Fix applied→
9b65c7cc fix(workspace): remove entries with empty projects on project removal When removing a project clears all projects from a conformance rule or owners pattern, remove the entire entry rather than leaving an empty projects array. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
4 hours ago by Caleb Ukle
Canceled
34872
205d6061 chore(core): update nx to 22.6.0-rc.0
4 hours ago by FrozenPandaz
Succeeded
109
4f10c52f
4 hours ago by pull[bot]
Succeeded
master
35930fd0 fix(core): add .claude/settings.local.json to .gitignore (#34870) ## Current Behavior When configuring AI agents via `nx polygraph`, a `.claude/settings.local.json` file is created containing user-specific settings. This file is not gitignored by Nx, so it can accidentally be committed to the repository. ## Expected Behavior `.claude/settings.local.json` should be gitignored by default, similar to how `.claude/worktrees` is already handled. ## Changes - Added a migration that adds `.claude/settings.local.json` to existing workspaces' `.gitignore` - Updated all three `.gitignore` templates so new workspaces include it from the start - Follows the same pattern as the existing `add-claude-worktrees-to-git-ignore` migration
4 hours ago by Jason Jean
Succeeded
master
35930fd0 fix(core): add .claude/settings.local.json to .gitignore (#34870) ## Current Behavior When configuring AI agents via `nx polygraph`, a `.claude/settings.local.json` file is created containing user-specific settings. This file is not gitignored by Nx, so it can accidentally be committed to the repository. ## Expected Behavior `.claude/settings.local.json` should be gitignored by default, similar to how `.claude/worktrees` is already handled. ## Changes - Added a migration that adds `.claude/settings.local.json` to existing workspaces' `.gitignore` - Updated all three `.gitignore` templates so new workspaces include it from the start - Follows the same pattern as the existing `add-claude-worktrees-to-git-ignore` migration
4 hours ago by Jason Jean
Succeeded
847
e4af0e58
4 hours ago by pull[bot]
Succeeded
34685
92f6ec9f fix(docs): update devkit link in nx-vs-turborepo doc Co-authored-by: barbados-clemens <barbados-clemens@users.noreply.github.com>
4 hours ago by nx-cloud[bot]