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.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/server%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- [#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/254a7d5ca7489\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","6504d332f8532eff9b203d1a4032e2aa8434ba3c","3deba3d3edc8ef13a2984feea106adf77e95c541",{"_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","6acc9f0f59b4d9dbb0bf2af1","fixedTasks",[503,504],"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..b2b400739 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?: unknown) {\n this.selectedComponentInfo.next(info);\n this.cd.detectChanges();\n }\ndiff --git a/packages/@ama-mcp/core/src/server/index.ts b/packages/@ama-mcp/core/src/server/index.ts\nindex 06acf55be..1da56a003 100644\n--- a/packages/@ama-mcp/core/src/server/index.ts\n+++ b/packages/@ama-mcp/core/src/server/index.ts\n@@ -2,13 +2,16 @@ import {\n type Icon,\n type Implementation,\n McpServer,\n+ type PromptCallback,\n type ReadResourceCallback,\n type ReadResourceTemplateCallback,\n+ type RegisteredPrompt,\n type RegisteredResource,\n type RegisteredResourceTemplate,\n type RegisteredTool,\n type ResourceMetadata,\n type ResourceTemplate,\n+ type ScopeChallengeHandler,\n type ServerOptions,\n type StandardSchemaWithJSON,\n type ToolAnnotations,\n@@ -33,6 +36,18 @@ const sendMetricsIfAuthorized = async (...args: Parameters = {\n+ title?: string;\n+ description?: string;\n+ argsSchema?: Args;\n+ icons?: Icon[];\n+ scopeChallenge?: ScopeChallengeHandler;\n+ _meta?: Record;\n+};\n+\n /**\n * MCP server with telemetry support\n */\n@@ -44,12 +59,19 @@ export class AmaMcpServer extends McpServer {\n /**\n * @inheritdoc\n */\n- public override registerPrompt(...args: Parameters) {\n- const [name, config, promptCallback] = args;\n+ public override registerPrompt(name: string, config: PromptConfig, promptCallback: PromptCallback): RegisteredPrompt;\n+ /**\n+ * @inheritdoc\n+ */\n+ public override registerPrompt(name: string, config: PromptConfig, promptCallback: PromptCallback): RegisteredPrompt;\n+ /**\n+ * @inheritdoc\n+ */\n+ public override registerPrompt(name: string, config: PromptConfig, promptCallback: PromptCallback | PromptCallback): RegisteredPrompt {\n const callback = createCallback(promptCallback, name, 'promptCall', { logger: this.logger });\n let error;\n try {\n- return super.registerPrompt(name, config, callback);\n+ return super.registerPrompt(name, config as PromptConfig, callback as PromptCallback);\n } catch (e) {\n error = e;\n throw e;\n","suggestedFixDescription","fix: adapt to MCP SDK 2.3 and @types/chrome 0.3 typings","suggestedFixStatus","suggestedFixReasoning","Two compile failures came from the dependency bumps in this PR, and neither appears on main.\n\n**ama-mcp-core:compile (TS2416)**\n- `@modelcontextprotocol/server` 2.3.1 types the `registerPrompt` callback differently depending on whether `argsSchema` is given. Without it, the callback receives only the server context. With it, the callback receives the parsed args and then the context.\n- The old override used `Parameters`, which only picks up the last overload. That overload is the deprecated raw-shape one, so the override was no longer assignable to the base method.\n- The override in `packages/@ama-mcp/core/src/server/index.ts` now declares two overloads: no schema, and a `StandardSchemaWithJSON` schema. The shared implementation keeps the existing telemetry wrapping.\n- A small `PromptConfig` type was added, and the SDK types `PromptCallback`, `RegisteredPrompt` and `ScopeChallengeHandler` are now imported.\n- A single narrow cast is needed when forwarding to `super.registerPrompt`, because TypeScript cannot resolve the overloads from a union. No `any` and no ts-ignore were used.\n\n**chrome-devtools:build-components (TS2769)**\n- `@types/chrome` 0.3 types the `chrome.devtools.inspectedWindow.eval` callback as receiving `(result, exceptionInfo)`. The old callback took only `info`, so no overload matched.\n- `updateSelectedComponentInfo` in `apps/chrome-devtools/src/app-components/app.ts` now accepts an optional second `_exceptionInfo` parameter, typed `unknown`. Runtime behaviour is unchanged.\n\n**Verification**\n- `ama-mcp-core:compile` and `chrome-devtools:build-components` both ran successfully after the changes.\n- No predefined fixes or off-limits areas were found in the configuration files.","suggestedFixExecutionTime",230362,"verificationExecutionTime","reviewComment","We updated our code to match the new typings that came in with this dependency bump. Our `registerPrompt` override now declares the same overloads as `McpServer` in `@modelcontextprotocol/server` 2.3.1. Our devtools eval callback now accepts the `(result, exceptionInfo)` arguments from `@types/chrome` 0.3. This should fix both TypeScript compile errors.","originalSuggestedFix","originalSuggestedFixDescription","originalSuggestedFixReasoning","userActionRecordedAt",["D",1791794959758],"suggestedAt",["D",1791794959758],"verifiedAt",["D",1791794964497],"xdL8","failureClassification","code_change","fileModeMap","suggestedFixFailureReason","suggestedFixFailureReasonDetails","suggestedFixFailureReasonType","assignedAgentName","autoApplySkipped","autoApplySkipReason","flakyRerunSkipped","flakyRerunPending","confidence",7,"confidenceReasoning","Both targets were re-run and compiled successfully (chrome-devtools:build-components earlier in the session, ama-mcp-core:compile per the user's rerun). The causes are clear: typing changes from the dependency bumps. The chrome-devtools change is a trivial one-parameter addition. The registerPrompt fix is less obvious, because it replaces the override signature with two overloads plus a narrow cast, and other reasonable ways to write it exist. Two projects are affected and there are no behavioural changes, so confidence is moderately high rather than very high.","fixApplicationAttempts",[],"taskOutputSummary","TASK ID: ama-mcp-core:compile\nsrc/server/index.ts:47:19 - error TS2416: Property 'registerPrompt' in type 'AmaMcpServer' is not assignable to the same property in base type 'McpServer'.\n Type '(name: string, config: { title?: string | undefined; description?: string | undefined; argsSchema?: ZodRawShape | undefined; icons?: { src: string; mimeType?: string | undefined; sizes?: string[] | undefined; theme?: \"light\" | ... 1 more ... | undefined; }[] | undefined; scopeChallenge?: ScopeChallengeHandler | unde...' is not assignable to type '{ (name: string, config: { title?: string | undefined; description?: string | undefined; argsSchema?: undefined; icons?: { src: string; mimeType?: string | undefined; sizes?: string[] | undefined; theme?: \"light\" | ... 1 more ... | undefined; }[] | undefined; scopeChallenge?: ScopeChallengeHandler | undefined; _meta...'.\n Types of parameters 'cb' and 'cb' are incompatible.\n Types of parameters 'ctx' and 'args' are incompatible.\n Type '{ [x: string]: unknown; }' is not assignable to type 'ServerContext'.\n Property 'mcpReq' is missing in type '{ [x: string]: unknown; }' but required in type 'BaseContext'.\n\n47 public override registerPrompt(...args: Parameters) {\n ~~~~~~~~~~~~~~\n\n ../../../.yarn/cache/@modelcontextprotocol-server-npm-2.3.1-ff579c1f16-13bcf61340.zip/node_modules/@modelcontextprotocol/server/dist/createMcpHandler-D4NN8WsG.d.mts:2119:3\n 2119 mcpReq: {\n ~~~~~~\n 'mcpReq' is declared here.\n\n\nFound 1 error.\n\n\n\nTASK ID: chrome-devtools:build-components\n❯ Building...\n✔ Building...\nApplication bundle generation failed. [12.082 seconds] - 2026-10-12T08:43:39.196Z\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","ama-mcp-core:compile","chrome-devtools:build-components",{"_507":503,"_508":509,"_510":-5,"_511":-5,"_512":-5,"_513":-5},{"_507":504,"_508":509,"_510":-5,"_511":-5,"_512":-5,"_513":-5},"taskName","runLinkId","JxSInWVvgg","dteExecutionId","agentName","launchTemplates","taskTarget","AmadeusITGroup",["D",1676054118998],["D",1681913345534],"allowedEmailDomains",[576],"planActivationDate",["D",1686144031537],"isEligibleForProTrial","planLimits",{"_562":563,"_564":565,"_566":423,"_567":347,"_568":347,"_569":570,"_571":572,"_573":572,"_574":575},"isAiEnabled","planTransitions",[],"id","memberships",[542,543,544,545,546,547,548,549],"privateCloudInstallationId","hasBillingInformation","hasLicense","isUnclaimed","isOnTrial","isHighPriority","vcsProfileLink","vcsConfiguration","lastMembersSyncedAt","isAiBringYourOwnKey","enterpriseTrial","disabledReasonMessage",{"_550":561,"_552":553},{"_550":560,"_552":555},{"_550":559,"_552":553},{"_550":558,"_552":555},{"_550":557,"_552":555},{"_550":556,"_552":555},{"_550":554,"_552":555},{"_550":551,"_552":553},"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",1791794041844],["D",1791794999657],["D",1791794999657],[],[],[],[],{},{},{},{"_77":588,"_79":-5},{"_90":589,"_92":590,"_94":591,"_96":592},{"_129":613,"_131":614,"_133":615},{"_121":607,"_123":608},{"_104":596,"_106":597,"_80":598,"_82":599},{"_98":593},[594],{"_73":101,"_102":595,"_79":-5},[],[606],[],[603],[600],{"_73":111,"_102":601,"_79":-5},{"_113":114,"_86":602},[],{"_73":111,"_102":604,"_79":-5},{"_113":117,"_118":605},[],{"_73":111,"_102":22,"_79":-5},[611],[609],{"_73":111,"_102":610,"_79":-5},[],{"_73":111,"_102":612,"_79":-5},[],[619],[618],[616],{"_73":101,"_102":617,"_79":-5},[],{"_73":101,"_102":22,"_79":-5},{"_73":101,"_102":139,"_79":-5},["D",1791794041844],["D",1791794999940],["D",1791794999657],[637],{"_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":631,"_43":632,"_45":28},{"_219":220,"_221":222,"_223":630},["D",1791794463758],{"_62":-5,"_63":-5},{"_46":22,"_47":22,"_48":22,"_49":28,"_50":22,"_51":633,"_53":-5,"_54":-5,"_55":634,"_57":635,"_59":636,"_61":-5},[],[],[],[],{"_79":146,"_15":147,"_148":577,"_150":578,"_152":579,"_154":155,"_156":-5,"_157":22,"_158":-5,"_159":-5,"_160":-5,"_161":580,"_163":22,"_164":165,"_166":28,"_167":638,"_169":582,"_80":583,"_172":-5,"_173":584,"_175":639,"_177":586,"_179":-5,"_180":28,"_181":182,"_183":587},[],{},["D",1676055838344],"type","PRIMARY","publicCloudCounterpartId","privateCloudCounterpartId","installationSource","user","remoteSourceIntegrationType","GITHUB_EVENTLESS","featureMarkers",{"_683":22,"_684":28,"_685":22},"manualSetAccessLevel","idAccessLevel","READ_ONLY","patAccessLevel",{"_676":317,"_677":678,"_679":680,"_681":682},"flakyTaskConfiguration",{"_672":673,"_674":675},"aiTaskFixingConfiguration",{"_46":22,"_47":22,"_48":22,"_49":28,"_50":22,"_51":668,"_54":-5,"_55":669,"_57":670,"_59":671},"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",690],"notifications",["P",692],"isSystemAdmin","isSingleTenant","isPATExpiryAfterLoginEnabled","isOrganizationAccessEnabled","isExecutiveReportDisabled","loginas","repositoryAccessProvidersToOffer",[],"redirectTo","/cipes/6acc9b792aa7356437834098/configurations/nx-agents?runGroup=38223856266-1","deferredUserOrganizations",["P",704],"sidebarCollapsed","toast","currentUserId","currentUserEmail","signedInUser","isImpersonating","isBotRequest","ENV",{"_775":22,"_351":28,"_776":22,"_777":22,"_778":22,"_779":780,"_781":782,"_783":28,"_784":785,"_786":787,"_717":788},"posthogBootstrap",{"_745":746,"_747":748},"ultracacheUiEnabled","pylon",{"_737":738,"_739":740,"_71":741,"_742":-7,"_743":744},"requestInfo",{"_721":722,"_84":350,"_88":723,"_724":725,"_726":727},"hints",{"_730":733,"_735":736},"/cipes/6acc9b792aa7356437834098/configurations/nx-agents","url","https://cloud.nx.app/cipes/6acc9b792aa7356437834098/configurations/nx-agents","userPreferences",{"_728":729},"theme",{"_71":182,"_730":731,"_732":733,"_734":733},"variant","system","resolvedVariant","light","clientColorScheme","timeZone","UTC","appId","a1074fe2-8172-4ebd-9889-879f8308a0a2","email","b6fe34c7-db91-494d-a6f3-439a938699c5@nxcloud.invalid","Anonymous Nx Cloud Visitor","avatarUrl","emailHash","8189025e7911447cafba71792073738cbb8768f41807a93c4216fd10f282bae9","distinctID","b6fe34c7-db91-494d-a6f3-439a938699c5","featureFlags",{"_749":22,"_750":751,"_752":22,"_753":22,"_754":28,"_755":22,"_756":22,"_757":28,"_758":46,"_759":22,"_760":22,"_761":22,"_762":22,"_763":22,"_764":22,"_765":28,"_766":46,"_767":22,"_768":22,"_769":770,"_771":22,"_772":773,"_774":28},"teams_minimum_spend","cnw_empty_workspace_position","treatment","resource_addon_default","show_setup_self_healing_ci_alert","run_details_polling","demo-mode","non_dte_resource_usage","feature_activation_guide","one_page_connect_workspace_gitlab","workspace_sandboxing_toggle","config_yaml","automated_add_ons","workspace_rewind","workspace_badges","survey-targeting-8e88152ae4-custom","cipe_execution_timeline","one_page_connect_workspace_github","pylon_chat","resource_usage_toggle","one_page_connect_workspace_manual","test","new_access_control","welcome_view_cnw_experiment","variant-2","new_layout","isProduction","isAnalyticsEnabled","isPosthogEnabled","isPylonEnabled","privateCloud",{"_807":798,"_349":350},"auth0",{"_801":802,"_803":804,"_805":806},"e2eTestMode","rollbar",{"_793":794,"_795":796,"_46":22,"_797":798,"_799":22,"_800":22},"posthog",{"_789":790,"_791":792},{"_737":738},"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