crxjs/chrome-extension-tools (@crxjs/vite-plugin)

\n\n### [`v2.7.1`](https://redirect.github.com/crxjs/chrome-extension-tools/blob/HEAD/packages/vite-plugin/CHANGELOG.md#271)\n\n##### Patch Changes\n\n- [`efa9c63`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/efa9c63): Update direct dependency ranges for `convert-source-map`, `debug`,\n and `fs-extra`.\n- [`6efde9d`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/6efde9d): Filter Vite 8/Rolldown-only options before the dev file writer calls\n Rollup, removing `Unknown input options: platform` warnings.\n\n### [`v2.7.0`](https://redirect.github.com/crxjs/chrome-extension-tools/blob/HEAD/packages/vite-plugin/CHANGELOG.md#270)\n\n##### Minor Changes\n\n- [`9f00943`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/9f00943): Add dev HMR support for manifest-declared MAIN world content scripts.\n\n##### Patch Changes\n\n- [`a9cc89a`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/a9cc89a): Remove unused vite-plugin dependencies and update selected dependency\n versions.\n\n### [`v2.6.1`](https://redirect.github.com/crxjs/chrome-extension-tools/blob/HEAD/packages/vite-plugin/CHANGELOG.md#261)\n\n##### Patch Changes\n\n- [`2b88621`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/2b88621): Coalesce file writer readiness waits so large dev-server graph\n updates do not repeatedly recompute the same dependency traversal. This also\n fixes late HMR readiness waits that could miss the shared ready event and\n delay content script updates.\n\n### [`v2.6.0`](https://redirect.github.com/crxjs/chrome-extension-tools/blob/HEAD/packages/vite-plugin/CHANGELOG.md#260)\n\n##### Minor Changes\n\n- [`4f5d2ec`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4f5d2ec): feat: add IIFE content script bundling\n\n Content scripts named with `.iife.ts` extension are automatically bundled as\n self-contained IIFE files with all dependencies inlined. This is useful for\n MAIN world content scripts used with `chrome.scripting.executeScript` or\n `chrome.scripting.registerContentScripts`.\n\n##### Patch Changes\n\n- [`5316e9c`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/5316e9c): Allow `chrome-extension://` and `moz-extension://` origins in Vite\n dev-server CORS automatically. This keeps extension pages able to fetch\n dev-server files on Vite releases with the stricter localhost-only CORS\n default, including Vite `4.5.6`, `5.4.12`, and `6.0.9+`, without requiring\n projects to configure `server.cors.origin` manually.\n- [`1aee9ad`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/1aee9ad): fix: dynamic content scripts failing in build --watch mode\n- [`2f8bab5`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/2f8bab5): Fix the dev-mode loading page so it waits for the requested extension\n HTML file, preserves the page URL query string, allows extension-origin\n readiness polling, and throttles automatic reloads to avoid rapid flicker.\n- [`1681511`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/1681511): Expand vite-plugin CI to run e2e tests against supported Vite\n versions and fix compatibility issues exposed by the matrix.\n- [`0593d58`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/0593d58): fix: publish ESM declarations for the Vite plugin entrypoint\n\n### [`v2.5.0`](https://redirect.github.com/crxjs/chrome-extension-tools/blob/HEAD/packages/vite-plugin/CHANGELOG.md#250)\n\n##### Minor Changes\n\n- [`4756baf`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4756baf): feat: add HMR support for CSS declared in manifest content_scripts\n\n- [`4756baf`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4756baf): add: browser_specific_settings.gecko properties\n\n- [`4756baf`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4756baf): Fix \"TypeError: plugins is not iterable\" error when using\n rolldown-vite (Vite 7).\n\n In rolldown-vite, the buildStart hook doesn't receive options.plugins. This\n fix uses the configResolved hook to get plugins from the resolved config, with\n buildStart kept as a fallback for older Vite versions.\n\n- [`4756baf`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4756baf): Fixed\n [#852](https://redirect.github.com/crxjs/chrome-extension-tools/issues/852), the plugin\n now emits a correct URL in `service-worker-loader.js` when the Vite option\n `server.https` is enabled.\n\n- [`4756baf`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4756baf): fix: resolve TypeScript types correctly for ESM and CJS consumers\n\n- [`4756baf`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4756baf): feat: add Vite 8 beta support\n\n##### Patch Changes\n\n- [`4756baf`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4756baf): ci: migrate release workflow to npm trusted publishers\n\n- [`570312a`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/570312a): fix: sanitize colons from output filenames on Windows\n\n- [`4756baf`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4756baf): fix: copy CSS files declared in manifest content_scripts to output\n\n- [`4756baf`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4756baf): Replace cheerio with node-html-parser to fix npm deprecation warning\n for whatwg-encoding.\n\n Also adds explicit vite peerDependency declaration (^3.0.0 through ^7.0.0) to\n enable proper version resolution when used with different vite versions.\n\n- [`4756baf`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4756baf): ci: run compat tests against stable Vite 8, make the vite8 available\n as a peer dependency\n\n- [`4756baf`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4756baf): fix: UnoCSS/TailwindCSS HMR issues with virtual CSS modules\n\n- [`8a99b4f`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/8a99b4f): made data_collection_permissions optional\n\n- [`4756baf`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4756baf): fix: respect user's build.manifest setting in Vite 4+\n\n When users set `build.manifest: false` in their Vite config, the Vite manifest\n file (`.vite/manifest.json` in Vite 5+, or `manifest.json` in older versions)\n is now properly removed from the output bundle.\n\n CRXJS internally requires the Vite manifest to derive content script resources\n during build, so it forces `build.manifest: true`. Previously, this meant the\n Vite manifest was always included in the output even if the user explicitly\n disabled it. Now, CRXJS removes the manifest from the bundle after processing\n if the user didn't want it.\n\n Closes [#1077](https://redirect.github.com/crxjs/chrome-extension-tools/issues/1077)\n\n- [`d364bd8`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/d364bd8): chore: upgrade chokidar to 5.0.0\n\n- [`4756baf`](https://redirect.github.com/crxjs/chrome-extension-tools/commit/4756baf): feat(client): Update the style and content of the development mode\n loading page\n\n

\n\n

figma/plugin-typings (@figma/plugin-typings)

\n\n### [`v1.140.0`](https://redirect.github.com/figma/plugin-typings/compare/v1.139.0...v1.140.0)\n\n[Compare Source](https://redirect.github.com/figma/plugin-typings/compare/v1.139.0...v1.140.0)\n\n### [`v1.139.0`](https://redirect.github.com/figma/plugin-typings/compare/v1.138.0...v1.139.0)\n\n[Compare Source](https://redirect.github.com/figma/plugin-typings/compare/v1.138.0...v1.139.0)\n\n

\n\n

figma/rest-api-spec (@figma/rest-api-spec)

\n\n### [`v0.43.0`](https://redirect.github.com/figma/rest-api-spec/compare/v0.42.0...2a90e5adc67d8117d7c2da624f03a9bfa3027fb6)\n\n[Compare Source](https://redirect.github.com/figma/rest-api-spec/compare/v0.42.0...2a90e5adc67d8117d7c2da624f03a9bfa3027fb6)\n\n### [`v0.42.0`](https://redirect.github.com/figma/rest-api-spec/compare/v0.41.0...v0.42.0)\n\n[Compare Source](https://redirect.github.com/figma/rest-api-spec/compare/v0.41.0...v0.42.0)\n\n### [`v0.41.0`](https://redirect.github.com/figma/rest-api-spec/compare/v0.40.0...v0.41.0)\n\n[Compare Source](https://redirect.github.com/figma/rest-api-spec/compare/v0.40.0...v0.41.0)\n\n

\n\n

jsverse/transloco (@jsverse/transloco)

\n\n### [`v8.4.0`](https://redirect.github.com/jsverse/transloco/blob/HEAD/CHANGELOG.md#840-2026-06-13)\n\n[Compare Source](https://redirect.github.com/jsverse/transloco/compare/bd284ecd5e14ee6b5cbee0d84e3432a749e49d6a...b2b52b3bbcb4d958522e3ccee3e64e422555f8c5)\n\n##### 🚀 Features\n\n- **transloco:** transpile function arguments in FunctionalTranspiler\n\n##### 🩹 Fixes\n\n- translateSignal utility missing injector for toSignal\n- **transloco-scoped-libs:** multi-scope i18n with join strategy\n\n##### ❤️ Thank You\n\n- Dafnik\n- f-aubert\n- Ilshat Khamitov\n\n

\n\n

microsoft/tsdoc (@microsoft/tsdoc)

\n\n### [`v0.17.1`](https://redirect.github.com/microsoft/tsdoc/blob/HEAD/tsdoc/CHANGELOG.md#0171)\n\nTue, 29 Sep 2026 18:52:33 GMT\n\n##### Patches\n\n- Add missing tsdoc-unsupported-html-name to TSDocConfiguration.allTsdocMessageIds so eslint-plugin-tsdoc does not crash when reportUnsupportedHtmlElements is enabled (GitHub [#453](https://redirect.github.com/microsoft/tsdoc/issues/453))\n- Fix an issue where `TSDocEmitter` dropped a line break that appeared before an inline node such as a code span, `{@link}` tag, or HTML element, joining the adjacent words.\n\n### [`v0.17.0`](https://redirect.github.com/microsoft/tsdoc/blob/HEAD/tsdoc/CHANGELOG.md#0170)\n\nWed, 16 Sep 2026 01:24:29 GMT\n\n##### Minor changes\n\n- Update emitter to not replace line breaks\n\n

\n\n

modelcontextprotocol/typescript-sdk (@modelcontextprotocol/client)

\n\n### [`v2.2.0`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/releases/tag/%40modelcontextprotocol/client%402.2.0)\n\n[Compare Source](https://redirect.github.com/modelcontextprotocol/typescript-sdk/compare/@modelcontextprotocol/client@2.1.0...@modelcontextprotocol/client@2.2.0)\n\n##### Minor Changes\n\n- [#2887](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2887) [`edd12e2`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/edd12e282620ebf770d67316f19cf91d4112a1bd) Thanks [@maxisbey](https://redirect.github.com/maxisbey)! - Constructing `ClientCredentialsProvider`, `PrivateKeyJwtProvider`, `StaticPrivateKeyJwtProvider` or `CrossAppAccessProvider` without `expectedIssuer` is deprecated: the constructor logs one `console.warn` and that call signature is marked `@deprecated`. Behaviour is otherwise unchanged. Pass the `issuer` of the authorization server the credentials were registered with.\n\n `fetchToken()` throws `AuthorizationServerMismatchError`, before sending anything, when the provider's client information is bound to a different authorization server than the one it is called with. The `AuthorizationServerMismatchError` message no longer assumes the authorization-code callback; its fields are unchanged.\n\n `OAuthTokensSchema` and `OAuthClientInformationSchema` accept the optional `issuer` stamp, so a provider that reads storage back through them keeps it. `auth()` overwrites it on every save.\n\n##### Patch Changes\n\n- [#2885](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2885) [`9dd722f`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/9dd722fd0b533b3cb44cd2834409f7ea4dd32b00) Thanks [@claude](https://redirect.github.com/apps/claude)! - Sending a notification on a closed connection no longer produces a briefly unhandled promise rejection (seen as `unhandledrejection` on Cloudflare Workers) in addition to the returned rejection.\n\n- [#2883](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2883) [`c0f7aec`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/c0f7aec2925a46b32dc2f2aad5bf636a36f02c78) Thanks [@claude](https://redirect.github.com/apps/claude)! - Fix a type-check failure for CommonJS TypeScript projects introduced in 2.1.0: `dist/index.d.cts` imported types from `jose`, which is ESM-only, so `tsc` with `module: node16`/`node18` and `skipLibCheck: false` failed with TS1479. The two `jose` types used by the DPoP API (`CryptoKey`, `JWK`) are now inlined into the declaration files. No runtime change.\n\n- [#2768](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2768) [`efebf5b`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/efebf5b2ba2f07c6fa27ada824a0999b801fec0a) Thanks [@web-abin](https://redirect.github.com/web-abin)! - Correct the JSDoc for insecure OAuth token endpoints. The TLS requirement comes from the MCP authorization specification's OAuth 2.1 communication-security rules, not SEP-2207, which covers OIDC-flavored refresh-token guidance. Documentation only; no runtime behavior change.\n\n- [#2729](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2729) [`a4ae2f9`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/a4ae2f98da3814a9290f2791cfcca8148dcec978) Thanks [@claude](https://redirect.github.com/apps/claude)! - Correct the `registerClient` `@deprecated` notice: Dynamic Client Registration was deprecated by spec PR [#2858](https://redirect.github.com/modelcontextprotocol/typescript-sdk/issues/2858) (Client ID Metadata Documents), not SEP-2577 (which deprecates roots, sampling, and logging). The notice now also names the earliest possible removal date under the feature lifecycle policy (2027-07-28) and clarifies that the `client_id_metadata_document_supported` gating lives in the built-in `auth()` flow — `registerClient` called directly always sends the registration request. Documentation only; no runtime behavior change.\n\n- [#2862](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2862) [`e780e13`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/e780e13869ad419a864b669bd5fa9702cfb36b14) Thanks [@SyedTashfin](https://redirect.github.com/SyedTashfin)! - Preserve `_meta` on `input_required` results. The 2026-07-28 decode seam rebuilt the payload from `inputRequests` and `requestState` only, so result-level metadata a server sent on an `input_required` result (including `io.modelcontextprotocol/serverInfo`) was dropped before an `allowInputRequired: true` caller could see it. `Result._meta` is a result-level field, so `input_required` carries it exactly like any other result.\n\n- [#2886](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2886) [`ef39308`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/ef39308e963496b75e50553f6265d99cacb4fbb9) Thanks [@claude](https://redirect.github.com/apps/claude)! - `listTools()`, `listPrompts()`, `listResources()` and `listResourceTemplates()` called without a cursor now follow `nextCursor` until the server stops sending one, instead of stopping silently with a short list when a cursor repeats; a page that has the same items and the same `nextCursor` as the page before it ends the walk and is not added twice, and `listMaxPages` still caps the walk.\n\n- [#2642](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2642) [`cfa09db`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/cfa09db614308eaf4fd575c89833da8878d4acb7) Thanks [@claude](https://redirect.github.com/apps/claude)! - Fix `Client.listen()` rejections escaping as process-level unhandled rejections. The internal `opening` promise could reject (ack timeout, transport close, server cancel, caller abort) while `listen()` was still serially awaiting `transport.send(...)`, so no rejection handler was attached yet — the rejection surfaced as an `unhandledRejection` that caller-side handling cannot prevent, and a send that never settles (e.g. a stdio write parked on `'drain'`) left `listen()` suspended forever even though the ack timer had already fired. `listen()` now suspends on the `opening` state machine directly and routes send failures into it, so every termination path rejects the returned promise and nothing escapes.\n\n- [#2597](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2597) [`7f7a94c`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/7f7a94c22017e121a960e071bb50ec75e34450bd) Thanks [@arimu1](https://redirect.github.com/arimu1)! - Treat hostnames ending in `.localhost` as loopback for the SEP-2207 token-endpoint https guard (RFC 6761 §6.3), so host-based multi-tenant local OAuth works. The SDK does not resolve the name itself: `*.localhost` reaches the local machine only if the system resolver follows RFC 6761.\n\n- Updated dependencies \\[[`edd12e2`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/edd12e282620ebf770d67316f19cf91d4112a1bd)]:\n - [@modelcontextprotocol/core](https://redirect.github.com/modelcontextprotocol/core)@2.2.0\n\n### [`v2.1.0`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/releases/tag/%40modelcontextprotocol/server%402.1.0)\n\n[Compare Source](https://redirect.github.com/modelcontextprotocol/typescript-sdk/compare/@modelcontextprotocol/client@2.0.0...@modelcontextprotocol/client@2.1.0)\n\n##### Minor Changes\n\n- [#1624](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/1624) [`6032170`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/60321700871029401a2e3bed8fdf4f02c9ec3331) Thanks [@SamMorrowDrums](https://redirect.github.com/SamMorrowDrums)! - Add request-time OAuth scope challenges for tools, resources, resource templates,\n and prompts. Each primitive's `scopeChallenge` callback receives the parsed\n request and verified authentication info, then either continues or returns the\n exact scope set for an `insufficient_scope` response. `requireScopes` provides a\n small helper for static all-of checks.\n\n `createMcpHandler` and Streamable HTTP transports return HTTP 403 with an\n `insufficient_scope` challenge before handler execution or SSE setup. The\n preflight is active whenever a registered primitive carries a `scopeChallenge`\n callback — there is no handler- or transport-level configuration. The\n challenge's `WWW-Authenticate` header is built by the same formatter as the\n bearer-auth 401/403 answers, and its `resource_metadata` parameter is derived\n from the verified `AuthInfo`: `requireBearerAuth` / `verifyBearerToken` now\n stamp their configured `resourceMetadataUrl` onto the `AuthInfo` they return\n (new optional `AuthInfo.resourceMetadataUrl` field), with a fallback to the\n well-known location for an HTTP(S) RFC 8707 `resource` identifier; the\n parameter is omitted when neither is available.\n\n##### Patch Changes\n\n- [#2726](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2726) [`6fa4227`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/6fa42279fecaba423635072f716bbb2f6f7c77f3) Thanks [@LuckTerence](https://redirect.github.com/LuckTerence)! - `SdkError` and `SdkHttpError` accept standard `ErrorOptions` as an optional fourth constructor argument and forward it to `Error`, so a wrapped error is reachable through the standard `Error.cause` chain. Version-negotiation probe failures (`SdkErrorCode.EraNegotiationFailed`) now use it: the underlying `TypeError: fetch failed` and the DNS or socket error beneath it surface via `error.cause`, so pino, Sentry, and `util.inspect` render `ENOTFOUND` / `ECONNREFUSED` / `ETIMEDOUT` instead of stopping at the `SdkError` ([#2657](https://redirect.github.com/modelcontextprotocol/typescript-sdk/issues/2657)). The previous `error.data.cause` slot is still populated for compatibility but is deprecated and slated for removal; read `error.cause` instead.\n\n- [#2654](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2654) [`03842cd`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/03842cd9cae9a9b142c77d2fb65e829fc4e03eab) Thanks [@pshah19](https://redirect.github.com/pshah19)! - Treat request id `0` as a real id. Two guards tested a `RequestId` for truthiness, so the legal JSON-RPC ids `0` and `''` were read as absent. Id `0` is not a corner case: the outbound request counter is zero-based, so it is the first id every peer assigns, which on the server→client leg is the first `sampling/createMessage`, `elicitation/create`, or `roots/list` a server sends.\n\n - `notifications/cancelled` carrying id `0` was ignored, and the in-flight handler ran to completion with its `AbortSignal` never fired.\n - A notification sent with `relatedRequestId: 0` wrongly passed the debounce gate (for methods opted into `debouncedNotificationMethods`). Because the pending set is keyed by method alone, a second such notification in the same tick was silently dropped rather than sent.\n\n Absent is now the only value that means \"no id\".\n\n- [#2668](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2668) [`3e90449`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/3e90449fd52997da43b79a536d2c19c446603cc7) Thanks [@KKonstantinov](https://redirect.github.com/KKonstantinov)! - Stop sending `notifications/cancelled` for the `initialize` handshake. The spec is explicit that a client MUST NOT attempt to cancel its `initialize` request, but the outbound cancel path fired for any in-flight request: aborting the `AbortSignal` passed to `connect()`, or letting the handshake hit its timeout, put a forbidden cancellation on the wire naming the initialize request id.\n\n The local behaviour is unchanged — the caller's promise still rejects with the same abort/timeout error, and `connect()` still tears the connection down. Only the wire notification is suppressed. Every other method keeps the existing cancellation path.\n\n- [#2698](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2698) [`7b781ed`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/7b781ed4e25355a25d15974f3c76de81299694ed) Thanks [@maxisbey](https://redirect.github.com/maxisbey)! - Read Streamable HTTP request bodies with a size limit. Every SDK-owned body read —\n `WebStandardStreamableHTTPServerTransport` (and the Node transport built on it),\n `createMcpHandler`, `toNodeHandler`, and `createMcpHonoApp`'s JSON pre-parse — now stops at\n 4 MiB by default (the limit the legacy SSE transport already uses; the Express adapter and stdio\n bound their reads too) and answers `413 Payload Too Large` before anything is parsed.\n `toWebRequest` (when it reads the Node stream itself) now rejects once the body exceeds the\n limit with an error whose `name` is `'RequestBodyTooLargeError'` and `status` is `413`, and\n `toNodeHandler` answers that with `413`; hand-wired callers of `toWebRequest` should handle the\n rejection or pass a pre-parsed body, and `isLegacyRequest` reports such a request as non-legacy\n so the modern handler answers it. JSON-RPC batch arrays are limited to 100 messages; a longer\n batch is answered `400` / `-32600` and none of it is dispatched.\n\n The limit is configurable with a new `maxRequestBodySize` option (bytes, default\n `DEFAULT_MAX_REQUEST_BODY_SIZE` = 4 MiB, exported from `@modelcontextprotocol/server`) on\n `WebStandardStreamableHTTPServerTransportOptions`, `CreateMcpHandlerOptions` (forwarded to its\n stateless legacy leg; `isLegacyRequest` and `legacyStatelessFallback` take the same option),\n `CreateMcpHonoAppOptions`, and `ToNodeHandlerOptions` / `ToWebRequestOptions` (the adapter's\n bound applies before the handler's, so raise both). The bounded reader is exported as\n `readRequestBody` for adapter authors. Hosts that pre-parse the body and pass it as\n `parsedBody` skip the SDK's read and its size limit entirely; the batch bound applies either way.\n\n `createMcpHonoApp` and `createMcpExpressApp` now run their Host/Origin validation before the\n JSON body parser, so a request from a disallowed Host or Origin with an invalid JSON body is\n answered `403` rather than `400`, and its body is not read.\n\n- [#2590](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2590) [`75dc7ea`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/75dc7ea6e2913e1ac37d4f06eec62cd5cfac9e7a) Thanks [@davidpavlovschi](https://redirect.github.com/davidpavlovschi)! - Reject a modern (2026-07-28) POST that omits the required `MCP-Protocol-Version` header.\n\n `createMcpHandler` accepted a request whose body carried a valid per-request `_meta`\n envelope but whose `MCP-Protocol-Version` header was absent: the request was classified\n modern, dispatched, and answered `200` — tool handlers ran. Only the *mismatch* case\n (header present, disagreeing with the body) was rejected, so of the standard headers\n SEP-2243 requires on a modern POST, presence was enforced for `Mcp-Method` (and for\n `Mcp-Name` on the methods that mirror `params.name` / `params.uri`) but not for\n `MCP-Protocol-Version`.\n\n Such a request is now refused with `400 Bad Request` and JSON-RPC `-32020`\n (`HeaderMismatch`), matching the shape the sibling missing-header cells already emit and\n echoing the request id — per the Streamable HTTP spec, which requires the header on every\n POST and lists a missing required standard header as a `HeaderMismatch` failure. The\n spec's allowance to treat a header-less request as `2025-03-26` is available only to a\n server that also serves pre-2025-06-18 clients, and permits routing it to *legacy*\n handling — never serving it as 2026-07-28; under `legacy: 'reject'` the requirement is\n unconditional.\n\n Era classification is deliberately unchanged and stays body-primary: a proxy that strips\n the header still must not change the era, so such a request is still *classified* modern\n and is refused one rung later, at `standard-header-validation` — the same rung that\n already answers a missing `Mcp-Method`. Legacy-era traffic is untouched, notifications\n are unaffected, body-less `GET` / `DELETE` session operations are method-routed before\n any header validation, and stdio serving (which has no HTTP headers) is not involved.\n\n Clients built with this SDK always send the header, so no first-party client is affected;\n hand-rolled clients that omitted it must add it.\n\n- [#2494](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2494) [`6a05402`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/6a054025e8cebaecead76fb51d92ba3974e8d091) Thanks [@claude](https://redirect.github.com/apps/claude)! - `StdioServerTransport` now closes itself and fires `onclose` when its stdin ends or closes. The stdio binding says servers \"SHOULD exit promptly when their standard input is closed\" — stdin EOF is the primary graceful-shutdown signal, and on some platforms (notably Windows, where no signal is delivered when the parent goes away) the only reliable one. Previously the transport listened only for `data` and `error`, so when an MCP client hung up its end of the pipe (window closed, session restarted, host crashed) the server never noticed: `onclose` never fired, nothing tore down, and server processes accumulated as zombies until killed by hand. The transport now attaches `end`/`close` listeners on stdin that close the transport (idempotently — `onclose` still fires exactly once if `close()` is also called), so `Server`/`McpServer` and `serveStdio` tear down through the existing `onclose` chain and a well-behaved server process exits naturally. Requests still in flight when stdin ends are aborted (their handlers observe `signal.aborted`) and their responses are not written: EOF means the client has hung up and is no longer waiting. A client that wants answers keeps stdin open until it has read them.\n\n- [#2613](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2613) [`70de0c8`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/70de0c8b569b0d664a56b90be2f141d1d1645880) Thanks [@jwcarman](https://redirect.github.com/jwcarman)! - Emit and validate the `Mcp-Name` header for tasks requests per SEP-2663's Streamable HTTP binding: the client transport now mirrors `params.taskId` into `Mcp-Name` on `tasks/get` / `tasks/update` / `tasks/cancel` (previously omitted, causing conforming servers to reject every task poll with `-32020 HeaderMismatch`), and the server-side standard-header validation cross-checks it via the same shared `MCP_NAME_HEADER_SOURCE` table.\n\n On the server, `createMcpHandler` now answers a modern (2026-07-28) `tasks/get` / `tasks/update` / `tasks/cancel` POST that omits `Mcp-Name`, or whose header disagrees with `params.taskId`, with `400` / `-32020` (`HeaderMismatch`) at the `standard-header-validation` rung, the same treatment `tools/call` / `prompts/get` / `resources/read` already get. Legacy-era (2025-11-25) tasks traffic is unaffected. Clients built with this SDK release send the header; hand-rolled clients that omitted it must add it.\n\n- Updated dependencies \\[[`dcc0102`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/dcc01028ff6a499a5728c2b6181c1727d52e2fab)]:\n - [@modelcontextprotocol/core](https://redirect.github.com/modelcontextprotocol/core)@2.1.0\n\n

\n\n

OpenAPITools/openapi-generator-cli (@openapitools/openapi-generator-cli)

\n\n### [`v2.41.0`](https://redirect.github.com/OpenAPITools/openapi-generator-cli/releases/tag/v2.41.0)\n\n[Compare Source](https://redirect.github.com/OpenAPITools/openapi-generator-cli/compare/v2.40.1...v2.41.0)\n\n##### Features\n\n- **release:** v7.25.0 release ([#1278](https://redirect.github.com/OpenAPITools/openapi-generator-cli/issues/1278)) ([b6cef74](https://redirect.github.com/OpenAPITools/openapi-generator-cli/commit/b6cef74bd28bd914ed700ad1b61c7839d5ec20b4))\n\n### [`v2.40.1`](https://redirect.github.com/OpenAPITools/openapi-generator-cli/releases/tag/v2.40.1)\n\n[Compare Source](https://redirect.github.com/OpenAPITools/openapi-generator-cli/compare/v2.40.0...v2.40.1)\n\n##### Bug Fixes\n\n- **deps:** update dependency fs-extra to v11.4.0 ([#1264](https://redirect.github.com/OpenAPITools/openapi-generator-cli/issues/1264)) ([254a7d5](https://redirect.github.com/OpenAPITools/openapi-generator-cli/commit/254a7d5ca748970f56f1ca1f11287213a98e3928))\n\n### [`v2.40.0`](https://redirect.github.com/OpenAPITools/openapi-generator-cli/releases/tag/v2.40.0)\n\n[Compare Source](https://redirect.github.com/OpenAPITools/openapi-generator-cli/compare/v2.39.1...v2.40.0)\n\n##### Features\n\n- **release:** v7.24.0 release ([#1259](https://redirect.github.com/OpenAPITools/openapi-generator-cli/issues/1259)) ([a241dc9](https://redirect.github.com/OpenAPITools/openapi-generator-cli/commit/a241dc9027c0f93d0c890e103782b1deda8ff946))\n\n

\n\n

Redocly/redocly-cli (@redocly/openapi-core)

\n\n### [`v2.57.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.57.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.56.1...@redocly/openapi-core@2.57.0)\n\n##### Minor Changes\n\n- Added `const` checking to the `no-enum-type-mismatch` rule: a `const` value must conform to the schema's `type`, the same way every `enum` value does.\n\n **Note**: linting output may include new errors for schemas whose `const` value doesn't match their `type`.\n\n##### Patch Changes\n\n- Fixed an issue where `no-enum-type-mismatch` dropped violations and reported a wrong location when `type` was written as an array.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.57.0.\n\n### [`v2.56.1`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.56.1)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.56.0...@redocly/openapi-core@2.56.1)\n\n##### Patch Changes\n\n- Improved overall startup performance.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.56.1.\n\n### [`v2.56.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.56.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.55.0...@redocly/openapi-core@2.56.0)\n\n##### Minor Changes\n\n- Added support for applying Overlay documents to the `bundle` command output.\n Pass overlays with the new `--overlay` option or list them under `overlays` for an API in `redocly.yaml`.\n- Added support for linting Overlay 1.1 and 1.2 documents, including the `copy` action field, the `$self` field, and reusable actions in `components.actions`.\n The `spec-ref-siblings` rule now checks the fields next to a reusable action `$ref` in Overlay documents.\n\n##### Patch Changes\n\n- Fixed an issue where `respect` failed with an unexpected error when a step used an `operationId` without the `$sourceDescriptions..` prefix and the Arazzo file also listed an `arazzo` source description.\n Such `operationId`s are looked up in the `openapi` source descriptions only.\n- Updated `undici` to the `6.29.0` version.\n- Updated [@redocly/client-generator](https://redirect.github.com/redocly/client-generator) to v0.4.18.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.56.0.\n- Updated [@redocly/respect-core](https://redirect.github.com/redocly/respect-core) to v2.56.0.\n- Updated [@redocly/reunite-integration](https://redirect.github.com/redocly/reunite-integration) to v2.56.0.\n\n### [`v2.55.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.55.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.54.3...@redocly/openapi-core@2.55.0)\n\n##### Minor Changes\n\n- Added the `--replace` option to the `push` command.\n `--replace` removes the files under the mount path that are not part of the push.\n\n##### Patch Changes\n\n- Fixed `respect` so known secrets are masked in non-JSON request bodies, such as `application/x-www-form-urlencoded` token requests.\n- Fixed `respect` so a step fails with a clear error when a runtime expression embedded in a string has no value, such as `Bearer {$outputs.accessToken}`.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.55.0.\n- Updated [@redocly/respect-core](https://redirect.github.com/redocly/respect-core) to v2.55.0.\n- Updated [@redocly/reunite-integration](https://redirect.github.com/redocly/reunite-integration) to v2.55.0.\n- Fixed an issue where the `workflow-dependsOn` rule reported a duplicate when different workflows listed the same workflow in `dependsOn`.\n\n### [`v2.54.3`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.54.3)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.54\n\n> ❗ **Important**\n> \n> ✂ PR body was truncated to here.\n\n\n

\n\n---\n\n### Configuration\n\n📅 **Schedule**: (in timezone Europe/Paris)\n\n- Branch creation\n - At any time (no schedule defined)\n- Automerge\n - At any time (no schedule defined)\n\n🚦 **Automerge**: Enabled.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.\n\n👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://redirect.github.com/renovatebot/renovate/discussions) if that's undesired.\n\n---\n\n - [ ] If you want to rebase/retry this PR, check this box\n\n---\n\nThis PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/AmadeusITGroup/otter).\n\n","21ba2dc7d3ac95efab03d7578abc7b84cbc84bfc","b25d067c5294127bde11a8f14023372e03b2ff54",{"_446":447,"_448":449,"_450":451,"_452":453,"_454":455,"_456":457,"_458":-5,"_459":-5,"_460":461,"_462":463,"_464":453,"_465":466,"_467":468,"_469":-5,"_470":471,"_472":-5,"_473":-5,"_474":-5,"_475":-5,"_148":476,"_477":478,"_479":480,"_388":481,"_482":483,"_484":-5,"_485":-5,"_486":-5,"_487":-5,"_488":-5,"_489":-5,"_490":-5,"_491":-5,"_492":-5,"_493":494,"_495":496,"_497":498,"_499":500,"_501":-5,"_502":500},"suggestedFixId","6ac6562fd10bc06543d12097","fixedTasks",[503],"otherFailedTasks",[],"verificationStatus","COMPLETED","verificationTasksExecuted",[503],"userAction","NONE","userActionOrigin","userCommitMessage","suggestedFix","diff --git a/apps/chrome-devtools/src/app-components/app.ts b/apps/chrome-devtools/src/app-components/app.ts\nindex 2e256df01..27f94d721 100644\n--- a/apps/chrome-devtools/src/app-components/app.ts\n+++ b/apps/chrome-devtools/src/app-components/app.ts\n@@ -157,7 +157,7 @@ export class App {\n /* eslint-enable @typescript-eslint/restrict-template-expressions */\n }\n \n- private updateSelectedComponentInfo(info?: OtterLikeComponentInfo) {\n+ private updateSelectedComponentInfo(info?: OtterLikeComponentInfo, _exceptionInfo?: chrome.devtools.inspectedWindow.EvaluationExceptionInfo) {\n this.selectedComponentInfo.next(info);\n this.cd.detectChanges();\n }\n","suggestedFixDescription","fix(chrome-devtools): adapt eval callback to new @types/chrome signature","suggestedFixStatus","suggestedFixReasoning","The @types/chrome bump from ^0.1.0 to ^0.3.0 changed the typing of the `chrome.devtools.inspectedWindow.eval` callback.\nIt now receives `(result, exceptionInfo)` as a tuple union, instead of a single `result` argument.\n\n`updateSelectedComponentInfo(info?: OtterLikeComponentInfo)` in apps/chrome-devtools/src/app-components/app.ts took only one parameter.\nIt was therefore no longer assignable to the callback type, which caused TS2769 at app.ts:155.\n\nThe handler now declares a second optional parameter, `_exceptionInfo?: chrome.devtools.inspectedWindow.EvaluationExceptionInfo`.\nThis uses the library's own exported type, so type safety is kept and no `any` or `@ts-ignore` is involved.\nThe runtime behavior is unchanged: the handler still calls `next(info)` and `detectChanges()`.\n\nNo SELF_HEALING.md or predefined fix rules exist in the repo, and no similar failure was found on other branches.\nAfter the change, `yarn nx build-components chrome-devtools` ran successfully.","suggestedFixExecutionTime",181418,"verificationExecutionTime","reviewComment","We fixed our build by widening the `updateSelectedComponentInfo` callback in the chrome-devtools app so it also accepts the `exceptionInfo` argument. The updated @types/chrome typings now call the `inspectedWindow.eval` callback with `(result, exceptionInfo)`, which our one-parameter handler no longer matched. With this change the TS2769 error is gone, and `build-components` for chrome-devtools now completes successfully.","originalSuggestedFix","originalSuggestedFixDescription","originalSuggestedFixReasoning","userActionRecordedAt",["D",1791383087271],"suggestedAt",["D",1791383087271],"verifiedAt",["D",1791383093457],"2hTZ","failureClassification","code_change","fileModeMap","suggestedFixFailureReason","suggestedFixFailureReasonDetails","suggestedFixFailureReasonType","assignedAgentName","autoApplySkipped","autoApplySkipReason","flakyRerunSkipped","flakyRerunPending","confidence",9,"confidenceReasoning","The fix is a single-line signature change in one file, and only one task failed. The error pointed directly at the handler, and the library's own exported type is used. The rerun of chrome-devtools:build-components passed. An alternative such as an inline lambda would work too, but this is the most natural fix and does not change runtime behavior.","fixApplicationAttempts",[],"taskOutputSummary","TASK ID: chrome-devtools:build-components\n❯ Building...\n✔ Building...\nApplication bundle generation failed. [9.315 seconds] - 2026-10-07T14:19:57.053Z\n\n✘ [ERROR] TS2769: No overload matches this call.\n Overload 1 of 3, '(expression: string, options?: EvalOptions | undefined): Promise', gave the following error.\n Type '(info?: OtterLikeComponentInfo | undefined) => void' has no properties in common with type 'EvalOptions'.\n Overload 2 of 3, '(expression: string, callback: (...args: [result: undefined, exceptionInfo: EvaluationExceptionInfo] | [result: OtterLikeComponentInfo | undefined, exceptionInfo: undefined]) => void): void', gave the following error.\n Argument of type '(info?: OtterLikeComponentInfo | undefined) => void' is not assignable to parameter of type '(...args: [result: undefined, exceptionInfo: EvaluationExceptionInfo] | [result: OtterLikeComponentInfo | undefined, exceptionInfo: undefined]) => void'.\n Types of parameters 'info' and 'args' are incompatible.\n Type '[result: undefined, exceptionInfo: EvaluationExceptionInfo] | [result: OtterLikeComponentInfo | undefined, exceptionInfo: undefined]' is not assignable to type '[info?: OtterLikeComponentInfo | undefined]'.\n Type '[result: undefined, exceptionInfo: EvaluationExceptionInfo]' is not assignable to type '[info?: OtterLikeComponentInfo | undefined]'.\n Source has 2 element(s) but target allows only 1. [plugin angular-compiler]\n\n /home/runner/work/otter/otter/apps/chrome-devtools/src/app-components/app.ts:155:6:\n 155 │ this.updateSelectedComponentInfoCallback\n ╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n\n","remoteTaskSummary","localTaskSummary","chrome-devtools:build-components",{"_505":503,"_506":507,"_508":-5,"_509":-5,"_510":-5,"_511":-5},"taskName","runLinkId","N1y9Pekfsu","dteExecutionId","agentName","launchTemplates","taskTarget","AmadeusITGroup",["D",1676054118998],["D",1681913345534],"allowedEmailDomains",[574],"planActivationDate",["D",1686144031537],"isEligibleForProTrial","planLimits",{"_560":561,"_562":563,"_564":423,"_565":347,"_566":347,"_567":568,"_569":570,"_571":570,"_572":573},"isAiEnabled","planTransitions",[],"id","memberships",[540,541,542,543,544,545,546,547],"privateCloudInstallationId","hasBillingInformation","hasLicense","isUnclaimed","isOnTrial","isHighPriority","vcsProfileLink","vcsConfiguration","lastMembersSyncedAt","isAiBringYourOwnKey","enterpriseTrial","disabledReasonMessage",{"_548":559,"_550":551},{"_548":558,"_550":553},{"_548":557,"_550":551},{"_548":556,"_550":553},{"_548":555,"_550":553},{"_548":554,"_550":553},{"_548":552,"_550":553},{"_548":549,"_550":551},"userId","63eb8f0c1147ed000ed89147","role","admin","656f2a38d8c7f6f8d5bfdab5","member","64a51a42097e04000dcff5a3","63f5d0d76abadd000e2a636a","63ee2a741147ed000ed892b0","63ecec5bd91fa9000e2ebaa1","63ecec62d91fa9000e2ebaa3","63e68de49bae37000e41c9c6","baseIncludedCredits",300000,"additionalCredits",{},"discountedCreditsMaximum","contributorLimit","concurrentConnectionLimit","runsLimit",1000000,"adminUserLimit",9999,"workspaceLimit","modifiers",[],"amadeus.com",["D",1791382259587],["D",1791383327734],["D",1791383327734],[],[],[],[],{},{},{},{"_77":586,"_79":-5},{"_90":587,"_92":588,"_94":589,"_96":590},{"_129":611,"_131":612,"_133":613},{"_121":605,"_123":606},{"_104":594,"_106":595,"_80":596,"_82":597},{"_98":591},[592],{"_73":101,"_102":593,"_79":-5},[],[604],[],[601],[598],{"_73":111,"_102":599,"_79":-5},{"_113":114,"_86":600},[],{"_73":111,"_102":602,"_79":-5},{"_113":117,"_118":603},[],{"_73":111,"_102":22,"_79":-5},[609],[607],{"_73":111,"_102":608,"_79":-5},[],{"_73":111,"_102":610,"_79":-5},[],[617],[616],[614],{"_73":101,"_102":615,"_79":-5},[],{"_73":101,"_102":22,"_79":-5},{"_73":101,"_102":139,"_79":-5},["D",1791382259587],["D",1791383328515],["D",1791383327734],[635],{"_188":294,"_295":294,"_296":297,"_298":299,"_300":-5,"_301":-5,"_302":303,"_304":305,"_306":307,"_308":309,"_310":311,"_312":313,"_314":315,"_316":317,"_318":-5,"_319":-5},[],[225,226,227,228,229,230,231,232,233,234,235,236,237,238,239,240,241,242,243,244,245,246,247,248,249,250,251,252,253,254,255,256,257,258,259,260,261,262,263,264,265,266,267,268,269,270,271,272,273,274,275,276,23,277,278,279,280,281,282,283,284,285,286,287,288,289,290,291,292,293],[],{"_41":629,"_43":630,"_45":28},{"_219":220,"_221":222,"_223":628},["D",1791382591696],{"_62":-5,"_63":-5},{"_46":22,"_47":22,"_48":22,"_49":28,"_50":22,"_51":631,"_53":-5,"_54":-5,"_55":632,"_57":633,"_59":634,"_61":-5},[],[],[],[],{"_79":146,"_15":147,"_148":575,"_150":576,"_152":577,"_154":155,"_156":-5,"_157":22,"_158":-5,"_159":-5,"_160":-5,"_161":578,"_163":22,"_164":165,"_166":28,"_167":636,"_169":580,"_80":581,"_172":-5,"_173":582,"_175":637,"_177":584,"_179":-5,"_180":28,"_181":182,"_183":585},[],{},["D",1676055838344],"type","PRIMARY","publicCloudCounterpartId","privateCloudCounterpartId","installationSource","user","remoteSourceIntegrationType","GITHUB_EVENTLESS","featureMarkers",{"_681":22,"_682":28,"_683":22},"manualSetAccessLevel","idAccessLevel","READ_ONLY","patAccessLevel",{"_674":317,"_675":676,"_677":678,"_679":680},"flakyTaskConfiguration",{"_670":671,"_672":673},"aiTaskFixingConfiguration",{"_46":22,"_47":22,"_48":22,"_49":28,"_50":22,"_51":666,"_54":-5,"_55":667,"_57":668,"_59":669},"enableWorkspaceDataCaching","showVcsStatusChecks","defaultBranch","main","visibility","ALLOW_UNAUTHENTICATED","sandboxingConfiguration","launchTemplate",[],[],[],[],"threshold","NORMAL","samplePeriodDays",28,"provider","repositoryFullName","AmadeusITGroup/otter","repositoryId","589619867","repositoryVisibility","PUBLIC","isRemoteCachingActive","isDistributedTaskExecutionActive","isVCSIntegrationActive","currentUser","currentHostname","cloud.nx.app","incident",["P",688],"notifications",["P",690],"isSystemAdmin","isSingleTenant","isPATExpiryAfterLoginEnabled","isOrganizationAccessEnabled","isExecutiveReportDisabled","loginas","repositoryAccessProvidersToOffer",[],"redirectTo","/cipes/6ac652f3b0b52c84e7e7ed42/configurations/nx-agents?runGroup=37633939677-1","deferredUserOrganizations",["P",702],"sidebarCollapsed","toast","currentUserId","currentUserEmail","signedInUser","isImpersonating","isBotRequest","ENV",{"_773":22,"_351":28,"_774":22,"_775":22,"_776":22,"_777":778,"_779":780,"_781":28,"_782":783,"_784":785,"_715":786},"posthogBootstrap",{"_743":744,"_745":746},"ultracacheUiEnabled","pylon",{"_735":736,"_737":738,"_71":739,"_740":-7,"_741":742},"requestInfo",{"_719":720,"_84":350,"_88":721,"_722":723,"_724":725},"hints",{"_728":731,"_733":734},"/cipes/6ac652f3b0b52c84e7e7ed42/configurations/nx-agents","url","https://cloud.nx.app/cipes/6ac652f3b0b52c84e7e7ed42/configurations/nx-agents","userPreferences",{"_726":727},"theme",{"_71":182,"_728":729,"_730":731,"_732":731},"variant","system","resolvedVariant","light","clientColorScheme","timeZone","UTC","appId","a1074fe2-8172-4ebd-9889-879f8308a0a2","email","3dff056d-31b5-4e41-96dc-264ac376fcf1@nxcloud.invalid","Anonymous Nx Cloud Visitor","avatarUrl","emailHash","063df537c708fd7c212b33442939cce2ea5c0367e85be673a3e5351f1f01c25d","distinctID","3dff056d-31b5-4e41-96dc-264ac376fcf1","featureFlags",{"_747":22,"_748":22,"_749":22,"_750":22,"_751":46,"_752":22,"_753":22,"_754":22,"_755":22,"_756":28,"_757":22,"_758":28,"_759":46,"_760":22,"_761":28,"_762":763,"_764":22,"_765":22,"_766":22,"_767":22,"_768":769,"_770":771,"_772":28},"pylon_chat","show_setup_self_healing_ci_alert","new_access_control","non_dte_resource_usage","one_page_connect_workspace_github","resource_usage_toggle","workspace_badges","workspace_rewind","teams_minimum_spend","feature_activation_guide","demo-mode","new_layout","one_page_connect_workspace_gitlab","workspace_sandboxing_toggle","run_details_polling","one_page_connect_workspace_manual","test","resource_addon_default","automated_add_ons","survey-targeting-8e88152ae4-custom","config_yaml","welcome_view_cnw_experiment","variant-2","cnw_empty_workspace_position","treatment","cipe_execution_timeline","isProduction","isAnalyticsEnabled","isPosthogEnabled","isPylonEnabled","privateCloud",{"_805":796,"_349":350},"auth0",{"_799":800,"_801":802,"_803":804},"e2eTestMode","rollbar",{"_791":792,"_793":794,"_46":22,"_795":796,"_797":22,"_798":22},"posthog",{"_787":788,"_789":790},{"_735":736},"apiKey","phc_eTmACxF0EKeNRjAZbfpdszbHYumyKhWqsIpMU4Wi53c","apiHost","https://pha-prx.ops.cloud.nx.app","accessToken","d0e4070ed1d54ed29429808f497ffbab3e77f1c74c2a9427fa5c5e418eea62ca96294bc716a7e8210acf93f0d37b6d29","environment","production","codeVersion","2610.14.0002","captureUncaught","captureUnhandledRejections","domain","auth.nx.app","clientId","Ron6k221B4IaH0QK9hmHuCneTovLLPpX","audience","https://api.nrwl.io/","containerVersionTimestamp"]

Nx Agents

Forwarded environment variables