Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Succeeded
22.2.1
8df9d500 chore(misc): fix release script to check GITHUB_ACTIONS not NODE_AUTH_TOKEN (#33824) The check should be for `GITHUB_ACTIONS` since that is the intention. The token may not be set due to Trusted Publisher flow. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
13 hours ago by FrozenPandaz
Succeeded
22.2.1
8df9d500 chore(misc): fix release script to check GITHUB_ACTIONS not NODE_AUTH_TOKEN (#33824) The check should be for `GITHUB_ACTIONS` since that is the intention. The token may not be set due to Trusted Publisher flow. --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
13 hours ago by FrozenPandaz
Succeeded
22.2.1
c4af6734 docs(misc): add nx-mcp reference page (#33767) fixes: DOC-341 https://deploy-preview-33767--nx-docs.netlify.app/docs/reference/nx-mcp --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: barbados-clemens <barbados-clemens@users.noreply.github.com>
1 day ago by jaysoo
Succeeded
22.2.1
c4af6734 fix(repo): revert to older nightly Rust for WASM builds (#33797) ## Current Behavior The nightly-2025-12-10 Rust version removed `mtim()` from the WASI `MetadataExt` trait, causing the WASM build to fail with: ``` error[E0599]: no method named `mtim` found for reference `&std::fs::Metadata` in the current scope ``` ## Expected Behavior WASM builds should compile successfully. ## Solution Revert to `nightly-2025-05-09` which still has the `mtim()` API available in the WASI `MetadataExt` trait.
1 day ago by FrozenPandaz
Succeeded
22.2.1
c4af6734 docs(misc): add nx-mcp reference page (#33767) fixes: DOC-341 https://deploy-preview-33767--nx-docs.netlify.app/docs/reference/nx-mcp --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: barbados-clemens <barbados-clemens@users.noreply.github.com>
1 day ago by FrozenPandaz
Failed
22.2.1
c4af6734 docs(misc): add nx-mcp reference page (#33767) fixes: DOC-341 https://deploy-preview-33767--nx-docs.netlify.app/docs/reference/nx-mcp --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: barbados-clemens <barbados-clemens@users.noreply.github.com>
1 day ago by FrozenPandaz
Failed
22.2.1
c4af6734 docs(misc): add nx-mcp reference page (#33767) fixes: DOC-341 https://deploy-preview-33767--nx-docs.netlify.app/docs/reference/nx-mcp --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: barbados-clemens <barbados-clemens@users.noreply.github.com>
1 day ago by FrozenPandaz
Succeeded
22.2.1
4147b62a fix(repo): revert to older nightly Rust for WASM builds (#33797) ## Current Behavior The nightly-2025-12-10 Rust version removed `mtim()` from the WASI `MetadataExt` trait, causing the WASM build to fail with: ``` error[E0599]: no method named `mtim` found for reference `&std::fs::Metadata` in the current scope ``` ## Expected Behavior WASM builds should compile successfully. ## Solution Revert to `nightly-2025-05-09` which still has the `mtim()` API available in the WASI `MetadataExt` trait.
1 day ago by FrozenPandaz
Succeeded
22.2.1
6cdbeb6e fix(repo): use RUSTUP_TOOLCHAIN env var for WASM builds (#33794) ## Current Behavior The `build:wasm` script uses `rustup override set nightly-2025-12-10` to set the Rust toolchain. However, when mise is configured to manage Rust (e.g., `rust = "1.90.0"` in `mise.toml`), it sets the `RUSTUP_TOOLCHAIN` environment variable which has higher precedence than directory overrides. This causes the WASM build to fail with: ``` error[E0554]: `#![feature]` may not be used on the stable release channel ``` ## Expected Behavior WASM builds should use nightly Rust regardless of mise configuration. ## Solution Set `RUSTUP_TOOLCHAIN=nightly-2025-12-10` directly in the script, which overrides any existing env var from mise or other sources.
1 day ago by FrozenPandaz
Succeeded
22.2.1
0d7ecb93 fix(repo): install nightly Rust for WASM build in publish workflow (#33792) ## Current Behavior After the mise migration (#33772), the `publish.yml` workflow fails during the "Build Wasm" step with: ``` error[E0554]: `#![feature]` may not be used on the stable release channel --> packages/nx/src/lib.rs:2:33 | 2 | #![cfg_attr(target_os = "wasi", feature(wasi_ext))] ``` The WASM build requires nightly Rust because it uses the unstable `wasi_ext` feature. The `build:wasm` script attempts to switch to nightly via `rustup override set`, but after the mise migration, the nightly toolchain is no longer pre-installed, causing the build to fail with the stable compiler. ## Expected Behavior The WASM build should successfully compile using nightly Rust with the `wasi_ext` feature. ## Related Issue(s) Fixes the publish workflow regression introduced in #33772
1 day ago by FrozenPandaz
Succeeded
22.2.1
33c3adaa fix(repo): restore mise tools in e2e-matrix workflow (#33785) ## Current Behavior The inline `mise_toml` config in `e2e-matrix.yml` was overwriting the entire `mise.toml` file, causing rust, dotnet, bun, and java to NOT be installed by mise. This resulted in slow package installs as these tools were downloaded during `pnpm install` instead. ## Expected Behavior All tools from `mise.toml` (rust, dotnet, bun, java) should be installed by mise, with only the node version varying based on the matrix. ## Solution Use mise's template syntax to make node version configurable via `NODE_VERSION` env var while preserving all other tools from `mise.toml`: ```toml node = "{{ env['NODE_VERSION'] | default(value='24') }}" ``` Then in the workflow, set the env var instead of overriding the entire config: ```yaml - name: Setup dev tools with mise uses: jdx/mise-action@v3 env: NODE_VERSION: ${{ matrix.node_version }} ``` ## Related Issue(s) Fixes slow install times in nightly e2e-matrix workflow after #33772.
1 day ago by FrozenPandaz
Succeeded
22.2.1
e4b9e582 fix(core): fix record stat on initial CNW call (#33783) This PR fixes an issue with CNW where the initial `recordStat` call is not working due to a logic error on passing `directory` that isn't initialized yet.
1 day ago by FrozenPandaz