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.141.0`](https://redirect.github.com/figma/plugin-typings/compare/v1.140.0...v1.141.0)\n\n[Compare Source](https://redirect.github.com/figma/plugin-typings/compare/v1.140.0...v1.141.0)\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.44.0`](https://redirect.github.com/figma/rest-api-spec/compare/2a90e5adc67d8117d7c2da624f03a9bfa3027fb6...v0.44.0)\n\n[Compare Source](https://redirect.github.com/figma/rest-api-spec/compare/2a90e5adc67d8117d7c2da624f03a9bfa3027fb6...v0.44.0)\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/server)

\n\n### [`v2.3.1`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/releases/tag/%40modelcontextprotocol/client%402.3.1)\n\n[Compare Source](https://redirect.github.com/modelcontextprotocol/typescript-sdk/compare/@modelcontextprotocol/server@2.3.0...@modelcontextprotocol/server@2.3.1)\n\n##### Patch Changes\n\n- Updated dependencies \\[]:\n - [@modelcontextprotocol/core](https://redirect.github.com/modelcontextprotocol/core)@2.3.1\n\n### [`v2.3.0`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/releases/tag/%40modelcontextprotocol/server%402.3.0)\n\n[Compare Source](https://redirect.github.com/modelcontextprotocol/typescript-sdk/compare/@modelcontextprotocol/server@2.2.0...@modelcontextprotocol/server@2.3.0)\n\n##### Minor Changes\n\n- [#2929](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2929) [`40f8f4e`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/40f8f4e229d963cd7fd2890bda2aeebe7005299a) Thanks [@claude](https://redirect.github.com/apps/claude)! - `requireBearerAuth` and `verifyBearerToken` take a new optional `expectedResource`, which makes them accept only tokens issued for this resource (the token's audience). Set it to the value your authorization server puts into tokens meant for this server, usually the server's URL. When it is set, a token is accepted only if the verifier reports that value in `AuthInfo.resource`; the two are compared as strings, ignoring a fragment and one trailing slash. A token reported for another value, or for none, is answered `401 invalid_token` with the usual `WWW-Authenticate` challenge. When it is not set, nothing changes. To use it, pass `expectedResource` and have `verifyAccessToken` fill `AuthInfo.resource`, for example from the `aud` claim. The option is declared on a new exported type, `VerifyBearerTokenOptions`, which extends `BearerAuthOptions`; `BearerAuthOptions` itself is unchanged. The Express `requireBearerAuth` passes the option through. With Express, `@modelcontextprotocol/express` has to be upgraded to this release as well: 2.0.1 does not pass the option on, so nothing is compared. Its options type does not have the option, so TypeScript reports an `expectedResource` written in a call to the 2.0.1 `requireBearerAuth` as an error.\n\n- [#2926](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2926) [`6d8dbc6`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/6d8dbc6cb590edf766fcb66b636ca6b654e99c37) Thanks [@claude](https://redirect.github.com/apps/claude)! - `McpServer` now accepts a `maxToolInputElements` option that limits the number of elements in tool-call arguments: the largest combined number of array elements and object members a single `tools/call` `arguments` payload may contain. It is off by default, so behavior is unchanged unless you set it. When it is set and a call exceeds it, that call is answered with an `isError: true` tool result that names the limit, before the input schema runs, and the server keeps serving. Set it above the largest arguments your tools legitimately accept; `maxRequestBodySize` remains the primary limit on request size. The value must be a number of at least 1, or `Infinity` for no limit; any other value is rejected at construction. The options type is exported as `McpServerOptions`.\n\n- [#2918](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2918) [`84804c2`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/84804c22e45a662675a198f853b7f00063838a8d) Thanks [@claude](https://redirect.github.com/apps/claude)! - A `Server` or `McpServer` now serves one connection at a time, and a Streamable HTTP server transport without sessions (`sessionIdGenerator: undefined`) serves one request. An app that uses one server object, or one stateless transport, for every HTTP request fails on the second request after this upgrade. Build the server and the transport per request instead.\n\n What keeps working without a change:\n\n - `createMcpHandler(buildServer)` and `serveStdio(buildServer)`, where `buildServer` returns a new server on every call.\n - A handler that builds a new server and a new stateless transport for each request.\n - One server and one transport per session (a transport with a `sessionIdGenerator`).\n - Connecting a server again after `close()`.\n - `Client`.\n\n What fails now, how it shows, and what to change:\n\n - One server object with a new stateless transport per request (`const server = new McpServer(...)` outside the handler, `await server.connect(transport)` inside it): the second HTTP request the process receives fails, and so does every later one. `connect()` rejects with an `SdkError` of code `ALREADY_CONNECTED`. If the handler closes the transport when the response ends, requests that arrive one after the other still work and a request that overlaps another one fails. Change: move `new McpServer(...)` and its registrations into the handler.\n - One stateless transport for every request (a transport built once with `sessionIdGenerator: undefined`): the second HTTP request fails. `WebStandardStreamableHTTPServerTransport.handleRequest()` rejects with `Stateless transport cannot be reused across requests. Create a new transport per request.`, and `NodeStreamableHTTPServerTransport.handleRequest()` answers `500`. Change: build the server and the transport inside the handler and connect them there.\n - `createMcpHandler(() => server)` with a server built once: a request that arrives after the previous response has been read to its end still works. A request that arrives while another one is being served is answered `500` with the JSON-RPC error `-32603` (`Internal server error`); the reason is reported only through the `onerror` option. Change: pass a function that builds the server, as in `createMcpHandler(buildServer)`.\n - One server object for every session: the `initialize` request of the second session fails with `ALREADY_CONNECTED`. Change: build a server per session.\n\n What the caller sees when `connect()` or `handleRequest()` rejects depends on the host. Express 5, Fastify and Hono answer `500`. A plain `node:http` listener without its own error handling gets an unhandled rejection, which ends the process.\n\n The README examples of `@modelcontextprotocol/express`, `@modelcontextprotocol/fastify`, `@modelcontextprotocol/hono` and `@modelcontextprotocol/node`, and the handler examples in the JSDoc of `WebStandardStreamableHTTPServerTransport` and `NodeStreamableHTTPServerTransport`, now build a server and a transport per request.\n\n- [#2907](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2907) [`e55f9ac`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/e55f9ac1b1cae413599b499cbaa45c0378edba78) Thanks [@claude](https://redirect.github.com/apps/claude)! - `allowedOrigins` and `validateOriginHeader` accept lowercase entries of the form `://*`, such as `moz-extension://*` or `chrome-extension://*`, which admit every origin of that scheme. This lets a server admit MCP clients that run as a browser extension when the extension ID cannot be listed, as on Firefox, where it differs on every install. `http://*` and `https://*` are not honoured, and the defaults are unchanged.\n\n##### Patch Changes\n\n- [#2599](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2599) [`5238fba`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/5238fba4424f82ec1ae9f6f458dd655ab322062d) Thanks [@freya0926](https://redirect.github.com/freya0926)! - A server can now serve, and a client can now call, `tasks/get` and `tasks/cancel` of the Tasks extension (SEP-2663) on a 2026-07-28 connection, when the handler is registered and the request is sent with an explicit schema. Every other method that a protocol revision removed is still refused. If one server factory serves both eras and such a handler is meant for 2025-era clients only, register it only when `ctx.era === 'legacy'`.\n\n- [#2107](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2107) [`2fc49ea`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/2fc49eaf17a6b9ac0810c875cc96d3b949f9522c) Thanks [@pragnyanramtha](https://redirect.github.com/pragnyanramtha)! - `prompts/get` without `arguments` no longer fails with \"Invalid arguments\" when every argument of the prompt is optional. A missing `arguments` is now validated as `{}`, as it already is for `tools/call`, so a top-level `.optional()` or `.default(...)` on `argsSchema` no longer sees `undefined`.\n\n- [#2889](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2889) [`4d94e7b`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/4d94e7b1ccf769d94a7bbba7789f1ee6c7dfdd8c) Thanks [@claude](https://redirect.github.com/apps/claude)! - `registerTool` no longer converts tool schemas up front, so a server built per request stops converting every tool on every request. The warning about an invalid `x-mcp-header` declaration now appears each time tools are listed, not when the tool is registered.\n\n- [#2908](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2908) [`633dd3e`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/633dd3e12bff6869c932c4a526341622320912b1) Thanks [@claude](https://redirect.github.com/apps/claude)! - The `license` field of the package manifests is now `Apache-2.0`; the `LICENSE` file shipped in each package carries the full terms, including the MIT text for earlier contributions. No code change.\n\n- [#2841](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2841) [`2237555`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/2237555ed036c3e80341c0f3c28684e9c3ff0728) Thanks [@sharziki](https://redirect.github.com/sharziki)! - `McpServer.registerPrompt()` now types the callback correctly when no `argsSchema` is given: its one parameter is the server context. Before, reading `ctx.mcpReq` there was a type error although it worked at runtime. Prompts registered with an `argsSchema` are unchanged.\n\n- Updated dependencies \\[[`633dd3e`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/633dd3e12bff6869c932c4a526341622320912b1)]:\n - [@modelcontextprotocol/core](https://redirect.github.com/modelcontextprotocol/core)@2.3.0\n\n### [`v2.2.0`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/releases/tag/%40modelcontextprotocol/server%402.2.0)\n\n[Compare Source](https://redirect.github.com/modelcontextprotocol/typescript-sdk/compare/@modelcontextprotocol/server@2.1.0...@modelcontextprotocol/server@2.2.0)\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- [#2778](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2778) [`e3fb9ed`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/e3fb9edcdec70ed7c8463548ea9b90bbcb74c4ab) Thanks [@vjymisal0](https://redirect.github.com/vjymisal0)! - Fix a stack overflow in `createMcpHandler` when the factory returns the same server instance for more than one request. Returning a fresh instance per request is still required.\n\n- [#2651](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2651) [`c55efa6`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/c55efa62fc4218592418ffbd313d1a906286f1d3) Thanks [@sushantkumar23](https://redirect.github.com/sushantkumar23)! - `createMcpHandler` now ends a `subscriptions/listen` stream right after the acknowledgement when it honored none of the requested notification types, instead of holding the stream open with nothing to deliver. The client receives the acknowledgement and then the `resultType: \"complete\"` result. Streams that honor at least one type are unchanged.\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/client%402.1.0)\n\n[Compare Source](https://redirect.github.com/modelcontextprotocol/typescript-sdk/compare/@modelcontextprotocol/server@2.0.0...@modelcontextprotocol/server@2.1.0)\n\n##### Minor Changes\n\n- [#2629](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2629) [`dcc0102`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/dcc01028ff6a499a5728c2b6181c1727d52e2fab) Thanks [@gbshankar](https://redirect.github.com/gbshankar)! - Add DPoP (RFC 9449 / SEP-1932) sender-constrained access token support to the client.\n - Opt in by implementing `OAuthClientProvider.dpop()` returning a `DpopSession` (new, along with `generateDpopKeyPair`, `accessTokenHash`, `isDpopNonceChallenge`). `auth()` / `exchangeAuthorization` / `refreshAuthorization` / `fetchToken` then sign a DPoP proof into token requests (retrying once on an authorization-server `use_dpop_nonce` challenge, with client authentication re-applied per attempt), and `StreamableHTTPClientTransport`, `SSEClientTransport` and `withOAuth` present a `token_type: \"DPoP\"` access token as `Authorization: DPoP ` plus a fresh per-request proof, retry a resource-server `use_dpop_nonce` challenge once, and pick up a `DPoP-Nonce` delivered on any response. Tokens the AS issued as `Bearer` are still presented as Bearer.\n - DPoP is applied at the fetch layer: the transports wrap their resource-server `fetch` (including a caller-supplied `fetch` / `eventSourceInit.fetch`) with the new `withDpopFromProvider(provider)` middleware, so proofs are always bound to the request actually sent. `withDpop(session, getToken)` is exported for callers that manage tokens themselves (e.g. alongside a minimal `AuthProvider`); the `AuthProvider` interface itself is unchanged.\n - `auth()` now recovers from `invalid_dpop_proof` on refresh (e.g. a refresh token bound to a key that is no longer held) by discarding the tokens and re-authorizing, like `invalid_grant`. `OAuthErrorCode` gains `InvalidDpopProof` and `UseDpopNonce`; `extractWWWAuthenticateParams` recognizes the `DPoP` challenge scheme; `OAuthMetadataSchema` gains `dpop_signing_alg_values_supported`.\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- [#2043](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2043) [`c4248a9`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/c4248a935f245a86b2fb8b88b9c3d594e2bfea75) Thanks [@ChrisJr404](https://redirect.github.com/ChrisJr404)! - On Windows, stdio servers spawned by `StdioClientTransport` now also inherit `COMSPEC`, `PATHEXT`, `PROGRAMDATA`, `PROGRAMFILES(X86)`, `PROGRAMW6432`, and `WINDIR` (added to `DEFAULT_INHERITED_ENV_VARS`). Programs a server launches can depend on them: PowerShell finds no native executables without `PATHEXT`, and Windows OpenSSH exits 255 without `ProgramData`.\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- [#2475](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2475) [`b654261`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/b65426158ed9f29aea8ef3dc09ca22d7d9d6f970) Thanks [@sanjibani](https://redirect.github.com/sanjibani)! - `StreamableHTTPClientTransport` and `SSEClientTransport` now give their transport-managed headers precedence over same-named entries in `requestInit.headers`: `Authorization` when `authProvider` yields a token, `mcp-protocol-version`, and (Streamable HTTP) `mcp-session-id`. Header names compare case-insensitively and every `HeadersInit` form is covered (plain object, tuple array, `Headers` instance). Previously the caller-supplied value won, so a static `Authorization` placeholder (e.g. an env-var API key) kept overriding the OAuth token even after the provider obtained one and the fallback-to-OAuth flow never completed; a `Headers` instance or lowercase key produced a combined `Bearer , Bearer ` value instead. A configured `Authorization` is still sent while the provider has no token, and other configured headers pass through unchanged. Closes [#2208](https://redirect.github.com/modelcontextprotocol/typescript-sdk/issues/2208).\n\n- [#2581](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2581) [`5119ee7`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/5119ee7fd7790e335a3fb60ef36f85334e2a6326) Thanks [@hugosmoreira](https://redirect.github.com/hugosmoreira)! - Preserve the exact OAuth resource indicator from protected resource metadata when building authorization and token requests. Previously a pathless `resource` such as `https://example.com` was normalized to `https://example.com/` via `URL.href`, which breaks authorization servers that require the `resource` parameter to match the published value exactly (Microsoft Entra ID rejects it with `AADSTS9010010`). The exported OAuth helpers (`startAuthorization`, `exchangeAuthorization`, `refreshAuthorization`, `fetchToken`, `executeTokenRequest`) now also accept a `string` for `resource`; `selectResourceURL` still returns a `URL`, and a provider's `validateResourceURL` result is used unchanged. Fixes [#1968](https://redirect.github.com/modelcontextprotocol/typescript-sdk/issues/1968).\n\n- [`3924de9`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/3924de99df834302d89f5997a1b64ca268282284) - Let `saveTokens` failures surface after a successful token refresh. In `auth()`, one `try`\n wrapped both `refreshAuthorization()` and the `provider.saveTokens()` that persists its\n result, and the `catch` deliberately swallows anything that is not an `OAuthError` — plus\n `ServerError` — so that a failed refresh falls through to a fresh authorization request.\n A persistence error thrown by the provider landed in that same branch: it was discarded\n with no log and no rethrow, and `auth()` continued to `startAuthorization()` and returned\n `'REDIRECT'`.\n\n Against an authorization server that rotates refresh tokens (the OAuth 2.1 default, and\n Keycloak's) this loses credentials rather than merely hiding an error. The exchange has\n already succeeded server-side, so the old refresh token is invalidated at the moment the\n new one is issued; dropping the new token set leaves nothing usable on either side. On a\n headless or CLI client, where `redirectToAuthorization` is typically a no-op, the fallthrough\n is silent and the client is left with stale tokens and no indication of why.\n\n The `try`/`catch` now covers only `refreshAuthorization()`. Persisting the result happens\n after it, on an unguarded path, so a provider's I/O error propagates to the caller.\n\n Refresh-request failures keep their existing control flow exactly: a `ServerError` or an\n unknown error still falls through to a new authorization flow, a non-`ServerError`\n `OAuthError` is still rethrown, and `InsecureTokenEndpointError` is still surfaced. The\n SEP-2352 `issuer` stamp written with the refreshed tokens is unchanged.\n\n Those fallbacks no longer happen in silence, though. Both routes to an unexplained\n re-authorization now emit a `console.warn` naming the cause: the in-place fallthrough in\n the refresh block, and `auth()`'s outer recovery for `invalid_grant`, `invalid_client`,\n and `unauthorized_client`, which discards stored credentials and retries. The second one\n matters most in practice — an expired, revoked, or rotation-reuse-detected refresh token\n is reported as `invalid_grant`, which is precisely the state a dropped token set leaves\n behind for the next call.\n\n Consumers whose `OAuthClientProvider.saveTokens` can reject should note that `auth()` may\n now reject where it previously returned `'REDIRECT'` — that rejection is the failure that\n was being discarded.\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))\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","41a6990bfb5cc136d93111a6b1ef0355969616bd","0252305d7569fdb50acab3f07985e3c3593d2d03",{"_439":440,"_441":442,"_443":444,"_445":446,"_447":448,"_449":450,"_451":-5,"_452":-5,"_453":454,"_455":456,"_457":446,"_458":459,"_460":461,"_462":-5,"_463":464,"_465":-5,"_466":-5,"_467":-5,"_468":-5,"_148":469,"_470":471,"_472":473,"_381":474,"_475":476,"_477":-5,"_478":-5,"_479":-5,"_480":-5,"_481":-5,"_482":-5,"_483":-5,"_484":-5,"_485":-5,"_486":487,"_488":489,"_490":491,"_492":493,"_494":-5,"_495":493},"suggestedFixId","6acdb8e5f73178bf0bd822d5","fixedTasks",[496],"otherFailedTasks",[],"verificationStatus","COMPLETED","verificationTasksExecuted",[496],"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..f320cfbdd 100644\n--- a/apps/chrome-devtools/src/app-components/app.ts\n+++ b/apps/chrome-devtools/src/app-components/app.ts\n@@ -148,7 +148,7 @@ export class App {\n \n private requestSelectedComponentInfo() {\n /* eslint-disable @typescript-eslint/restrict-template-expressions -- we want to print the content of the functions */\n- chrome.devtools.inspectedWindow.eval(\n+ void chrome.devtools.inspectedWindow.eval(\n `function getTranslations(node){ return (${getTranslationsRec})(node, getTranslations); } `\n + `function getAnalyticEvents(node){ return (${getAnalyticEventsRec})(node, getAnalyticEvents); } `\n + `(${getSelectedComponentInfo})(getTranslations, getAnalyticEvents);`,\n","suggestedFixDescription","fix(chrome-devtools): mark inspectedWindow.eval promise as ignored","suggestedFixStatus","suggestedFixReasoning","The failing task was chrome-devtools:lint:ci. It reported one error: `@typescript-eslint/no-floating-promises` at `apps/chrome-devtools/src/app-components/app.ts:151`.\n\nThat line is the `chrome.devtools.inspectedWindow.eval(...)` call in `requestSelectedComponentInfo`. The PR bumps `@types/chrome` from ^0.1.0 to ^0.3.0. The likely explanation is that the new typings give `eval` a Promise return type, so the unawaited call is now flagged. I did not read the new typings to confirm this.\n\nThe fix prefixes the call with `void`, which the rule's own message offers as a way to explicitly ignore a promise. The call already passes `updateSelectedComponentInfoCallback`, which receives the result, so nothing needs awaiting. Adding `void` leaves behavior unchanged.\n\nI did not disable the rule or weaken any lint config. No `.nx/SELF_HEALING.md` exists, and AGENTS.md has no predefined fixes or off-limits areas, so nothing restricted this change.\n\nRunning `yarn eslint --quiet` on the changed file produced no errors. The similar-failure check found no matching failure on other branches, so the error comes from this PR's dependency update.","suggestedFixExecutionTime",44722,"verificationExecutionTime","reviewComment","We fixed the lint failure by marking the `chrome.devtools.inspectedWindow.eval(...)` call with the `void` operator. The @types/chrome upgrade most likely made `eval` return a Promise, which `@typescript-eslint/no-floating-promises` now flags. Results are still delivered through the existing callback, so behavior is unchanged. ESLint on the changed file now passes with no errors.","originalSuggestedFix","originalSuggestedFixDescription","originalSuggestedFixReasoning","userActionRecordedAt",["D",1791867109832],"suggestedAt",["D",1791867109832],"verifiedAt",["D",1791867129650],"Q3eV","failureClassification","code_change","fileModeMap","suggestedFixFailureReason","suggestedFixFailureReasonDetails","suggestedFixFailureReasonType","assignedAgentName","autoApplySkipped","autoApplySkipReason","flakyRerunSkipped","flakyRerunPending","confidence",8,"confidenceReasoning","The fix is a one-line `void` prefix in a single file, and it is the remedy the lint rule itself suggests. Only one task failed, and chrome-devtools:lint:ci now passes on rerun. The score is not higher because `void` is not the only reasonable fix. The call could instead be awaited or given a `.catch`, and the Promise-returning behavior of the new @types/chrome is inferred, not confirmed.","fixApplicationAttempts",[],"taskOutputSummary","TASK ID: chrome-devtools:lint:ci\n> git ls-files \":(glob)**/*\" | yarn eslint --quiet --cache --cache-location .cache/eslint\r\n\r\n(node:2990) [DEP0176] DeprecationWarning: fs.F_OK is deprecated, use fs.constants.F_OK instead\n(Use `node --trace-deprecation ...` to show where the warning was created)\n\n/home/runner/work/otter/otter/apps/chrome-devtools/src/app-components/app.ts\n 151:5 error Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the `void` operator @typescript-eslint/no-floating-promises\n\n✖ 1 problem (1 error, 0 warnings)\n\nWarning: command \"git ls-files \":(glob)**/*\" | yarn eslint --quiet --cache --cache-location .cache/eslint\" exited with non-zero status code","remoteTaskSummary","localTaskSummary","chrome-devtools:lint:ci",{"_498":496,"_499":500,"_501":-5,"_502":-5,"_503":-5,"_504":-5},"taskName","runLinkId","q3hpN2aKbB","dteExecutionId","agentName","launchTemplates","taskTarget","AmadeusITGroup",["D",1676054118998],["D",1681913345534],"allowedEmailDomains",[567],"planActivationDate",["D",1686144031537],"isEligibleForProTrial","planLimits",{"_553":554,"_555":556,"_557":416,"_558":340,"_559":340,"_560":561,"_562":563,"_564":563,"_565":566},"isAiEnabled","planTransitions",[],"id","memberships",[533,534,535,536,537,538,539,540],"privateCloudInstallationId","hasBillingInformation","hasLicense","isUnclaimed","isOnTrial","isHighPriority","vcsProfileLink","vcsConfiguration","lastMembersSyncedAt","isAiBringYourOwnKey","enterpriseTrial","disabledReasonMessage",{"_541":552,"_543":544},{"_541":551,"_543":546},{"_541":550,"_543":544},{"_541":549,"_543":546},{"_541":548,"_543":546},{"_541":547,"_543":546},{"_541":545,"_543":546},{"_541":542,"_543":544},"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",1791866925870],["D",1791867183744],["D",1791867183744],[],[],[],[],{},{},{},{"_77":579,"_79":-5},{"_90":580,"_92":581,"_94":582,"_96":583},{"_129":604,"_131":605,"_133":606},{"_121":598,"_123":599},{"_104":587,"_106":588,"_80":589,"_82":590},{"_98":584},[585],{"_73":101,"_102":586,"_79":-5},[],[597],[],[594],[591],{"_73":111,"_102":592,"_79":-5},{"_113":114,"_86":593},[],{"_73":111,"_102":595,"_79":-5},{"_113":117,"_118":596},[],{"_73":111,"_102":22,"_79":-5},[602],[600],{"_73":111,"_102":601,"_79":-5},[],{"_73":111,"_102":603,"_79":-5},[],[610],[609],[607],{"_73":101,"_102":608,"_79":-5},[],{"_73":101,"_102":22,"_79":-5},{"_73":101,"_102":139,"_79":-5},["D",1791866925870],["D",1791867184010],["D",1791867183744],[626],{"_188":287,"_288":287,"_289":290,"_291":292,"_293":-5,"_294":-5,"_295":296,"_297":298,"_299":300,"_301":302,"_303":304,"_305":306,"_307":308,"_309":310,"_311":-5,"_312":-5},[],[218,219,220,221,222,223,224,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,23,270,271,272,273,274,275,276,277,278,279,280,281,282,283,284,285,286],[],{"_41":620,"_43":621,"_45":28},{"_62":-5,"_63":-5},{"_46":22,"_47":22,"_48":22,"_49":28,"_50":22,"_51":622,"_53":-5,"_54":-5,"_55":623,"_57":624,"_59":625,"_61":-5},[],[],[],[],{"_79":146,"_15":147,"_148":568,"_150":569,"_152":570,"_154":155,"_156":-5,"_157":22,"_158":-5,"_159":-5,"_160":-5,"_161":571,"_163":22,"_164":165,"_166":28,"_167":627,"_169":573,"_80":574,"_172":-5,"_173":575,"_175":628,"_177":577,"_179":-5,"_180":28,"_181":182,"_183":578},[],{},["D",1676055838344],"type","PRIMARY","publicCloudCounterpartId","privateCloudCounterpartId","installationSource","user","remoteSourceIntegrationType","GITHUB_EVENTLESS","featureMarkers",{"_672":22,"_673":28,"_674":22},"manualSetAccessLevel","idAccessLevel","READ_ONLY","patAccessLevel",{"_665":310,"_666":667,"_668":669,"_670":671},"flakyTaskConfiguration",{"_661":662,"_663":664},"aiTaskFixingConfiguration",{"_46":22,"_47":22,"_48":22,"_49":28,"_50":22,"_51":657,"_54":-5,"_55":658,"_57":659,"_59":660},"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",679],"notifications",["P",681],"isSystemAdmin","isSingleTenant","isPATExpiryAfterLoginEnabled","isOrganizationAccessEnabled","isExecutiveReportDisabled","loginas","repositoryAccessProvidersToOffer",[],"redirectTo","/cipes/6acdb82d3d87970f162661e8/configurations/config-yaml?runGroup=38347998963-1","deferredUserOrganizations",["P",693],"sidebarCollapsed","toast","currentUserId","currentUserEmail","signedInUser","isImpersonating","isBotRequest","ENV",{"_764":22,"_344":28,"_765":22,"_766":22,"_767":22,"_768":769,"_770":771,"_772":28,"_773":774,"_775":776,"_706":777},"posthogBootstrap",{"_734":735,"_736":737},"ultracacheUiEnabled","pylon",{"_726":727,"_728":729,"_71":730,"_731":-7,"_732":733},"requestInfo",{"_710":711,"_84":343,"_88":712,"_713":714,"_715":716},"hints",{"_719":722,"_724":725},"/cipes/6acdb82d3d87970f162661e8/configurations/config-yaml","url","https://cloud.nx.app/cipes/6acdb82d3d87970f162661e8/configurations/config-yaml","userPreferences",{"_717":718},"theme",{"_71":182,"_719":720,"_721":722,"_723":722},"variant","system","resolvedVariant","light","clientColorScheme","timeZone","UTC","appId","a1074fe2-8172-4ebd-9889-879f8308a0a2","email","fd89b5c0-1ecd-46d2-b668-9daf455d45f4@nxcloud.invalid","Anonymous Nx Cloud Visitor","avatarUrl","emailHash","fc7ac2a99d9c73762012ea53a430007cdd64b6c14044ec6f07f982cea80a490a","distinctID","fd89b5c0-1ecd-46d2-b668-9daf455d45f4","featureFlags",{"_738":739,"_740":22,"_741":22,"_742":28,"_743":22,"_744":745,"_746":22,"_747":22,"_748":28,"_749":22,"_750":46,"_751":22,"_752":753,"_754":22,"_755":22,"_756":28,"_757":46,"_758":22,"_759":22,"_760":22,"_761":22,"_762":22,"_763":28},"welcome_view_cnw_experiment","variant-2","config_yaml","automated_add_ons","run_details_polling","workspace_rewind","one_page_connect_workspace_manual","test","workspace_sandboxing_toggle","show_setup_self_healing_ci_alert","feature_activation_guide","resource_addon_default","one_page_connect_workspace_gitlab","teams_minimum_spend","cnw_empty_workspace_position","treatment","survey-targeting-8e88152ae4-custom","new_access_control","cipe_execution_timeline","one_page_connect_workspace_github","pylon_chat","resource_usage_toggle","workspace_badges","demo-mode","non_dte_resource_usage","new_layout","isProduction","isAnalyticsEnabled","isPosthogEnabled","isPylonEnabled","privateCloud",{"_796":787,"_342":343},"auth0",{"_790":791,"_792":793,"_794":795},"e2eTestMode","rollbar",{"_782":783,"_784":785,"_46":22,"_786":787,"_788":22,"_789":22},"posthog",{"_778":779,"_780":781},{"_726":727},"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"]

Config YAML