Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
22.4.x
37522911 fix(core): use --lockfile-only for Bun updateLockFile (#34375) ## Current Behavior The Bun package manager config uses `--frozen-lockfile` for `updateLockFile`: ```typescript updateLockFile: 'bun install --frozen-lockfile', ``` However, `--frozen-lockfile` **prevents** changes to the lockfile, causing `nx release` to fail when trying to update the lockfile after version bumps. ## Expected Behavior Use `--lockfile-only` which generates/updates the lockfile without installing dependencies: ```typescript updateLockFile: 'bun install --lockfile-only', ``` This is consistent with other package managers: - npm: `npm install --package-lock-only` - pnpm: `pnpm install --lockfile-only` - yarn berry: `yarn install --mode update-lockfile` ## Background When Bun support was added in PR #22602 (April 2024), `--lockfile-only` didn't exist in Bun. Bun has since added this flag. Closes #34344 Co-authored-by: Kai Gritun <kai@kaigritun.com> (cherry picked from commit f1873b27a8cdd0c230b28343b8c77cbb22713555)
1 month ago by kaigritun
Failed
22.4.x
3bcb3c8b feat(js): update swc/cli to 0.8.0 (#34365) Update `@swc/cli` to 0.8.0 which uses chokidar v5
1 month ago by Coly010
Failed
22.4.x
3bcb3c8b feat(js): update swc/cli to 0.8.0 (#34365) Update `@swc/cli` to 0.8.0 which uses chokidar v5
1 month ago by Coly010
Canceled
22.4.x
3bcb3c8b feat(js): update swc/cli to 0.8.0 (#34365) Update `@swc/cli` to 0.8.0 which uses chokidar v5
1 month ago by Coly010
Failed
22.4.x
d460e867 chore(repo): re-enable gradle e2e tests (#34357)      ## Current Behavior  ## Expected Behavior  Re-enabling tests and putting back kotlin e2e tests for gradle. ## Related Issue(s)  Fixes # (cherry picked from commit 693f75149aa2f4b6448226422dc2a2ef134905ca)
1 month ago by lourw
Failed
22.4.x
db477657 fix(nx-dev): include nx cli examples on refs page (#34367) ![wm_2026-02-06T11-26-54@2x](https://github.com/user-attachments/assets/c2814268-e921-420b-a9e2-2b90c8a89526) https://deploy-preview-34367--nx-docs.netlify.app/docs/reference/nx-commands#nx-add cli examples are included in the generated page now fixes: DOC-402 (cherry picked from commit 359c7fbf4e4c937e3a0e020b3eab5010e63db579)
1 month ago by barbados-c...
Failed
22.4.x
182d28c3 docs(misc): reduce memory footprint of nx-dev build (#34258) We're showing over 8 GB of memory usage on Netlify, and 11+ GB on Agents. Let's test out a few ways to reduce the memory footprint. --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2 months ago by jaysoo
Canceled
22.4.x
59e3f3c8 docs(nx-dev): update Nx Cloud & Home features, add new components (#34149)
2 months ago by bcabanes
Succeeded
22.4.x
43a34d0b fix(core): prevent command injection in getNpmPackageVersion (#34309) ## Current Behavior The `getNpmPackageVersion` function in `packages/workspace/src/generators/utils/get-npm-package-version.ts` uses `execSync` with direct string interpolation of the `packageName` parameter. When a user runs `create-nx-workspace` with a custom `--preset` value that doesn't match a known preset, the value flows unsanitized into a shell command: ```js execSync(`npm view ${packageName}... version --json`) ``` This allows arbitrary command execution via shell metacharacters (e.g., `--preset='pkg$(malicious command)'`). ## Expected Behavior User-supplied package names are validated against a strict npm package name regex before being passed to any shell command. The function now uses `execFileSync` with an args array instead of `execSync` with string interpolation, providing defense in depth: 1. **Input validation** — rejects anything that isn't a valid npm package name 2. **Safe execution** — arguments are passed as an array so Node.js handles escaping, rather than concatenating into a raw shell string (cherry picked from commit 79d878f24041a680fa103eb1b346bab72b8e88d0)
2 months ago by FrozenPandaz
Failed
22.4.x
0848679f fix(maven): include pom.xml and ancestor pom files as inputs for all targets (#34291) ## Current Behavior - `pom.xml` is only included as an input when a mojo uses default inputs - Mojos with specific input configurations (like `maven-compiler-plugin:compile`) don't get `pom.xml` in their inputs - Parent `pom.xml` files aren't tracked as inputs This can lead to stale cache hits when: 1. `pom.xml` changes but a mojo has specific input config 2. A parent `pom.xml` changes (affecting inherited properties, dependency versions, plugin config) ## Expected Behavior - Every target should include its own `pom.xml` as an input - Every target should include ancestor `pom.xml` files (within the workspace) as inputs - Cache should invalidate when any relevant `pom.xml` changes ## Related Issue(s) N/A - discovered during code review ## Changes - **CacheConfig.kt**: Removed `pom.xml` from `defaultInputs` (now always added explicitly) - **MojoAnalyzer.kt**: Added `workspaceRoot` parameter and logic to walk up the parent chain, adding all in-workspace ancestor `pom.xml` files as inputs - **NxProjectAnalyzerMojo.kt**: Pass `workspaceRoot` to `MojoAnalyzer` (cherry picked from commit 3f6bdc7ff7acd4bb14e18e197ef4b19d59e5a02a)
2 months ago by FrozenPandaz
Failed
22.4.x
d0f7a77f docs(nx-dev): add autonomous AI workflows blog post Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> (cherry picked from commit 01d2f64b900bf076e2b8fb6ed88556b15f739ca5)
2 months ago by juristr
Failed
22.4.x
9073f40e docs(misc): update the docs to use more direct language (#34264)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
2 months ago by vsavkin
Succeeded
22.4.x
cd97ff7a fix(vite): handle sophisticated vite plugins (#34242) ## Current Behavior With Vite now providing additional options (environments etc) for framework authors, vite.config files can be much more simple for the user. However, this often assumes that the `root` property will be set and provided during `Vite CLI` invocation. When we run `resolveConfig` to determine inputs and outputs, we do not set this `root` and expect the user to have it in their vite config file. For some plugins/frameworks such as Tanstack Start - this causes the plugin to error. The `isBuildable` conditions is also not inclusive enough and can skip projects that should be marked as buildable. ## Expected Behavior Ensure that sophisticated vite plugins are supported with Nx ## Related Issue(s) CLOSES NXC-3637 (cherry picked from commit 3d62c8b5c13501cac418e3c483d2d71ea3123d3e)
2 months ago by Coly010
Succeeded
22.4.x
b6cb5cca feat(core): add variant 2 to CNW cloud prompts with promo message (#34223) This PR uses three variants for CNW for prompting for Cloud/platform connection. - Variant 0: Shows "Try the full Nx platform?" prompt → platform-setup completion - Variant 1: Shows "Would you like remote caching..." prompt → cache-setup completion - Variant 2: No prompt → platform-promo completion with "Want faster builds?" Both template and custom flows use the same messages and prompts. ### Skip (all) -- No changes <img width="1392" height="994" alt="cnw_all_skip_completion" src="https://github.com/user-attachments/assets/1579df01-fc36-4324-bc74-19efc18f78af" /> ### Variant 0 (full platform) Template prompt: <img width="1392" height="994" alt="cnw_template_variant_0_prompt" src="https://github.com/user-attachments/assets/d02e9ddc-fd25-4f6f-ac61-6f6d518fe338" /> Template completion: <img width="1392" height="994" alt="cnw_template_variant_0_completion" src="https://github.com/user-attachments/assets/12e459a0-962c-4724-82fa-a4f5a3b6fbd8" /> Custom prompt: <img width="1392" height="994" alt="cnw_custom_variant_0_prompt" src="https://github.com/user-attachments/assets/8143832a-a85e-43b4-81eb-15074c223476" /> Custom completion: <img width="1392" height="994" alt="cnw_custom_variant_0_completion" src="https://github.com/user-attachments/assets/036ef6f9-4977-459a-bbd2-502670a12d01" /> ### Variant 1 (remote cache) Template prompt: <img width="1392" height="994" alt="cnw_template_variant_1_prompt" src="https://github.com/user-attachments/assets/f69b540f-7e48-46ae-99e5-f53657176424" /> Template completion: <img width="1392" height="994" alt="cnw_template_variant_1_completion" src="https://github.com/user-attachments/assets/04c17847-b0f2-4e37-b7d2-5556aa14f510" /> Custom prompt: <img width="1392" height="994" alt="cnw_custom_variant_1_prompt" src="https://github.com/user-attachments/assets/abdb38b2-611e-458b-85c0-7b89cd1b827e" /> Custom completion: <img width="1348" height="950" alt="cnw_custom_variant_1_completion" src="https://github.com/user-attachments/assets/e7d35ddb-e8ac-4ad1-889e-9fff89538900" /> ## Variant 2 (no prompt) Template completion: <img width="1392" height="994" alt="cnw_template_variant_2_completion" src="https://github.com/user-attachments/assets/07050989-a56c-46eb-a0c3-8730916856ff" /> Custom completion: <img width="1392" height="994" alt="cnw_custom_variant_2_completion" src="https://github.com/user-attachments/assets/94000828-37b2-4059-a13b-0d36972cfd3e" /> ## Related Issue(s) Closes CLOUD-4189 Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2 months ago by jaysoo
Canceled
22.4.x
1dad3049 Revert "Revert "feat(core): add A/B testing variant 1 to skip cloud p…rompt in CNW (#34106)" (#34191) (#34204) This reverts commit f0166645573fa519acb127c74e4f9edc08197562. (cherry picked from commit e108dac1bb34d081389479380d7c30b5e64f0a49)
2 months ago by jaysoo