Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
master
ba0c07d9 chore(misc): include blog in auto-deployment (#35582) It's a separate app now, needs to update as well.
by Jack Hsu
Succeeded
master
ba0c07d9 chore(misc): include blog in auto-deployment (#35582) It's a separate app now, needs to update as well.
by Jack Hsu
Succeeded
master
ba0c07d9 chore(misc): include blog in auto-deployment (#35582) It's a separate app now, needs to update as well.
by Jack Hsu
Succeeded
35520
172ee928 fix(misc): restore the skipped-Cloud "next steps" banner for --nxCloud=skip After dropping CNW's forced normalization to the connect flow, the post-creation banner that suggests "Run nx connect" was also removed. Users who explicitly pass --nxCloud=skip lose the (still useful) hint. Restore getSkippedCloudMessage / getSkippedNxCloudInfo. When the user picks "skip" we still show the "Next steps: nx connect" banner. When they pick "never" we stay quiet (matches the original intent). NXC-4401
by Jack Hsu
Succeeded
35582
d06b74b2 chore(misc): include blog in auto-deployment
by Jack Hsu
Failed
35520
Flaky task→
172ee928 fix(misc): restore the skipped-Cloud "next steps" banner for --nxCloud=skip After dropping CNW's forced normalization to the connect flow, the post-creation banner that suggests "Run nx connect" was also removed. Users who explicitly pass --nxCloud=skip lose the (still useful) hint. Restore getSkippedCloudMessage / getSkippedNxCloudInfo. When the user picks "skip" we still show the "Next steps: nx connect" banner. When they pick "never" we stay quiet (matches the original intent). NXC-4401
by Jack Hsu
Failed
35520
130f7091 fix(misc): restore the skipped-Cloud "next steps" banner for --nxCloud=skip After dropping CNW's forced normalization to the connect flow, the post-creation banner that suggests "Run nx connect" was also removed. Users who explicitly pass --nxCloud=skip lose the (still useful) hint. Restore getSkippedCloudMessage / getSkippedNxCloudInfo. When the user picks "skip" we still show the "Next steps: nx connect" banner. When they pick "never" we stay quiet (matches the original intent). NXC-4401
by Jack Hsu
Canceled
35520
e9a7a744 fix(misc): restore the skipped-Cloud "next steps" banner for --nxCloud=skip After dropping CNW's forced normalization to the connect flow, the post-creation banner that suggests "Run nx connect" was also removed. Users who explicitly pass --nxCloud=skip lose the (still useful) hint. Restore getSkippedCloudMessage / getSkippedNxCloudInfo. When the user picks "skip" we still show the "Next steps: nx connect" banner. When they pick "never" we stay quiet (matches the original intent). NXC-4401
by Jack Hsu
Failed
35520
e351b91b fix(misc): restore the skipped-Cloud "next steps" banner for --nxCloud=skip After dropping CNW's forced normalization to the connect flow, the post-creation banner that suggests "Run nx connect" was also removed. Users who explicitly pass --nxCloud=skip lose the (still useful) hint. Restore getSkippedCloudMessage / getSkippedNxCloudInfo. When the user picks "skip" we still show the "Next steps: nx connect" banner. When they pick "never" we stay quiet (matches the original intent). NXC-4401
by Jack Hsu
Failed
35520
0eb61043 fix(misc): restore the skipped-Cloud "next steps" banner for --nxCloud=skip After dropping CNW's forced normalization to the connect flow, the post-creation banner that suggests "Run nx connect" was also removed. Users who explicitly pass --nxCloud=skip lose the (still useful) hint. Restore getSkippedCloudMessage / getSkippedNxCloudInfo. When the user picks "skip" we still show the "Next steps: nx connect" banner. When they pick "never" we stay quiet (matches the original intent). NXC-4401
by Jack Hsu
Failed
35520
2dabd75b fix(misc): restore the skipped-Cloud "next steps" banner for --nxCloud=skip After dropping CNW's forced normalization to the connect flow, the post-creation banner that suggests "Run nx connect" was also removed. Users who explicitly pass --nxCloud=skip lose the (still useful) hint. Restore getSkippedCloudMessage / getSkippedNxCloudInfo. When the user picks "skip" we still show the "Next steps: nx connect" banner. When they pick "never" we stay quiet (matches the original intent). NXC-4401
by Jack Hsu
Failed
master
70d1c195 feat(bundling)!: drop legacy typescript plugin and align rollup buildLibsFromSource default (#35516) ## Current Behavior `useLegacyTypescriptPlugin` opt-in keeps the `rollup-plugin-typescript2` code path alive in `@nx/rollup` with a deprecation warning. The `withNx` plugin defaults `buildLibsFromSource` to `false` while the executor schema defaults to `true` — same option, two defaults. ## Expected Behavior - `useLegacyTypescriptPlugin` option, schema entry, and `rollup-plugin-typescript2` dep removed; only `@rollup/plugin-typescript` remains. - `withNx` `buildLibsFromSource` default flipped to `true` so it matches the executor. - `update-23-0-0-remove-use-legacy-typescript-plugin` migration strips the deprecated option from existing project.json `options`/`configurations` and from `rollup.config.{cjs,mjs,js,ts}` `withNx({...})` calls so users see no behavior change after upgrade. ## Breaking Change Note `@rollup/plugin-typescript` enforces that the TS `outDir` is inside the rollup `output.dir`. Users whose custom `rollup.config.{cjs,mjs}` overrides `output.dir` to a path outside the executor's `outputPath` will fail with `Path of Typescript compiler option 'outDir' must be located inside Rollup 'dir' option`. The legacy `rollup-plugin-typescript2` was permissive here. Affected users should align their custom config's `output.dir` with the executor's `outputPath` (or use the function form `(config) => ({ ...config, output: { ...config.output[0], ...overrides } })` to preserve `dir`). Two e2e cases that exercised this legacy pattern were dropped from `rollup-legacy.test.ts`. ## Related Issue(s) Fixes NXC-4157
by Jack Hsu
Succeeded
35517
20c98cf3 fix(vite): tighten ensure-vitest-package migration @nx/vitest always installed, even in workspaces with no vitest usage. When @nx/vitest/plugin is already registered alongside @nx/vite/plugin entries that carry vitest options, those options are silently dropped. Migration guide backward-compat section still says "will be removed in Nx 23" rather than noting the removal happened. @nx/vitest installed only when vitest usage is detected: vitest in package.json, @nx/vite:test executor in any project, vitest-related options on @nx/vite/plugin, or vitest.config.* in any project root. Vitest options extracted from @nx/vite/plugin are merged into any existing @nx/vitest plugin entry (matched by include/exclude scope) without overwriting user-set fields. Migration guide backward-compat section updated to describe the removal as historical fact. Companion migration doc added under packages/vite/docs/. Addresses review comments on PR for NXC-4158
by Jack Hsu
Failed
35517
Flaky task→
20c98cf3 fix(vite): tighten ensure-vitest-package migration @nx/vitest always installed, even in workspaces with no vitest usage. When @nx/vitest/plugin is already registered alongside @nx/vite/plugin entries that carry vitest options, those options are silently dropped. Migration guide backward-compat section still says "will be removed in Nx 23" rather than noting the removal happened. @nx/vitest installed only when vitest usage is detected: vitest in package.json, @nx/vite:test executor in any project, vitest-related options on @nx/vite/plugin, or vitest.config.* in any project root. Vitest options extracted from @nx/vite/plugin are merged into any existing @nx/vitest plugin entry (matched by include/exclude scope) without overwriting user-set fields. Migration guide backward-compat section updated to describe the removal as historical fact. Companion migration doc added under packages/vite/docs/. Addresses review comments on PR for NXC-4158
by Jack Hsu
Succeeded
35516
e26fd360 feat(bundling)!: drop legacy typescript plugin and align rollup buildLibsFromSource default `useLegacyTypescriptPlugin` opt-in keeps the `rollup-plugin-typescript2` code path alive in `@nx/rollup` with a deprecation warning. The `withNx` plugin defaults `buildLibsFromSource` to `false` while the executor schema defaults to `true` — same option, two defaults. `useLegacyTypescriptPlugin` option, schema entry, and `rollup-plugin-typescript2` dep removed; only `@rollup/plugin-typescript` remains. `withNx` `buildLibsFromSource` default flipped to `true` to match executor. New migration strips the deprecated option from existing project.json and rollup.config.{cjs,mjs,js,ts} files so users see no behavior change after upgrade. Fixes NXC-4157
by Jack Hsu
Failed
35517
Fix ready→
1ac3797f fix(vite): tighten ensure-vitest-package migration @nx/vitest always installed, even in workspaces with no vitest usage. When @nx/vitest/plugin is already registered alongside @nx/vite/plugin entries that carry vitest options, those options are silently dropped. Migration guide backward-compat section still says "will be removed in Nx 23" rather than noting the removal happened. @nx/vitest installed only when vitest usage is detected: vitest in package.json, @nx/vite:test executor in any project, vitest-related options on @nx/vite/plugin, or vitest.config.* in any project root. Vitest options extracted from @nx/vite/plugin are merged into any existing @nx/vitest plugin entry (matched by include/exclude scope) without overwriting user-set fields. Migration guide backward-compat section updated to describe the removal as historical fact. Companion migration doc added under packages/vite/docs/. Addresses review comments on PR for NXC-4158
by Jack Hsu
Failed
35517
2661c6e2 fix(vite): tighten ensure-vitest-package migration ## Current Behavior @nx/vitest always installed, even in workspaces with no vitest usage. When @nx/vitest/plugin is already registered alongside @nx/vite/plugin entries that carry vitest options, those options are silently dropped. Migration guide backward-compat section still says "will be removed in Nx 23" rather than noting the removal happened. ## Expected Behavior @nx/vitest installed only when vitest usage is detected: vitest in package.json, @nx/vite:test executor in any project, vitest-related options on @nx/vite/plugin, or vitest.config.* in any project root. Vitest options extracted from @nx/vite/plugin are merged into any existing @nx/vitest plugin entry (matched by include/exclude scope) without overwriting user-set fields. Migration guide backward-compat section updated to describe the removal as historical fact. Companion migration doc added under packages/vite/docs/. ## Related Issue(s) Addresses review comments on PR for NXC-4158
by Jack Hsu
Failed
35571
Fix applied→
1f2b1749 chore(misc): test
by Jack Hsu
Failed
35516
Environment issue→
e26fd360 feat(bundling)!: drop legacy typescript plugin and align rollup buildLibsFromSource default `useLegacyTypescriptPlugin` opt-in keeps the `rollup-plugin-typescript2` code path alive in `@nx/rollup` with a deprecation warning. The `withNx` plugin defaults `buildLibsFromSource` to `false` while the executor schema defaults to `true` — same option, two defaults. `useLegacyTypescriptPlugin` option, schema entry, and `rollup-plugin-typescript2` dep removed; only `@rollup/plugin-typescript` remains. `withNx` `buildLibsFromSource` default flipped to `true` to match executor. New migration strips the deprecated option from existing project.json and rollup.config.{cjs,mjs,js,ts} files so users see no behavior change after upgrade. Fixes NXC-4157
by Jack Hsu
Succeeded
35520
03c55918 fix(misc): restore the skipped-Cloud "next steps" banner for --nxCloud=skip After dropping CNW's forced normalization to the connect flow, the post-creation banner that suggests "Run nx connect" was also removed. Users who explicitly pass --nxCloud=skip lose the (still useful) hint. Restore getSkippedCloudMessage / getSkippedNxCloudInfo. When the user picks "skip" we still show the "Next steps: nx connect" banner. When they pick "never" we stay quiet (matches the original intent). NXC-4401
by Jack Hsu