Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
master
cde6e59e fix(nx-dev): remove broken header links (podcast) (#35410) ## Current Behavior The Resources dropdown in the astro-docs header contained links returning 404 on nx.dev: - `/podcast` - `/resources-library?*` -> `/resources?...` Additionally, `/webinar` redirected to `/webinars` (canonical). ## Expected Behavior - Podcasts entry removed (page no longer exists). - Books / Case Studies / Whitepapers repointed to the new `/resources?filterBy=...` URLs. - Webinars points directly to `/webinars` (no redirect). All 12 Resources dropdown links verified returning 200. Books link clicked through from the local astro-docs dropdown and confirmed to load the Resources Library page.
by Juri Strum...
Succeeded
master
fcbc20d5 docs(nx-dev): correct sandbox mode availability to 22.6 (#35378)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
by Juri Strum...
Succeeded
master
fcbc20d5 docs(nx-dev): correct sandbox mode availability to 22.6 (#35378)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes #
by Juri Strum...
Succeeded
master
5a7e851c docs(nx-dev): blog post on sharing Tailwind styles in a monorepo (#35229)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: juristr <juristr@users.noreply.github.com>
by Juri Strum...
Failed
22.6.x
2fa235d1 docs(nx-dev): blog post on sharing Tailwind styles in a monorepo (#35229)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: juristr <juristr@users.noreply.github.com> (cherry picked from commit 5a7e851ce1c8c1a22eb1a57621c4814ae141b266)
by Juri Strum...
Succeeded
master
5a7e851c docs(nx-dev): blog post on sharing Tailwind styles in a monorepo (#35229)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: juristr <juristr@users.noreply.github.com>
by Juri Strum...
Failed
master
5a7e851c docs(nx-dev): blog post on sharing Tailwind styles in a monorepo (#35229)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: juristr <juristr@users.noreply.github.com>
by Juri Strum...
Succeeded
master
5a7e851c docs(nx-dev): blog post on sharing Tailwind styles in a monorepo (#35229)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: juristr <juristr@users.noreply.github.com>
by Juri Strum...
Succeeded
master
5a7e851c docs(nx-dev): blog post on sharing Tailwind styles in a monorepo (#35229)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: juristr <juristr@users.noreply.github.com>
by Juri Strum...
Succeeded
master
5a7e851c docs(nx-dev): blog post on sharing Tailwind styles in a monorepo (#35229)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: juristr <juristr@users.noreply.github.com>
by Juri Strum...
Canceled
master
5a7e851c docs(nx-dev): blog post on sharing Tailwind styles in a monorepo (#35229)      ## Current Behavior  ## Expected Behavior  ## Related Issue(s)  Fixes # --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: juristr <juristr@users.noreply.github.com>
by Juri Strum...
Succeeded
master
fbe33a9c fix(nx-dev): correct YouTube channel URL on courses page (#35034) ## Current Behavior The courses page YouTube link points to `https://www.youtube.com/@naborx` which is incorrect. ## Expected Behavior The link points to `https://www.youtube.com/@nxdevtools`, the actual Nx YouTube channel. ## Related Issue(s) N/A
by Juri Strum...
Succeeded
master
fbe33a9c fix(nx-dev): correct YouTube channel URL on courses page (#35034) ## Current Behavior The courses page YouTube link points to `https://www.youtube.com/@naborx` which is incorrect. ## Expected Behavior The link points to `https://www.youtube.com/@nxdevtools`, the actual Nx YouTube channel. ## Related Issue(s) N/A
by Juri Strum...
Succeeded
master
2086e4c0 fix(testing): gracefully handle broken jest configs in alias migration (#34901) ## Current Behavior The `replace-removed-matcher-aliases` migration crashes the entire migration runner when a project has a broken or misconfigured `jest.config.ts`. This was discovered while upgrading nx-labs from Nx 21 to 22 via `nx migrate --run-migrations`. The migration uses Jest's `readConfig()` and `Runtime.createContext()` to resolve jest configs, but has no error handling around these calls. If any project has issues like: - A missing file referenced in the config (e.g. `.lib.swcrc` that was renamed to `.swcrc`) - A missing transform module (e.g. `@swc/jest` not installed) - A missing preset file (e.g. `jest.preset.ts` instead of `jest.preset.js`) ...the entire migration fails with an opaque error: ``` Error: Command failed: /var/folders/.../node_modules/.bin/nx _migrate --run-migrations at checkExecSyncError (node:child_process:925:11) status: 1, stdout: null, stderr: null ``` The actual errors are swallowed by the nested `execSync` call, making it very hard to debug. ## Expected Behavior The migration should skip projects with broken jest configs and continue processing the rest of the workspace. ## Fix Wrapped the `readConfig` / `Runtime.createContext` / `SearchSource.getTestPaths` block in a try-catch that skips the failing project. This matches the defensive pattern already used in `packages/jest/src/plugins/plugin.ts` for similar jest config resolution. ## Test Plan - Added 3 tests covering: missing file reference, missing preset, and verifying valid projects are still processed when a sibling project has a broken config - All existing tests continue to pass
by Juri Strum...
Succeeded
master
2086e4c0 fix(testing): gracefully handle broken jest configs in alias migration (#34901) ## Current Behavior The `replace-removed-matcher-aliases` migration crashes the entire migration runner when a project has a broken or misconfigured `jest.config.ts`. This was discovered while upgrading nx-labs from Nx 21 to 22 via `nx migrate --run-migrations`. The migration uses Jest's `readConfig()` and `Runtime.createContext()` to resolve jest configs, but has no error handling around these calls. If any project has issues like: - A missing file referenced in the config (e.g. `.lib.swcrc` that was renamed to `.swcrc`) - A missing transform module (e.g. `@swc/jest` not installed) - A missing preset file (e.g. `jest.preset.ts` instead of `jest.preset.js`) ...the entire migration fails with an opaque error: ``` Error: Command failed: /var/folders/.../node_modules/.bin/nx _migrate --run-migrations at checkExecSyncError (node:child_process:925:11) status: 1, stdout: null, stderr: null ``` The actual errors are swallowed by the nested `execSync` call, making it very hard to debug. ## Expected Behavior The migration should skip projects with broken jest configs and continue processing the rest of the workspace. ## Fix Wrapped the `readConfig` / `Runtime.createContext` / `SearchSource.getTestPaths` block in a try-catch that skips the failing project. This matches the defensive pattern already used in `packages/jest/src/plugins/plugin.ts` for similar jest config resolution. ## Test Plan - Added 3 tests covering: missing file reference, missing preset, and verifying valid projects are still processed when a sibling project has a broken config - All existing tests continue to pass
by Juri Strum...
Succeeded
master
2086e4c0 fix(testing): gracefully handle broken jest configs in alias migration (#34901) ## Current Behavior The `replace-removed-matcher-aliases` migration crashes the entire migration runner when a project has a broken or misconfigured `jest.config.ts`. This was discovered while upgrading nx-labs from Nx 21 to 22 via `nx migrate --run-migrations`. The migration uses Jest's `readConfig()` and `Runtime.createContext()` to resolve jest configs, but has no error handling around these calls. If any project has issues like: - A missing file referenced in the config (e.g. `.lib.swcrc` that was renamed to `.swcrc`) - A missing transform module (e.g. `@swc/jest` not installed) - A missing preset file (e.g. `jest.preset.ts` instead of `jest.preset.js`) ...the entire migration fails with an opaque error: ``` Error: Command failed: /var/folders/.../node_modules/.bin/nx _migrate --run-migrations at checkExecSyncError (node:child_process:925:11) status: 1, stdout: null, stderr: null ``` The actual errors are swallowed by the nested `execSync` call, making it very hard to debug. ## Expected Behavior The migration should skip projects with broken jest configs and continue processing the rest of the workspace. ## Fix Wrapped the `readConfig` / `Runtime.createContext` / `SearchSource.getTestPaths` block in a try-catch that skips the failing project. This matches the defensive pattern already used in `packages/jest/src/plugins/plugin.ts` for similar jest config resolution. ## Test Plan - Added 3 tests covering: missing file reference, missing preset, and verifying valid projects are still processed when a sibling project has a broken config - All existing tests continue to pass
by Juri Strum...
Succeeded
master
2086e4c0 fix(testing): gracefully handle broken jest configs in alias migration (#34901) ## Current Behavior The `replace-removed-matcher-aliases` migration crashes the entire migration runner when a project has a broken or misconfigured `jest.config.ts`. This was discovered while upgrading nx-labs from Nx 21 to 22 via `nx migrate --run-migrations`. The migration uses Jest's `readConfig()` and `Runtime.createContext()` to resolve jest configs, but has no error handling around these calls. If any project has issues like: - A missing file referenced in the config (e.g. `.lib.swcrc` that was renamed to `.swcrc`) - A missing transform module (e.g. `@swc/jest` not installed) - A missing preset file (e.g. `jest.preset.ts` instead of `jest.preset.js`) ...the entire migration fails with an opaque error: ``` Error: Command failed: /var/folders/.../node_modules/.bin/nx _migrate --run-migrations at checkExecSyncError (node:child_process:925:11) status: 1, stdout: null, stderr: null ``` The actual errors are swallowed by the nested `execSync` call, making it very hard to debug. ## Expected Behavior The migration should skip projects with broken jest configs and continue processing the rest of the workspace. ## Fix Wrapped the `readConfig` / `Runtime.createContext` / `SearchSource.getTestPaths` block in a try-catch that skips the failing project. This matches the defensive pattern already used in `packages/jest/src/plugins/plugin.ts` for similar jest config resolution. ## Test Plan - Added 3 tests covering: missing file reference, missing preset, and verifying valid projects are still processed when a sibling project has a broken config - All existing tests continue to pass
by Juri Strum...
Failed
master
2086e4c0 fix(testing): gracefully handle broken jest configs in alias migration (#34901) ## Current Behavior The `replace-removed-matcher-aliases` migration crashes the entire migration runner when a project has a broken or misconfigured `jest.config.ts`. This was discovered while upgrading nx-labs from Nx 21 to 22 via `nx migrate --run-migrations`. The migration uses Jest's `readConfig()` and `Runtime.createContext()` to resolve jest configs, but has no error handling around these calls. If any project has issues like: - A missing file referenced in the config (e.g. `.lib.swcrc` that was renamed to `.swcrc`) - A missing transform module (e.g. `@swc/jest` not installed) - A missing preset file (e.g. `jest.preset.ts` instead of `jest.preset.js`) ...the entire migration fails with an opaque error: ``` Error: Command failed: /var/folders/.../node_modules/.bin/nx _migrate --run-migrations at checkExecSyncError (node:child_process:925:11) status: 1, stdout: null, stderr: null ``` The actual errors are swallowed by the nested `execSync` call, making it very hard to debug. ## Expected Behavior The migration should skip projects with broken jest configs and continue processing the rest of the workspace. ## Fix Wrapped the `readConfig` / `Runtime.createContext` / `SearchSource.getTestPaths` block in a try-catch that skips the failing project. This matches the defensive pattern already used in `packages/jest/src/plugins/plugin.ts` for similar jest config resolution. ## Test Plan - Added 3 tests covering: missing file reference, missing preset, and verifying valid projects are still processed when a sibling project has a broken config - All existing tests continue to pass
by Juri Strum...
Succeeded
master
2086e4c0 fix(testing): gracefully handle broken jest configs in alias migration (#34901) ## Current Behavior The `replace-removed-matcher-aliases` migration crashes the entire migration runner when a project has a broken or misconfigured `jest.config.ts`. This was discovered while upgrading nx-labs from Nx 21 to 22 via `nx migrate --run-migrations`. The migration uses Jest's `readConfig()` and `Runtime.createContext()` to resolve jest configs, but has no error handling around these calls. If any project has issues like: - A missing file referenced in the config (e.g. `.lib.swcrc` that was renamed to `.swcrc`) - A missing transform module (e.g. `@swc/jest` not installed) - A missing preset file (e.g. `jest.preset.ts` instead of `jest.preset.js`) ...the entire migration fails with an opaque error: ``` Error: Command failed: /var/folders/.../node_modules/.bin/nx _migrate --run-migrations at checkExecSyncError (node:child_process:925:11) status: 1, stdout: null, stderr: null ``` The actual errors are swallowed by the nested `execSync` call, making it very hard to debug. ## Expected Behavior The migration should skip projects with broken jest configs and continue processing the rest of the workspace. ## Fix Wrapped the `readConfig` / `Runtime.createContext` / `SearchSource.getTestPaths` block in a try-catch that skips the failing project. This matches the defensive pattern already used in `packages/jest/src/plugins/plugin.ts` for similar jest config resolution. ## Test Plan - Added 3 tests covering: missing file reference, missing preset, and verifying valid projects are still processed when a sibling project has a broken config - All existing tests continue to pass
by Juri Strum...
Failed
master
74288752 docs(core): rewrite Nx vs Turborepo comparison page (#34792) ## Current Behavior The Nx vs Turborepo comparison doc mixed setup complexity with advanced features without a clear progression. Some sections were missing (code generation comparison, cross-repo coordination, project graph visualization). Images were in PNG format. ## Expected Behavior - Progressive structure: starts with basics (onboarding, running tasks) and moves to advanced capabilities (CI, AI, cross-repo); beats the misconception that starting with Nx is more complex or you need to go full in - Overview table at top for quick comparison with links to sections (we could collapse it if it gets too much 🤔) - New sections: Running tasks (to emphasize how simple it is to run tasks in an existing repo, again beating the misconceptions that are around), Cross-repo coordination, CI throughput, Project graph - Improved sections: Onboarding (incremental adoption story), Caching (real benchmark configs), Code generation (acknowledges turbo gen) - All images converted to AVIF - Migration doc updated: removed beta/Nx 21 language for continuous tasks New docs: - [comparison doc](https://deploy-preview-34792--nx-docs.netlify.app/docs/guides/adopting-nx/nx-vs-turborepo) - [migration doc (mostly untouched)](https://deploy-preview-34792--nx-docs.netlify.app/docs/guides/adopting-nx/from-turborepo) ## Related Issue(s) N/A - documentation improvement
by Juri Strum...