Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
master
81e7d472 chore(repo): update nx to 23.0.0-beta.4 (#35528) Updating Nx from 23.0.0-beta.3 to 23.0.0-beta.4
by Jason Jean
Succeeded
master
81e7d472 chore(repo): update nx to 23.0.0-beta.4 (#35528) Updating Nx from 23.0.0-beta.3 to 23.0.0-beta.4
by Jason Jean
Succeeded
master
33a83e1c fix(nx-dev): short-circuit bot probes in framer rewrite edge function (#35527) Some bots are hitting the server, scanning for wordpress paths. This is resulting in 500 server error, but we should return 404. This fails in prod (500): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://nx.dev//wp/wp-includes/wlwmanifest.xml' ``` Fixed in preview (404): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://deploy-preview-35527--nx-dev.netlify.app//wp/wp-includes/wlwmanifest.xml' ``` ## Current Behavior Bot scanners hit `GET //wp/wp-includes/wlwmanifest.xml` (leading `//`). `new URL(pathname, framerUrl)` parses `//wp/...` as protocol-relative, promoting `wp` to upstream host. Fetch fails with DNS lookup error and the function 500s. ## Expected Behavior Leading `/+` collapsed before resolving against `framerUrl`. Common WordPress / exploit probes (`wp-includes`, `wp-admin`, `xmlrpc.php`, `wlwmanifest`, `.env`, `.git/`) short-circuit to 404. ## Related Issue(s) DOC-498
by Jack Hsu
Succeeded
master
81e7d472 chore(repo): update nx to 23.0.0-beta.4 (#35528) Updating Nx from 23.0.0-beta.3 to 23.0.0-beta.4
by Jason Jean
Succeeded
master
81e7d472 chore(repo): update nx to 23.0.0-beta.4 (#35528) Updating Nx from 23.0.0-beta.3 to 23.0.0-beta.4
by Jason Jean
In progress
master
81e7d472 chore(repo): update nx to 23.0.0-beta.4 (#35528) Updating Nx from 23.0.0-beta.3 to 23.0.0-beta.4
by Jason Jean
Succeeded
master
9e01808f fix(core): restore deprecated allWorkspaceFiles on WorkspaceFileMap (#35518) ## Current Behavior #34425 ("remove redundant `allWorkspaceFiles` from the project graph pipeline") dropped `allWorkspaceFiles` from the `WorkspaceFileMap` interface without a deprecation cycle. Plugins that import `createFileMapUsingProjectGraph` from the deep path `nx/src/project-graph/file-map-utils` — e.g. `@nx/owners` — fail to type-check against the beta release: ``` src/plugin/plugin.ts(73,20): error TS2339: Property 'allWorkspaceFiles' does not exist on type 'WorkspaceFileMap'. src/plugin/plugin.spec.ts(799,5): error TS2353: Object literal may only specify known properties, and 'allWorkspaceFiles' does not exist in type 'WorkspaceFileMap'. ``` The path is technically internal (not exported from `@nx/devkit`), but real consumers (including cached nx-cloud workers — see #35502) reach in there, and #35502 already established the pattern of restoring removed members as `@deprecated` shims rather than breaking them outright. ## Expected Behavior `allWorkspaceFiles` is restored on `WorkspaceFileMap` as `@deprecated` and exposed from `createFileMap` via a **non-enumerable lazy getter**: - **Lazy** — derived from `fileMap.projectFileMap` + `fileMap.nonProjectFiles` only when read. Zero allocation for callers that don't touch it. - **Non-enumerable** — stays out of `JSON.stringify` / `Object.keys`, so the daemon-serialization wins from #34425 are preserved if a `WorkspaceFileMap` ever ends up on the wire. - **Optional** — daemon-internal call sites (`updateFileMap`) that never set the field still satisfy the type. The hot-path improvements from #34425 stay intact: - No `allWorkspaceFiles` on `SerializedProjectGraph` going across the daemon wire - No `copyFileData()` on every graph serialization - No `buildAllWorkspaceFiles()` on incremental updates - No `storedAllWorkspaceFiles` retained in `build-project-graph` state - `updateFileMap` return value unchanged The shim only sits at the plugin boundary — `createFileMapUsingProjectGraph`, which runs in the plugin's process, not the daemon. Same back-compat pattern as #35502 (`hydrateFileMap` 3-arg overload). Both can be removed in a future major once known consumers (ocean, cached cloud workers) age out. ## Related Issue(s) 
by Jason Jean
Succeeded
master
33a83e1c fix(nx-dev): short-circuit bot probes in framer rewrite edge function (#35527) Some bots are hitting the server, scanning for wordpress paths. This is resulting in 500 server error, but we should return 404. This fails in prod (500): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://nx.dev//wp/wp-includes/wlwmanifest.xml' ``` Fixed in preview (404): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://deploy-preview-35527--nx-dev.netlify.app//wp/wp-includes/wlwmanifest.xml' ``` ## Current Behavior Bot scanners hit `GET //wp/wp-includes/wlwmanifest.xml` (leading `//`). `new URL(pathname, framerUrl)` parses `//wp/...` as protocol-relative, promoting `wp` to upstream host. Fetch fails with DNS lookup error and the function 500s. ## Expected Behavior Leading `/+` collapsed before resolving against `framerUrl`. Common WordPress / exploit probes (`wp-includes`, `wp-admin`, `xmlrpc.php`, `wlwmanifest`, `.env`, `.git/`) short-circuit to 404. ## Related Issue(s) DOC-498
by Jack Hsu
Succeeded
master
81e7d472 chore(repo): update nx to 23.0.0-beta.4 (#35528) Updating Nx from 23.0.0-beta.3 to 23.0.0-beta.4
by Jason Jean
Succeeded
master
81e7d472 chore(repo): update nx to 23.0.0-beta.4 (#35528) Updating Nx from 23.0.0-beta.3 to 23.0.0-beta.4
by Jason Jean
Succeeded
master
81e7d472 chore(repo): update nx to 23.0.0-beta.4 (#35528) Updating Nx from 23.0.0-beta.3 to 23.0.0-beta.4
by Jason Jean
Succeeded
master
33a83e1c fix(nx-dev): short-circuit bot probes in framer rewrite edge function (#35527) Some bots are hitting the server, scanning for wordpress paths. This is resulting in 500 server error, but we should return 404. This fails in prod (500): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://nx.dev//wp/wp-includes/wlwmanifest.xml' ``` Fixed in preview (404): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://deploy-preview-35527--nx-dev.netlify.app//wp/wp-includes/wlwmanifest.xml' ``` ## Current Behavior Bot scanners hit `GET //wp/wp-includes/wlwmanifest.xml` (leading `//`). `new URL(pathname, framerUrl)` parses `//wp/...` as protocol-relative, promoting `wp` to upstream host. Fetch fails with DNS lookup error and the function 500s. ## Expected Behavior Leading `/+` collapsed before resolving against `framerUrl`. Common WordPress / exploit probes (`wp-includes`, `wp-admin`, `xmlrpc.php`, `wlwmanifest`, `.env`, `.git/`) short-circuit to 404. ## Related Issue(s) DOC-498
by Jack Hsu
Succeeded
master
33a83e1c fix(nx-dev): short-circuit bot probes in framer rewrite edge function (#35527) Some bots are hitting the server, scanning for wordpress paths. This is resulting in 500 server error, but we should return 404. This fails in prod (500): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://nx.dev//wp/wp-includes/wlwmanifest.xml' ``` Fixed in preview (404): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://deploy-preview-35527--nx-dev.netlify.app//wp/wp-includes/wlwmanifest.xml' ``` ## Current Behavior Bot scanners hit `GET //wp/wp-includes/wlwmanifest.xml` (leading `//`). `new URL(pathname, framerUrl)` parses `//wp/...` as protocol-relative, promoting `wp` to upstream host. Fetch fails with DNS lookup error and the function 500s. ## Expected Behavior Leading `/+` collapsed before resolving against `framerUrl`. Common WordPress / exploit probes (`wp-includes`, `wp-admin`, `xmlrpc.php`, `wlwmanifest`, `.env`, `.git/`) short-circuit to 404. ## Related Issue(s) DOC-498
by Jack Hsu
Succeeded
master
b4cb43f8 chore(repo): remove offboarded core team members from README (#35504) ## Current Behavior The Core Team section of the top-level `README.md` lists 23 people across 6 markdown tables (5 rows of 4 + 1 final row of 3). Three of those names are former team members who have offboarded: - Philip Fulcher (`philipjfulcher`) - Colum Ferry (`Coly010`) - Austin Fahsl (`fahslaj`) ## Expected Behavior Remove the three offboarded entries and reflow the surviving 20 names into 5 even rows of 4. Original ordering preserved; gaps closed left-to-right, top-to-bottom. ## Notes - README only — no other files modified. - CODEOWNERS uses team handles (`@nrwl/nx-cli-reviewers`), not individual usernames, so no change needed there. - 20 surviving members fit cleanly into 5 rows of 4 — no awkward partial row. - Source padding regenerated per-row so the raw markdown stays visually aligned. ## Related Issue(s) (internal cleanup; no public issue)
by Jason Jean
Succeeded
master
33a83e1c fix(nx-dev): short-circuit bot probes in framer rewrite edge function (#35527) Some bots are hitting the server, scanning for wordpress paths. This is resulting in 500 server error, but we should return 404. This fails in prod (500): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://nx.dev//wp/wp-includes/wlwmanifest.xml' ``` Fixed in preview (404): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://deploy-preview-35527--nx-dev.netlify.app//wp/wp-includes/wlwmanifest.xml' ``` ## Current Behavior Bot scanners hit `GET //wp/wp-includes/wlwmanifest.xml` (leading `//`). `new URL(pathname, framerUrl)` parses `//wp/...` as protocol-relative, promoting `wp` to upstream host. Fetch fails with DNS lookup error and the function 500s. ## Expected Behavior Leading `/+` collapsed before resolving against `framerUrl`. Common WordPress / exploit probes (`wp-includes`, `wp-admin`, `xmlrpc.php`, `wlwmanifest`, `.env`, `.git/`) short-circuit to 404. ## Related Issue(s) DOC-498
by Jack Hsu
Succeeded
master
33a83e1c fix(nx-dev): short-circuit bot probes in framer rewrite edge function (#35527) Some bots are hitting the server, scanning for wordpress paths. This is resulting in 500 server error, but we should return 404. This fails in prod (500): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://nx.dev//wp/wp-includes/wlwmanifest.xml' ``` Fixed in preview (404): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://deploy-preview-35527--nx-dev.netlify.app//wp/wp-includes/wlwmanifest.xml' ``` ## Current Behavior Bot scanners hit `GET //wp/wp-includes/wlwmanifest.xml` (leading `//`). `new URL(pathname, framerUrl)` parses `//wp/...` as protocol-relative, promoting `wp` to upstream host. Fetch fails with DNS lookup error and the function 500s. ## Expected Behavior Leading `/+` collapsed before resolving against `framerUrl`. Common WordPress / exploit probes (`wp-includes`, `wp-admin`, `xmlrpc.php`, `wlwmanifest`, `.env`, `.git/`) short-circuit to 404. ## Related Issue(s) DOC-498
by Jack Hsu
Succeeded
master
ca93fb1a docs(misc): document agentic nx import flow
by Juri
Succeeded
master
b70d0524 fix(core): preserve hydrateFileMap back-compat for cached nx-cloud workers (#35502) ## Current Behavior `nx@23.0.0-beta.2` Nx Cloud V4 distributed-agent workers crash on every task with: ``` Failed to get external value at new NativeTaskHasherImpl (.../native-task-hasher-impl.js:25:23) at new InProcessTaskHasher (.../task-hasher.js:68:27) at createTaskHasher (.../create-task-hasher.js:13:16) at createOrchestrator (.../init-tasks-runner.js:86:60) at runDiscreteTasks (.../init-tasks-runner.js:114:32) at executeAndStoreTask (.../discrete-task-worker.js:1:832861) ``` #34425 ("remove redundant `allWorkspaceFiles` from the project graph pipeline") changed two helpers in `packages/nx/src/project-graph/build-project-graph.ts`: - `hydrateFileMap(fileMap, allWorkspaceFiles, rustReferences)` → `hydrateFileMap(fileMap, rustReferences)` - `getFileMap()` no longer returns `allWorkspaceFiles` Cached Nx Cloud V4 workers (e.g. `.nx/cache/cloud/2604.29.7/lib/core/runners/distributed-agent/v4/discrete-task-worker.js`) `require('nx/src/project-graph/build-project-graph')` directly and still call the 3-arg form: ```js hydrateFileMap( { projectFileMap, nonProjectFiles }, allWorkspaceFiles, // lands in rustReferences slot on beta.2 rustReferences // silently dropped ); ``` The `FileData[]` array poisons `storedRustReferences`. Later `createTaskHasher` reads `.projectFiles` / `.allWorkspaceFiles` off the array (both `undefined`), passes them to `new TaskHasher(...)`, and napi-rs throws `"Failed to get external value"` trying to coerce `undefined` into `&External<Arc<…>>`. ## Expected Behavior `hydrateFileMap` accepts both the new 2-arg shape and the legacy 3-arg shape, detected by `Array.isArray()` on the 2nd argument. `getFileMap()` re-exposes `allWorkspaceFiles: []` so cached workers that destructure it (for telemetry / `v4log`) see the property instead of `undefined`. Both surfaces are flagged `@deprecated` so we can remove them in a later major once cached V4 workers age out. A regression test pins both arities — verified red on the pre-fix code and green with the fix. ## Related Issue(s) 
by Jason Jean
Succeeded
master
33a83e1c fix(nx-dev): short-circuit bot probes in framer rewrite edge function (#35527) Some bots are hitting the server, scanning for wordpress paths. This is resulting in 500 server error, but we should return 404. This fails in prod (500): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://nx.dev//wp/wp-includes/wlwmanifest.xml' ``` Fixed in preview (404): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://deploy-preview-35527--nx-dev.netlify.app//wp/wp-includes/wlwmanifest.xml' ``` ## Current Behavior Bot scanners hit `GET //wp/wp-includes/wlwmanifest.xml` (leading `//`). `new URL(pathname, framerUrl)` parses `//wp/...` as protocol-relative, promoting `wp` to upstream host. Fetch fails with DNS lookup error and the function 500s. ## Expected Behavior Leading `/+` collapsed before resolving against `framerUrl`. Common WordPress / exploit probes (`wp-includes`, `wp-admin`, `xmlrpc.php`, `wlwmanifest`, `.env`, `.git/`) short-circuit to 404. ## Related Issue(s) DOC-498
by Jack Hsu
Failed
master
33a83e1c fix(nx-dev): short-circuit bot probes in framer rewrite edge function (#35527) Some bots are hitting the server, scanning for wordpress paths. This is resulting in 500 server error, but we should return 404. This fails in prod (500): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://nx.dev//wp/wp-includes/wlwmanifest.xml' ``` Fixed in preview (404): ``` curl -sS -o /dev/null -w "%{http_code}\n" --path-as-is 'https://deploy-preview-35527--nx-dev.netlify.app//wp/wp-includes/wlwmanifest.xml' ``` ## Current Behavior Bot scanners hit `GET //wp/wp-includes/wlwmanifest.xml` (leading `//`). `new URL(pathname, framerUrl)` parses `//wp/...` as protocol-relative, promoting `wp` to upstream host. Fetch fails with DNS lookup error and the function 500s. ## Expected Behavior Leading `/+` collapsed before resolving against `framerUrl`. Common WordPress / exploit probes (`wp-includes`, `wp-admin`, `xmlrpc.php`, `wlwmanifest`, `.env`, `.git/`) short-circuit to 404. ## Related Issue(s) DOC-498
by Jack Hsu