Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
34937
Flaky task→
332c9d4e docs(core): document @nx/js pluginsConfig options and caveats - Expand projectsAffectedByDependencyUpdates docs with per-value table and caution aside explaining 'auto' is pnpm-only - Expand analyze-source-files page to also cover analyzePackageJson and analyzeLockfile (previously undocumented) - Add pluginsConfig section to nx-json reference - Fix selectivelyHashTsConfig description to mention both tsconfig.base.json and tsconfig.json - Update sidebar label to reflect broader page scope
1 day ago by Steven Nance
Succeeded
34842
1157db96 fix(maven): filter out external-to-external dependencies in createDependencies When nx-maven-plugin v0.0.15 emits external-to-external Maven dependency edges (e.g., maven:org.springframework:spring-core -> maven:org.springframework:spring-jcl), the source cannot be resolved to a workspace project via rootToProjectMap, resulting in undefined source values that crash Nx core's fileDataDepTarget(). Filter out dependencies where source or target cannot be resolved to a workspace project, matching the pattern used in the Gradle plugin fix (#29943).
6 days ago by Steven Nance
Canceled
34842
ac701288 fix(maven): filter out external-to-external dependencies in createDependencies When nx-maven-plugin v0.0.15 emits external-to-external Maven dependency edges (e.g., maven:org.springframework:spring-core -> maven:org.springframework:spring-jcl), the source cannot be resolved to a workspace project via rootToProjectMap, resulting in undefined source values that crash Nx core's fileDataDepTarget(). Filter out dependencies where source or target cannot be resolved to a workspace project, matching the pattern used in the Gradle plugin fix (#29943).
6 days ago by Steven Nance
Canceled
34842
b072c16b fix(maven): filter out external-to-external dependencies in createDependencies When nx-maven-plugin v0.0.15 emits external-to-external Maven dependency edges (e.g., maven:org.springframework:spring-core -> maven:org.springframework:spring-jcl), the source cannot be resolved to a workspace project via rootToProjectMap, resulting in undefined source values that crash Nx core's fileDataDepTarget(). Filter out dependencies where source or target cannot be resolved to a workspace project, matching the pattern used in the Gradle plugin fix (#29943).
7 days ago by Steven Nance
Failed
master
6b59e745 docs(nx-cloud): add DPE information exchange section to Okta SAML docs (#34794) ## Current Behavior The Okta SAML doc ends with a vague "Contact your developer productivity engineer" message. It doesn't specify what information needs to be exchanged between the customer and DPE to enable SAML and SCIM. This section was present in the old combined `auth-saml.md` but was lost during the migration to separate Okta/Azure docs in astro-docs. ## Expected Behavior The doc now has a clear "Information to exchange with your DPE" section that outlines: - **From your DPE** (provided up front): Nx Cloud App URL, JWT token, and Organization ID for SCIM setup - **Send back to your DPE**: SAML certificate and SAML entry point URL This matches the pattern already used in the Azure SAML doc and assumes SCIM will be configured. ## Related Issue(s) N/A --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: llwt <llwt@users.noreply.github.com>
8 days ago by Steven Nance
Failed
master
6b59e745 docs(nx-cloud): add DPE information exchange section to Okta SAML docs (#34794) ## Current Behavior The Okta SAML doc ends with a vague "Contact your developer productivity engineer" message. It doesn't specify what information needs to be exchanged between the customer and DPE to enable SAML and SCIM. This section was present in the old combined `auth-saml.md` but was lost during the migration to separate Okta/Azure docs in astro-docs. ## Expected Behavior The doc now has a clear "Information to exchange with your DPE" section that outlines: - **From your DPE** (provided up front): Nx Cloud App URL, JWT token, and Organization ID for SCIM setup - **Send back to your DPE**: SAML certificate and SAML entry point URL This matches the pattern already used in the Azure SAML doc and assumes SCIM will be configured. ## Related Issue(s) N/A --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: llwt <llwt@users.noreply.github.com>
8 days ago by Steven Nance
Failed
master
6b59e745 docs(nx-cloud): add DPE information exchange section to Okta SAML docs (#34794) ## Current Behavior The Okta SAML doc ends with a vague "Contact your developer productivity engineer" message. It doesn't specify what information needs to be exchanged between the customer and DPE to enable SAML and SCIM. This section was present in the old combined `auth-saml.md` but was lost during the migration to separate Okta/Azure docs in astro-docs. ## Expected Behavior The doc now has a clear "Information to exchange with your DPE" section that outlines: - **From your DPE** (provided up front): Nx Cloud App URL, JWT token, and Organization ID for SCIM setup - **Send back to your DPE**: SAML certificate and SAML entry point URL This matches the pattern already used in the Azure SAML doc and assumes SCIM will be configured. ## Related Issue(s) N/A --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: llwt <llwt@users.noreply.github.com>
9 days ago by Steven Nance
Succeeded
master
6b59e745 docs(nx-cloud): add DPE information exchange section to Okta SAML docs (#34794) ## Current Behavior The Okta SAML doc ends with a vague "Contact your developer productivity engineer" message. It doesn't specify what information needs to be exchanged between the customer and DPE to enable SAML and SCIM. This section was present in the old combined `auth-saml.md` but was lost during the migration to separate Okta/Azure docs in astro-docs. ## Expected Behavior The doc now has a clear "Information to exchange with your DPE" section that outlines: - **From your DPE** (provided up front): Nx Cloud App URL, JWT token, and Organization ID for SCIM setup - **Send back to your DPE**: SAML certificate and SAML entry point URL This matches the pattern already used in the Azure SAML doc and assumes SCIM will be configured. ## Related Issue(s) N/A --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: llwt <llwt@users.noreply.github.com>
9 days ago by Steven Nance
Failed
master
6b59e745 docs(nx-cloud): add DPE information exchange section to Okta SAML docs (#34794) ## Current Behavior The Okta SAML doc ends with a vague "Contact your developer productivity engineer" message. It doesn't specify what information needs to be exchanged between the customer and DPE to enable SAML and SCIM. This section was present in the old combined `auth-saml.md` but was lost during the migration to separate Okta/Azure docs in astro-docs. ## Expected Behavior The doc now has a clear "Information to exchange with your DPE" section that outlines: - **From your DPE** (provided up front): Nx Cloud App URL, JWT token, and Organization ID for SCIM setup - **Send back to your DPE**: SAML certificate and SAML entry point URL This matches the pattern already used in the Azure SAML doc and assumes SCIM will be configured. ## Related Issue(s) N/A --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: llwt <llwt@users.noreply.github.com>
9 days ago by Steven Nance
Failed
master
6b59e745 docs(nx-cloud): add DPE information exchange section to Okta SAML docs (#34794) ## Current Behavior The Okta SAML doc ends with a vague "Contact your developer productivity engineer" message. It doesn't specify what information needs to be exchanged between the customer and DPE to enable SAML and SCIM. This section was present in the old combined `auth-saml.md` but was lost during the migration to separate Okta/Azure docs in astro-docs. ## Expected Behavior The doc now has a clear "Information to exchange with your DPE" section that outlines: - **From your DPE** (provided up front): Nx Cloud App URL, JWT token, and Organization ID for SCIM setup - **Send back to your DPE**: SAML certificate and SAML entry point URL This matches the pattern already used in the Azure SAML doc and assumes SCIM will be configured. ## Related Issue(s) N/A --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: llwt <llwt@users.noreply.github.com>
9 days ago by Steven Nance
Failed
master
6b59e745 docs(nx-cloud): add DPE information exchange section to Okta SAML docs (#34794) ## Current Behavior The Okta SAML doc ends with a vague "Contact your developer productivity engineer" message. It doesn't specify what information needs to be exchanged between the customer and DPE to enable SAML and SCIM. This section was present in the old combined `auth-saml.md` but was lost during the migration to separate Okta/Azure docs in astro-docs. ## Expected Behavior The doc now has a clear "Information to exchange with your DPE" section that outlines: - **From your DPE** (provided up front): Nx Cloud App URL, JWT token, and Organization ID for SCIM setup - **Send back to your DPE**: SAML certificate and SAML entry point URL This matches the pattern already used in the Azure SAML doc and assumes SCIM will be configured. ## Related Issue(s) N/A --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: llwt <llwt@users.noreply.github.com>
9 days ago by Steven Nance
Failed
master
6b59e745 docs(nx-cloud): add DPE information exchange section to Okta SAML docs (#34794) ## Current Behavior The Okta SAML doc ends with a vague "Contact your developer productivity engineer" message. It doesn't specify what information needs to be exchanged between the customer and DPE to enable SAML and SCIM. This section was present in the old combined `auth-saml.md` but was lost during the migration to separate Okta/Azure docs in astro-docs. ## Expected Behavior The doc now has a clear "Information to exchange with your DPE" section that outlines: - **From your DPE** (provided up front): Nx Cloud App URL, JWT token, and Organization ID for SCIM setup - **Send back to your DPE**: SAML certificate and SAML entry point URL This matches the pattern already used in the Azure SAML doc and assumes SCIM will be configured. ## Related Issue(s) N/A --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: llwt <llwt@users.noreply.github.com>
9 days ago by Steven Nance
Failed
master
6b59e745 docs(nx-cloud): add DPE information exchange section to Okta SAML docs (#34794) ## Current Behavior The Okta SAML doc ends with a vague "Contact your developer productivity engineer" message. It doesn't specify what information needs to be exchanged between the customer and DPE to enable SAML and SCIM. This section was present in the old combined `auth-saml.md` but was lost during the migration to separate Okta/Azure docs in astro-docs. ## Expected Behavior The doc now has a clear "Information to exchange with your DPE" section that outlines: - **From your DPE** (provided up front): Nx Cloud App URL, JWT token, and Organization ID for SCIM setup - **Send back to your DPE**: SAML certificate and SAML entry point URL This matches the pattern already used in the Azure SAML doc and assumes SCIM will be configured. ## Related Issue(s) N/A --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: llwt <llwt@users.noreply.github.com>
9 days ago by Steven Nance
Failed
master
6b59e745 docs(nx-cloud): add DPE information exchange section to Okta SAML docs (#34794) ## Current Behavior The Okta SAML doc ends with a vague "Contact your developer productivity engineer" message. It doesn't specify what information needs to be exchanged between the customer and DPE to enable SAML and SCIM. This section was present in the old combined `auth-saml.md` but was lost during the migration to separate Okta/Azure docs in astro-docs. ## Expected Behavior The doc now has a clear "Information to exchange with your DPE" section that outlines: - **From your DPE** (provided up front): Nx Cloud App URL, JWT token, and Organization ID for SCIM setup - **Send back to your DPE**: SAML certificate and SAML entry point URL This matches the pattern already used in the Azure SAML doc and assumes SCIM will be configured. ## Related Issue(s) N/A --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: llwt <llwt@users.noreply.github.com>
9 days ago by Steven Nance
Failed
master
6b59e745 docs(nx-cloud): add DPE information exchange section to Okta SAML docs (#34794) ## Current Behavior The Okta SAML doc ends with a vague "Contact your developer productivity engineer" message. It doesn't specify what information needs to be exchanged between the customer and DPE to enable SAML and SCIM. This section was present in the old combined `auth-saml.md` but was lost during the migration to separate Okta/Azure docs in astro-docs. ## Expected Behavior The doc now has a clear "Information to exchange with your DPE" section that outlines: - **From your DPE** (provided up front): Nx Cloud App URL, JWT token, and Organization ID for SCIM setup - **Send back to your DPE**: SAML certificate and SAML entry point URL This matches the pattern already used in the Azure SAML doc and assumes SCIM will be configured. ## Related Issue(s) N/A --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: llwt <llwt@users.noreply.github.com>
9 days ago by Steven Nance
Failed
master
6b59e745 docs(nx-cloud): add DPE information exchange section to Okta SAML docs (#34794) ## Current Behavior The Okta SAML doc ends with a vague "Contact your developer productivity engineer" message. It doesn't specify what information needs to be exchanged between the customer and DPE to enable SAML and SCIM. This section was present in the old combined `auth-saml.md` but was lost during the migration to separate Okta/Azure docs in astro-docs. ## Expected Behavior The doc now has a clear "Information to exchange with your DPE" section that outlines: - **From your DPE** (provided up front): Nx Cloud App URL, JWT token, and Organization ID for SCIM setup - **Send back to your DPE**: SAML certificate and SAML entry point URL This matches the pattern already used in the Azure SAML doc and assumes SCIM will be configured. ## Related Issue(s) N/A --------- Co-authored-by: nx-cloud[bot] <71083854+nx-cloud[bot]@users.noreply.github.com> Co-authored-by: llwt <llwt@users.noreply.github.com>
9 days ago by Steven Nance
Failed
34794
Fix applied→
5001cb7f docs(nx-cloud): add DPE information exchange section to Okta SAML docs The Okta SAML doc lost its section outlining what information needs to be exchanged with the DPE during setup. This adds a clear section covering what the DPE provides up front (Nx Cloud App URL, JWT token, org ID) and what the customer sends back (SAML certificate and entry point URL).
10 days ago by Steven Nance
Succeeded
master
654118ad fix(vitest)!: resolve reportsDirectory against workspace root (#34720) ## Current Behavior When `reportsDirectory` is configured with `{workspaceRoot}` token in `nx.json` targetDefaults: ```json "@nx/vitest:test": { "options": { "reportsDirectory": "{workspaceRoot}/coverage/{projectRoot}" } } ``` Coverage output lands in the wrong location. For example, with a project at `apps/my-app`, coverage goes to `apps/my-app/coverage/apps/my-app/` instead of the intended `coverage/apps/my-app/`. ## Expected Behavior Coverage output should be written to `<workspaceRoot>/coverage/apps/my-app/`. ## Root Cause Nx's `resolveNxTokensInOptions` strips `{workspaceRoot}/` from option values and replaces `{projectRoot}`, producing a workspace-root-relative path (e.g. `coverage/apps/my-app`). The vitest executor then passed this directly to vitest, which resolved it relative to the **project root** — not the workspace root. ## Fix Resolve non-absolute `reportsDirectory` paths against the workspace root before passing them to vitest, so vitest writes coverage to the correct location. ## Test Plan - Added unit tests for the new `resolveReportsDirectory` helper - Verified with a reproduction workspace that coverage now lands at the correct path
12 days ago by Steven Nance
Succeeded
34720
1b735658 fix(vue): update library test to match workspace-root-relative reportsDirectory
12 days ago by Steven Nance
Failed
34720
5c31d93c Merge branch 'master' into fix/vitest-reports-directory-workspace-root
12 days ago by Steven Nance