Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
35851
1ff12679 feat(angular): drop support for Angular v19 (#35844) ## Current Behavior `@nx/angular` supports Angular 19, 20, and 21. ## Expected Behavior Drops support for Angular 19; the minimum supported version is now 20. Removes the Angular 19 version mappings, compatibility branches, SSR templates, and the v19-only `serverRouting` option. > [!NOTE] > Part of the Angular v22 upgrade. This targets the `angular-v22` integration branch rather than `master`.  --- [View session information ↗](https://snapshot.app.trypolygraph.com/orgs/69cdc268b6aa527e4129c2b4/sessions/angular-v22.0.0-rc.2-5a2c66d4)  --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
by Leosvel Pé...
Succeeded
master
00270b55 fix(js): handle already-published version errors in release-publish executor (#35782) ## Current Behavior When using `nx release publish` with pnpm (or other package managers), if a package version has already been published to the registry, the executor fails with an error instead of gracefully handling it. ## Expected Behavior The release-publish executor should detect "already published" errors (E403 with 'previously published versions', EPUBLISHCONFLICT, E409 conflicts) and skip the publish gracefully with a warning, rather than failing the entire release process. ## Related Issue(s) Closes #35235
by Olawuni Ol...
Succeeded
662
24c5455c fix(schematics): check touchedFile path against the project files fix(schematics): Extend test for new resolving of touchedFiles fix tests for touchedProjects fix typo fix(schematics): check touchedFile path against the project files fix(schematics): Extend test for new resolving of touchedFiles fix tests for touchedProjects fix typo
by Mitko Tsch...
Failed
35851
Flaky task→
1ff12679 feat(angular): drop support for Angular v19 (#35844) ## Current Behavior `@nx/angular` supports Angular 19, 20, and 21. ## Expected Behavior Drops support for Angular 19; the minimum supported version is now 20. Removes the Angular 19 version mappings, compatibility branches, SSR templates, and the v19-only `serverRouting` option. > [!NOTE] > Part of the Angular v22 upgrade. This targets the `angular-v22` integration branch rather than `master`.  --- [View session information ↗](https://snapshot.app.trypolygraph.com/orgs/69cdc268b6aa527e4129c2b4/sessions/angular-v22.0.0-rc.2-5a2c66d4)  --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
by Leosvel Pé...
Succeeded
757
bd615619 feat(builders): add runInBand and maxWorkers options to jest
by Jason Jean
Succeeded
master
9f20267e fix(vite): enforce multi-version support windows for @nx/vite and @nx/vitest (#35671) ## Current Behavior `@nx/vite` and `@nx/vitest` don't consistently honor their supported version windows. Cross-major `packageJsonUpdates` and version-specific migrations run on workspaces outside their target range, generators can overwrite pinned third-party versions, and unsupported versions silently fall through to the latest install constants instead of erroring. ## Expected Behavior Both plugins enforce their support windows. Cross-major migrations declare source-major `requires` gates so they only run where they apply, generators throw a clear below-floor error and preserve pinned versions (`keepExistingVersions` defaults to `true`), and peer ranges and version maps match what each plugin actually supports. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: FrozenPandaz <jasonjean1993@gmail.com>
by Leosvel Pé...
Succeeded
1358
0f4740b4 fix(nx): run migrations for beta versions
by Jason Jean
Succeeded
master
1c948000 feat(core): avoid redundant rematch in findMatchingConfigFiles (#35793) ## Current Behavior `findMatchingConfigFiles` still rematches every candidate file against the plugin glob even though `multiGlobWithWorkspaceContext` already returned the file list for that exact glob. The previous branch revision only precompiled the minimatch pattern, which reduced some overhead but still kept the redundant rematch in the hot path. ## Expected Behavior Once `projectFiles` already comes from `multiGlobWithWorkspaceContext` for a plugin's `createNodes` pattern, `findMatchingConfigFiles` should only apply include/exclude filtering and should not rematch against the same glob again. This change removes the redundant rematch entirely and updates the unit tests to reflect the actual contract of `findMatchingConfigFiles`: it operates on a pre-matched file list plus include/exclude filters. Benchmark and reproduction evidence: - Repro issue: https://github.com/nrwl/nx/issues/35792 - Public repro repo: https://github.com/cw-alexcroteau/nx-find-matching-config-files-repro-20260525 - Successful cross-platform perf summary: https://github.com/cw-alexcroteau/nx-find-matching-config-files-repro-20260525/actions/runs/26409870118/attempts/1#summary-77741892587 ## Related Issue(s) Fixes #35792 --------- Co-authored-by: Craigory Coppola <craigorycoppola@gmail.com>
by Alex Croteau
Succeeded
35830
008ce26f fix(core): gate nx migrate first-party/third-party modes to Nx v23+ targets The first-party/third-party `nx migrate` modes rely on migration metadata that only exists in Nx v23+. Running them against pre-v23 targets produces incorrect results, so gate them: - `first-party` is offered/accepted only when migrating from Nx v22+ into a v23+ target; `third-party` only when the workspace is already on v23+. - The target version (including `latest`/dist-tags) is resolved before the mode is decided so the gate reads a concrete major. - A bare `nx migrate` on a pre-v22 install again requires an explicit target instead of defaulting to `latest`. - The multi-major prompt no longer offers a v22.x step, so a selected mode can't be invalidated by a redirect below v23. When the functionality isn't available, `nx migrate` falls back to migrating all packages, matching prior behavior.
by Leosvel Pé...
Failed
master
1c948000 feat(core): avoid redundant rematch in findMatchingConfigFiles (#35793) ## Current Behavior `findMatchingConfigFiles` still rematches every candidate file against the plugin glob even though `multiGlobWithWorkspaceContext` already returned the file list for that exact glob. The previous branch revision only precompiled the minimatch pattern, which reduced some overhead but still kept the redundant rematch in the hot path. ## Expected Behavior Once `projectFiles` already comes from `multiGlobWithWorkspaceContext` for a plugin's `createNodes` pattern, `findMatchingConfigFiles` should only apply include/exclude filtering and should not rematch against the same glob again. This change removes the redundant rematch entirely and updates the unit tests to reflect the actual contract of `findMatchingConfigFiles`: it operates on a pre-matched file list plus include/exclude filters. Benchmark and reproduction evidence: - Repro issue: https://github.com/nrwl/nx/issues/35792 - Public repro repo: https://github.com/cw-alexcroteau/nx-find-matching-config-files-repro-20260525 - Successful cross-platform perf summary: https://github.com/cw-alexcroteau/nx-find-matching-config-files-repro-20260525/actions/runs/26409870118/attempts/1#summary-77741892587 ## Related Issue(s) Fixes #35792 --------- Co-authored-by: Craigory Coppola <craigorycoppola@gmail.com>
by Alex Croteau
Succeeded
35386
14154ab7 chore(repo): update @monodon/rust to 3.0.0
by Craigory C...
Succeeded
35863
d3676648 feat(core): suggest available targets and closest task id on run-one errors [Self-Healing CI Rerun]
by nx-cloud[bot]
Succeeded
master
1c948000 feat(core): avoid redundant rematch in findMatchingConfigFiles (#35793) ## Current Behavior `findMatchingConfigFiles` still rematches every candidate file against the plugin glob even though `multiGlobWithWorkspaceContext` already returned the file list for that exact glob. The previous branch revision only precompiled the minimatch pattern, which reduced some overhead but still kept the redundant rematch in the hot path. ## Expected Behavior Once `projectFiles` already comes from `multiGlobWithWorkspaceContext` for a plugin's `createNodes` pattern, `findMatchingConfigFiles` should only apply include/exclude filtering and should not rematch against the same glob again. This change removes the redundant rematch entirely and updates the unit tests to reflect the actual contract of `findMatchingConfigFiles`: it operates on a pre-matched file list plus include/exclude filters. Benchmark and reproduction evidence: - Repro issue: https://github.com/nrwl/nx/issues/35792 - Public repro repo: https://github.com/cw-alexcroteau/nx-find-matching-config-files-repro-20260525 - Successful cross-platform perf summary: https://github.com/cw-alexcroteau/nx-find-matching-config-files-repro-20260525/actions/runs/26409870118/attempts/1#summary-77741892587 ## Related Issue(s) Fixes #35792 --------- Co-authored-by: Craigory Coppola <craigorycoppola@gmail.com>
by Alex Croteau
Succeeded
667
9965cabb fix(schematics): library schematic properly removes extra files Angular CLI now supports `host.delete()`. `updateProject()` now properly removes the library generated service and component files. > Earlier workarounds using `unlink()` were not working. Refs #650.
by Thomas Bur...
Succeeded
master
1c948000 feat(core): avoid redundant rematch in findMatchingConfigFiles (#35793) ## Current Behavior `findMatchingConfigFiles` still rematches every candidate file against the plugin glob even though `multiGlobWithWorkspaceContext` already returned the file list for that exact glob. The previous branch revision only precompiled the minimatch pattern, which reduced some overhead but still kept the redundant rematch in the hot path. ## Expected Behavior Once `projectFiles` already comes from `multiGlobWithWorkspaceContext` for a plugin's `createNodes` pattern, `findMatchingConfigFiles` should only apply include/exclude filtering and should not rematch against the same glob again. This change removes the redundant rematch entirely and updates the unit tests to reflect the actual contract of `findMatchingConfigFiles`: it operates on a pre-matched file list plus include/exclude filters. Benchmark and reproduction evidence: - Repro issue: https://github.com/nrwl/nx/issues/35792 - Public repro repo: https://github.com/cw-alexcroteau/nx-find-matching-config-files-repro-20260525 - Successful cross-platform perf summary: https://github.com/cw-alexcroteau/nx-find-matching-config-files-repro-20260525/actions/runs/26409870118/attempts/1#summary-77741892587 ## Related Issue(s) Fixes #35792 --------- Co-authored-by: Craigory Coppola <craigorycoppola@gmail.com>
by Alex Croteau
Failed
710
3791f258
by pull[bot]
Canceled
master
9f20267e fix(vite): enforce multi-version support windows for @nx/vite and @nx/vitest (#35671) ## Current Behavior `@nx/vite` and `@nx/vitest` don't consistently honor their supported version windows. Cross-major `packageJsonUpdates` and version-specific migrations run on workspaces outside their target range, generators can overwrite pinned third-party versions, and unsupported versions silently fall through to the latest install constants instead of erroring. ## Expected Behavior Both plugins enforce their support windows. Cross-major migrations declare source-major `requires` gates so they only run where they apply, generators throw a clear below-floor error and preserve pinned versions (`keepExistingVersions` defaults to `true`), and peer ranges and version maps match what each plugin actually supports. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: FrozenPandaz <jasonjean1993@gmail.com>
by Leosvel Pé...
Succeeded
1357
8b8addd2 chore(readme): add connect banner
by ben
Succeeded
master
98e9643a docs(nx-cloud): add platform pages for Nx Cloud add-ons (#35857) ## Current Behavior Resource usage and sandboxing docs lived under guides; there were no pages for the dedicated compute cluster, Docker layer caching, or the Docker/npm read-through caches. ## Expected Behavior Six consolidated platform-feature pages under `features/ci-features`, grouped in a new "Nx Cloud add-ons" sidebar section (Resource usage, Sandboxing, Dedicated compute cluster, Docker layer caching, Docker read-through cache, npm read-through cache). Resource usage moved out of guides with a redirect, and the launch-templates DinD note now points to the dedicated compute cluster instead of being enterprise-only. ## Previews: - https://deploy-preview-35857--nx-docs.netlify.app/docs/features/ci-features/resource-usage - https://deploy-preview-35857--nx-docs.netlify.app/docs/features/ci-features/dedicated-compute-cluster - https://deploy-preview-35857--nx-docs.netlify.app/docs/features/ci-features/sandboxing - https://deploy-preview-35857--nx-docs.netlify.app/docs/features/ci-features/docker-layer-caching - https://deploy-preview-35857--nx-docs.netlify.app/docs/features/ci-features/docker-read-through-cache - https://deploy-preview-35857--nx-docs.netlify.app/docs/features/ci-features/npm-read-through-cache - https://deploy-preview-35857--nx-docs.netlify.app/docs/reference/nx-cloud/launch-templates#launch-templatestemplate-nameimage  --- [View session information ↗](https://snapshot.app.trypolygraph.com/orgs/69cdc268b6aa527e4129c2b4/sessions/docs-sandbox-resource-usage-f431c8fc)  --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: jaysoo <jaysoo@users.noreply.github.com>
by Jack Hsu
Succeeded
756
8f768e8b
by pull[bot]