Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

In progress
35441
ad6f4415 chore(repo): default fs-trace on so CI captures data without env wiring Inverts the gate to opt-out (NX_FS_TRACE_FOREIGN_READS=0 disables) so the diagnostic runs unconditionally on the next CI build regardless of whether the target's `env` config reaches the test process.
by Craigory C...
Canceled
35441
ad6f4415 chore(repo): default fs-trace on so CI captures data without env wiring Inverts the gate to opt-out (NX_FS_TRACE_FOREIGN_READS=0 disables) so the diagnostic runs unconditionally on the next CI build regardless of whether the target's `env` config reaches the test process.
by Craigory C...
Succeeded
master
f89e71df fix(nx-dev): document nested CLI subcommands beyond two levels (#35519) ## Current Behavior The CLI docs generator that produces `/docs/reference/nx-commands` only flattens the top-level command and its direct children. Any subcommand nested deeper than that is silently dropped from the rendered page, even though the underlying yargs parser already produces the full nested tree. In practice this means commands like `nx show target inputs` and `nx show target outputs` have no public docs entry — users have no way to discover their flags (`--check`, `--target`, `--configuration`, etc.) without running `--help` locally. ## Expected Behavior The generator walks the full subcommand tree and renders every command. Three-deep commands like `nx show target inputs` appear as `###` headings alongside `nx show target`, with their own usage block and options table. Verified locally — running the generator before/after this change adds exactly two new sections (`nx show target inputs`, `nx show target outputs`) and changes nothing else. A new e2e test in `astro-docs/e2e/cli-subcommand-formatting.spec.ts` locks the third-level rendering in so this can't regress silently again. ## Related Issue(s) Fixes #
by Craigory C...
Succeeded
35519
7aaee972 fix(nx-dev): document nested CLI subcommands beyond two levels The CLI docs generator only flattened the top-level command and its direct children, silently dropping any deeper subcommands such as `nx show target inputs` and `nx show target outputs`. The yargs parser already produced the full nested tree — only the consumer was capped. - Replace the two-loop flatten with a recursive walk in `flattenCommands` so every depth is rendered. - Add an e2e test covering `nx show target inputs/outputs` to lock in the third-level rendering at h3 with proper usage blocks.
by Craigory C...
Failed
35340
0e4fcbeb feat(core): target-defaults filtering with array shape Squashed for rebase. Combines: - array-shape targetDefaults with executor as filter/injector - legacy record-shape deprecation warning - e2e/migration call site updates for the new union shape
by Craigory C...
Succeeded
master
2a412a3a chore(repo): declare lazy-loaded packages as implicit deps (#35392) ## Current Behavior Many Nx plugin packages lazy-load other plugins at runtime via `ensurePackage()` or the `require('@nx' + '/...')` pattern. These dependencies weren't declared in `package.json` at all, which meant: - `pnpm install` in the monorepo happened to find them only via hoisting from unrelated `devDependencies`. - Published packages gave no install-time signal about what optional peers a consumer might want. - The dependencies were invisible to dependency-graph tooling, supply-chain audits, and any future semantic-versioning logic. ## Expected Behavior Every lazy-loaded plugin or tool is declared as `peerDependencies` + `peerDependenciesMeta: { X: { optional: true } }`, matching the existing convention in `@nx/angular`, `@nx/angular-rspack`, `@nx/eslint`, etc. This gives consumers correct install/publish semantics without requiring them to install peers they don't use. For two packages — `@nx/workspace` and `@nx/js` — several of their newly-declared peers transitively reverse-depend on them. Raw package.json edges would cause `@nx/js:typescript-sync` to produce circular TypeScript project references (TS6202). Those two packages use `implicitDependencies: ["!name", …]` in `project.json` to drop the cyclic graph edges, keeping the task graph and tsc builds cycle-free without modifying the sync generator itself. Commits: 1. **workspace + js**: 14 optional peers on `@nx/workspace`, 5 on `@nx/js`, plus `implicitDependencies` negations in each `project.json`. 2. **Plugin packages**: `@nx/angular`, `@nx/expo`, `@nx/next`, `@nx/nuxt`, `@nx/react-native`, `@nx/storybook`, `@nx/vite`, `@nx/vue`, `@nx/web`. Cycles don't form for any of these, so no `implicitDependencies` negations were needed. `@nx/js:typescript-sync` populated the corresponding `tsconfig.lib.json` project references, which are committed alongside the `package.json` changes. ## Related Issue(s) Fixes # ## Test plan see: https://staging.nx.app/runs/m3Otv2Xl7m?sandboxViolations=true&query=%3Atest --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com>
by Craigory C...
Succeeded
35392
5e620c1c chore(rspack): drop vestigial build-base dependsOn override The hardcoded `build-base.dependsOn` and `nx-release-publish: {dependsOn: []}` override was added when this branch had @nx/rspack declaring node/cypress/docker/eslint as real package.json deps, which formed cycles in the task graph. After reverting rspack/package.json to master, rspack's only graph edges are devkit/js/module-federation/nest/web — none cycle back to rspack — so `^build-base` from the targetDefault is sufficient and the override forces unnecessary task ordering. Verified via `nx run rspack:build-base --graph`: 38-task plan, acyclic, still pulls cypress/docker/eslint/node transitively through nest -> node.
by Craigory C...
Succeeded
available-parcel
44af455f chore(repo): prune redundant implicitDependencies, bump bust Drop implicit edges that don't change resolved test inputs (verified via `nx show target inputs <p>:test` — byte-identical before/after across the 8 touched projects). The same source files for cypress, docker, eslint, node, module-federation, playwright still arrive via paths through `workspace`'s implicit list and `node`'s kept edges, so sandbox coverage is unchanged. Drops: - angular-rspack: nx (covered via devkit -> nx) - create-nx-plugin: nx, angular (no source / spec evidence) - create-nx-workspace: nx (covered transitively) - express: nx (covered via devkit -> nx) - module-federation: cypress, eslint - node: cypress, module-federation, playwright - rspack: cypress, docker, eslint, node Restored: - plugin: vitest (contract coupling — generator emits @nx/vitest:test executor and the spec asserts against that string) Bump bust to invalidate caches for fresh sandbox-report run.
by Craigory C...
Failed
master
6efd33f0 fix(core): skip target-defaults synthesis when defaults are incompatible with the specified target (#35486) When a `targetDefaults` entry keyed by target name carries an executor that differs from an inferred (specified-plugin) target's executor, the synthetic plugin built by `createTargetDefaultsResults` would be merged on top of the specified target. The downstream "incompatible executor" branch in `mergeTargetConfigurations` then dropped the specified target's options/configurations and let the synthetic's executor win, silently replacing the inferred command with the unrelated default executor. Skip synthesis in the specified-only branch when the resolved default is incompatible with the specified target. The default was authored for a different executor and shouldn't apply. Surfaces in polyglot workspaces — e.g. a `targetDefaults['test-native']` configured for `@monodon/rust:test` was overriding a dotnet plugin's inferred `test-native` (`command: 'dotnet test'`), causing CI to run `cargo test` against C# projects.
by Craigory C...
Succeeded
master
3c88f372 fix(core): add provenance check in nx console status path (#35485) ## Current Behavior nx console's status check is missing a provenance check ## Expected Behavior provenance is validated before installing latest nx ## Related Issue(s)  Fixes #
by Craigory C...
Failed
35392
44af455f chore(repo): declare lazy-loaded packages as optional peers
by Craigory C...
Succeeded
35486
e9443481 fix(core): skip target-defaults synthesis when defaults are incompatible with specified target When a `targetDefaults` entry keyed by target name carries an executor that differs from an inferred (specified-plugin) target's executor, the synthetic plugin built by `createTargetDefaultsResults` would be merged on top of the specified target. The downstream "incompatible executor" branch in `mergeTargetConfigurations` then dropped the specified target's options/configurations and let the synthetic's executor win, silently replacing the inferred command with the unrelated default executor. Skip synthesis in the specified-only branch when the resolved default is incompatible with the specified target. The default was authored for a different executor and shouldn't apply. Surfaces in polyglot workspaces — e.g. a `targetDefaults['test-native']` configured for `@monodon/rust:test` was overriding a dotnet plugin's inferred `test-native` (`command: 'dotnet test'`), causing CI to run `cargo test` against C# projects.
by Craigory C...
Failed
35392
1a8c31e9 chore(repo): prune redundant implicitDependencies, bump bust Drop implicit edges that don't change resolved test inputs (verified via `nx show target inputs <p>:test` — byte-identical before/after across the 8 touched projects). The same source files for cypress, docker, eslint, node, module-federation, playwright still arrive via paths through `workspace`'s implicit list and `node`'s kept edges, so sandbox coverage is unchanged. Drops: - angular-rspack: nx (covered via devkit -> nx) - create-nx-plugin: nx, angular (no source / spec evidence) - create-nx-workspace: nx (covered transitively) - express: nx (covered via devkit -> nx) - module-federation: cypress, eslint - node: cypress, module-federation, playwright - rspack: cypress, docker, eslint, node Restored: - plugin: vitest (contract coupling — generator emits @nx/vitest:test executor and the spec asserts against that string) Bump bust to invalidate caches for fresh sandbox-report run.
by Craigory C...
Succeeded
35398
dcd7bb98 fix(dotnet): rename inferred test target to test:dotnet The plugin emitted `test-native` for parity with the rust test pipeline. Workspace `targetDefaults.test-native` keys an `@monodon/rust:test` executor; Nx's target-defaults synthesis (`createTargetDefaultsResults`) pulls that default in by target-name and the resulting synthetic target overrides the inferred dotnet target during the incompatible-executor merge — so `nx test-native` ran `cargo test -p MsbuildAnalyzer.Tests`, which Cargo rejects on the dot in the project name. Use a `:dotnet`-suffixed name (mirroring `build:dotnet`) so the inferred target no longer collides with the rust default. Wire the project's noop `test` to `test:dotnet` so the workspace `test` chain still triggers dotnet tests in CI.
by Craigory C...
Succeeded
35485
5805c5f3 fix(core): add provenance check in nx console status path
by Craigory C...
Failed
35398
Fix ready→
ccab18d8 fix(dotnet): widen dependent task output hashing and add editorconfig input - Broaden `dependentTasksOutputFiles` glob from `**/*.{dll,props,targets}` to `**/*` on build, test, pack, and publish so dep projects' `bin/`/`obj/` artifacts (`.deps.json`, `.runtimeconfig.json`, `.pdb`, `.dll.config`, `apphost`, `assets.cache`) participate in input hashing. - Add `{workspaceRoot}/.editorconfig` as an input on the same targets; dotnet build reads it for code-style enforcement.
by Craigory C...
Succeeded
master
64bf7674 chore(repo): include native dts header in build-native inputs (#35481)
by Craigory C...
Succeeded
35481
759a765e chore(repo): include native dts header in build-native inputs The `dts-header.d.ts` file added in #35251 is consumed by napi via the `dtsHeaderFile` config in packages/nx/package.json, but the `native` named input in nx.json only globbed `*.rs` and Cargo files. Changes to the header would not invalidate `build-native` (or the related `build-native-wasm`, `format-native`, `lint-native` targets that share the same input), producing stale `index.d.ts` outputs from cache.
by Craigory C...
Succeeded
master
8183ec2a fix(core): start TUI event reader synchronously in enter() to prevent stdin race (#35465) Since the napi v2→v3 migration (#34619) moved Tui::start() out of enter() and into an async block, there is a window between enable_raw_mode() and EventStream::new() during which bytes can sit in the kernel tty buffer and later be parsed as keypresses by the reader. Two known sources: 1. Tail bytes of the OSC 11 color-scheme reply that terminal-colorsaurus doesn't fully consume (the reply contains '/' separators, e.g. `\x1b]11;rgb:RRRR/GGGG/BBBB\x07`, which trigger filter mode and feed hex digits as filter text). 2. Leftover input from the analytics prompt (#34144, new in v22.6) that uses enquirer/raw-mode and may not drain stdin completely. Either path manifests as the TUI booting with a bogus filter pre-applied that hides every task. start() was moved out because tokio::spawn requires a Tokio runtime context, and the sync __init NAPI method runs on the JS main thread without one. Switching the inner spawn to napi::bindgen_prelude::spawn (which uses napi's static runtime and works from any thread — already used elsewhere for the same reason) lets enter() call start() synchronously again, so EventStream exists before enter() returns and consumes those bytes itself. https://claude.ai/code/session_01RwrzRzTCZ7k8Uzw2xux6kM Co-authored-by: Claude <noreply@anthropic.com>
by Craigory C...
Succeeded
35441
c00e8a31 chore(repo): guard native expandOutputs/getFilesForOutputsBatch from realRoot scans The `workspace-context` mock catches calls that go through `setupWorkspaceContext` / `getAllFileDataInContext`, but `tasks-runner/cache.ts` calls the native `expandOutputs(workspaceRoot, outputs)` directly — which drives `nx_walker` and walks every plugin's sources, surfacing as the same cross-project sandbox violation set. Same applies to `getFilesForOutputsBatch`. Wrap both functions to short-circuit to an empty result when the first arg is the real workspace root. TempFs callers continue to hit the real native implementation.
by Craigory C...