Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
36547
064e3db4 chore(devkit): satisfy lint for convert-to-inferred test helpers The real-resolution test helper imports the project.json default plugin and the workspace-context reset — both restricted imports, allowed here because the file is test-only and excluded from the published lib build. Disable the restricted-imports rule for those two lines (matching the existing createTreeWithEmptyWorkspace import) and drop an unused no-console directive in the benchmark. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Miroslav J...
Succeeded
36548
9bf5d966 fix(devkit): build internal testing utility subpaths
by Miroslav J...
Failed
36548
Environment issue→
9bf5d966 fix(devkit): build internal testing utility subpaths
by Miroslav J...
Succeeded
36547
9cf249ec fix(devkit): isolate inferred migrator option sets
by Miroslav J...
Failed
36547
Flaky task→
9cf249ec fix(devkit): isolate inferred migrator option sets
by Miroslav J...
Succeeded
36548
226594d9 fix(testing): stabilize flaky e2e ci tasks
by Miroslav J...
Succeeded
36547
5d306183 cleanup(devkit): correct stale migrator comments and honest option-set typing Comment fixes: writeResiduals and runVerificationPass carried series-development scaffolding ('until centralization lands', 'added in a later task') describing a state that never ships; inferOncePerOptionSet JSDoc said stripped/raw-glob where the code stores full targets and the filtered file subset; the inference-pass counter docs named getCreateNodesResultsForPlugin, which Phase 4 does not go through — the counter counts whole-workspace passes (one per registration group on verify); include-coverage and plugin-filled-defaults JSDoc dropped their false 'exactly'/'never' absolutes. Typing: distinctOptionSets and InferenceOptionSet.options are raw mapper output that never receives defaults — type them Partial<T> and drop the casts; collectMigrationScope's trailing params become optional. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Miroslav J...
Succeeded
36547
47baa8a3 test(devkit): align inferred migrator target default specs
by Miroslav J...
Canceled
36547
47baa8a3 test(devkit): align inferred migrator target default specs
by Miroslav J...
Failed
36547
Fix applied→
47baa8a3 test(devkit): align inferred migrator target default specs
by Miroslav J...
Succeeded
36548
affff15e fix(linter): lazy load inferred eslint project files
by Miroslav J...
Failed
36547
0ea7405e test(devkit): update convert-to-inferred plugin specs for the hoist shape Update the plugin convert-to-inferred specs whose emitted config legitimately moved to the new centralized shape (shared config in nx.json targetDefaults, project.json carries deviations only): - vite / storybook / remix: update the --all/all-projects inline snapshots; document where the shared config went (targetDefaults assertions in vite + remix). - eslint / jest / webpack: add explicit effective-equivalence tests — two projects share a non-inferred option, so it is centralized exactly once into targetDefaults and the merged (effective) config still resolves it per project, with no per-project duplication. Guards against a shape update hiding a behavioral regression. No generator changes. webpack/rollup/rspack/next keep their pre-existing prettier/formatting failures (env-specific, empty diff vs master) — not touched here. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Miroslav J...
Failed
36548
Flaky task→
affff15e fix(linter): lazy load inferred eslint project files
by Miroslav J...
Failed
36547
Fix applied→
0ea7405e test(devkit): update convert-to-inferred plugin specs for the hoist shape Update the plugin convert-to-inferred specs whose emitted config legitimately moved to the new centralized shape (shared config in nx.json targetDefaults, project.json carries deviations only): - vite / storybook / remix: update the --all/all-projects inline snapshots; document where the shared config went (targetDefaults assertions in vite + remix). - eslint / jest / webpack: add explicit effective-equivalence tests — two projects share a non-inferred option, so it is centralized exactly once into targetDefaults and the merged (effective) config still resolves it per project, with no per-project duplication. Guards against a shape update hiding a behavioral regression. No generator changes. webpack/rollup/rspack/next keep their pre-existing prettier/formatting failures (env-specific, empty diff vs master) — not touched here. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Miroslav J...
Succeeded
36457
34a51bb1 docs(nx-cloud): trim on-prem specifics from AI features guide per review - Remove instance-wide key helm-values block and NX_CLOUD_ANTHROPIC_API_KEY startup detail (Caleb: keep on-prem install config out of public docs) - Feature-first structure; drop plan-availability aside and NX_CLOUD_AI_ENABLED version aside (Jack) - Bold feature names, use contractions, use "installation admin" terminology (Jack) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
by Miroslav J...
Succeeded
36458
cc324359 fix(devkit): error early when generating a project with an already used name Generating a project in a nested directory (e.g. apps/nested/server) derives the project name from the last directory segment. If another project already uses that name (e.g. apps/server), the generator used to proceed and fail later during project graph construction with a confusing "projects are defined in multiple locations" error, after files were already written. Validate the resolved name against existing projects up front and fail with an actionable message that suggests passing --name. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Miroslav J...
Failed
36458
Fix applied→
cc324359 fix(devkit): error early when generating a project with an already used name Generating a project in a nested directory (e.g. apps/nested/server) derives the project name from the last directory segment. If another project already uses that name (e.g. apps/server), the generator used to proceed and fail later during project graph construction with a confusing "projects are defined in multiple locations" error, after files were already written. Validate the resolved name against existing projects up front and fail with an actionable message that suggests passing --name. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Miroslav J...
Succeeded
36457
ba1583c7 docs(nx-cloud): update BYOK and AI key setup for 2026.07.1 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Miroslav J...
Succeeded
36334
fd23d12f fix(core): surface out-of-set dependency resolution warning for filtered-out groups When an out-of-set local dependency's current version cannot be resolved, the remediation warning was buffered to that dependency's ProjectLogger. On the success path a logger is only flushed by its release group's processGroup, so if the dependency lived in a different release group that was filtered out of the run (and therefore never processed), the warning was silently dropped. Flush the dependency's logger immediately after buffering the warning in resolveCurrentVersionForOutOfSetProject. flush() clears the buffer, so a later per-group flush of the same logger is a no-op and cannot double-print. Also make the release-version spec's ProjectLogger test double faithful (flush emits buffered lines into a capture array and clears) so flushed output can be asserted, and add coverage for the different-group (previously dropped) and same-group (exactly-once) cases. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
by Miroslav J...
Failed
36455
84fb74e0 fix(devkit): error early when generating a project with an already used name Generating a project in a nested directory (e.g. apps/a2v-migration/server) derives the project name from the last directory segment. If another project already uses that name (e.g. apps/server), the generator used to proceed and fail later during project graph construction with a confusing "projects are defined in multiple locations" error, after files were already written. Validate the resolved name against existing projects up front and fail with an actionable message that suggests passing --name. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Miroslav J...