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/server%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/node%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- [#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- Updated dependencies \\[[`6fa4227`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/6fa42279fecaba423635072f716bbb2f6f7c77f3), [`03842cd`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/03842cd9cae9a9b142c77d2fb65e829fc4e03eab), [`3e90449`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/3e90449fd52997da43b79a536d2c19c446603cc7), [`7b781ed`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/7b781ed4e25355a25d15974f3c76de81299694ed), [`75dc7ea`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/75dc7ea6e2913e1ac37d4f06eec62cd5cfac9e7a), [`6032170`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/60321700871029401a2e3bed8fdf4f02c9ec3331), [`6a05402`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/6a054025e8cebaecead76fb51d92ba3974e8d091), [`70de0c8`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/70de0c8b569b0d664a56b90be2f141d1d1645880)]:\n - [@modelcontextprotocol/server](https://redirect.github.com/modelcontextprotocol/server)@2.1.0\n\n

\n\n

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

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

\n\n

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

\n\n### [`v2.61.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.61.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.60.0...@redocly/openapi-core@2.61.0)\n\n##### Minor Changes\n\n- Added pass-through stream request bodies to the generated TypeScript, Python, Go, and PHP clients.\n A stream body is sent as is in one attempt, and the caller's `Content-Type` wins over the one in the API description.\n\n##### Patch Changes\n\n- Added a deprecation warning for Node.js 20.x.\n Update to Node.js 22.12.0 or higher.\n- Updated `@modelcontextprotocol/sdk` to `1.32.1` to resolve `GHSA-6qxp-vccf-f47h`.\n- Updated [@redocly/client-generator](https://redirect.github.com/redocly/client-generator) to v0.5.0.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.61.0.\n- Updated [@redocly/reunite-integration](https://redirect.github.com/redocly/reunite-integration) to v2.61.0.\n\n### [`v2.60.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.60.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.59.0...@redocly/openapi-core@2.60.0)\n\n##### Minor Changes\n\n- Added the `--file-name-conflicts-severity` option for the `split` command to control how file name conflicts are reported.\n\n##### Patch Changes\n\n- Fixed an issue where `split` lost content when two components, paths, webhooks, channels, operations, or code samples got the same file name.\n\n **Warning:** `split` output may differ from older releases: when several names would share one file, each later file now gets a `-n` suffix, where `n` is its order, for example `user-2.yaml` next to `User.yaml`.\n\n### [`v2.59.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.59.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.58.2...@redocly/openapi-core@2.59.0)\n\n##### Minor Changes\n\n- Improved `redocly recheck` to lint the `description` fields of API descriptions.\n Findings report the source line and column.\n You can suppress the findings by file, rule, and pointer, or adjust rules for descriptions only.\n\n **Note:** `ResolvedRecheckConfig` gains a required `descriptionRules` field.\n Library code that builds that object by hand must set it.\n\n##### Patch Changes\n\n- Updated `brace-expansion` to `2.1.7` and `5.0.12`, `dompurify` to `3.4.16`, `fast-uri` to `3.1.8`, and `js-yaml` to `5.4.3` to resolve `CVE-2026-102276`, `CVE-2026-102277`, `CVE-2026-102278`, `CVE-2026-86472`, `GHSA-p98j-92pf-mc4p`, and `GHSA-r3ph-w7gj-g6xm`.\n- Updated `oxfmt` to `0.72.0` and `tinypool` to `2.2.0` to resolve `CVE-2026-104848` and `CVE-2026-104849`.\n- Updated `proxy-addr` to `2.0.8` and `source-map-js` to `1.2.2` to resolve `CVE-2026-90711` and `CVE-2026-93749`.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.59.0.\n- Updated [@redocly/recheck](https://redirect.github.com/redocly/recheck) to v2.59.0.\n- Updated [@redocly/reunite-integration](https://redirect.github.com/redocly/reunite-integration) to v2.59.0.\n\n### [`v2.58.2`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.58.2)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.58.1...@redocly/openapi-core@2.58.2)\n\n##### Patch Changes\n\n- Fixed an issue where the generated PHP client failed with `Undefined constant \"OPERATIONS\"` when OPcache preload was enabled.\n- Updated [@redocly/client-generator](https://redirect.github.com/redocly/client-generator) to v0.4.23.\n\n### [`v2.58.1`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.58.1)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/8a5a966465f3bf9be4da8566ad4c0086f1fccd3c...@redocly/openapi-core@2.58.1)\n\n##### Patch Changes\n\n- Improved performance of the `no-invalid-media-type-examples`, `no-invalid-schema-examples`, and `no-invalid-parameter-examples` rules by reusing validators for schemas that are referenced or repeated.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.58.1.\n- Updated [@redocly/reunite-integration](https://redirect.github.com/redocly/reunite-integration) to v2.58.1.\n\n### [`v2.58.0`](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/cli@2.57.0...8a5a966465f3bf9be4da8566ad4c0086f1fccd3c)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.57.0...8a5a966465f3bf9be4da8566ad4c0086f1fccd3c)\n\n### [`v2.57.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.57.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.56.1...@redocly/openapi-core@2.57.0)\n\n##### Minor Changes\n\n- Added `const` checking to the `no-enum-type-mismatch` rule: a `const` value must conform to the schema's `type`, the same way every `enum` value does.\n\n **Note**: linting output may include new errors for schemas whose `const` value doesn't match their `type`.\n\n##### Patch Changes\n\n- Fixed an issue where `no-enum-type-mismatch` dropped violations and reported a wrong location when `type` was written as an array.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.57.0.\n\n### [`v2.56.1`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.56.1)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.56.0...@redocly/openapi-core@2.56.1)\n\n##### Patch Changes\n\n- Improved overall startup performance.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.56.1.\n\n### [`v2.56.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.56.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redoc\n\n> [!IMPORTANT]\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","f8dd66a1f2f0726889df73928803f4220de0aa09","31da3deaf8c0a53b92eec04e344bc6faa0a4bae9",{"_447":448,"_449":450,"_451":452,"_453":454,"_455":456,"_457":458,"_459":-5,"_460":-5,"_461":462,"_463":464,"_465":454,"_466":467,"_468":469,"_470":-5,"_471":472,"_473":-5,"_474":-5,"_475":-5,"_476":-5,"_148":477,"_478":479,"_480":481,"_389":482,"_483":484,"_485":-5,"_486":-5,"_487":-5,"_488":-5,"_489":-5,"_490":-5,"_491":-5,"_492":-5,"_493":-5,"_494":495,"_496":497,"_498":499,"_500":501,"_502":-5,"_503":501},"suggestedFixId","6acf3e0c3a1e33603e94f9ff","fixedTasks",[504],"otherFailedTasks",[],"verificationStatus","COMPLETED","verificationTasksExecuted",[504],"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","chrome-devtools:lint:ci failed with one error: @typescript-eslint/no-floating-promises at apps/chrome-devtools/src/app-components/app.ts:151.\n\nThe PR bumps @types/chrome from ^0.1.0 to ^0.3.0. The call to chrome.devtools.inspectedWindow.eval itself was not changed. The new typings most likely make eval return a Promise even when a callback is supplied, which would explain why the call is now flagged. I did not open the typings to confirm this.\n\nThe fix prefixes the call with the void operator. This is the explicit \"ignored\" marker the rule accepts. The result is still delivered through the existing callback (updateSelectedComponentInfoCallback), so runtime behavior is unchanged.\n\nAlternatives considered:\n- Adding .catch or await would change the control flow for no benefit.\n- Disabling the rule would weaken lint enforcement.\n\nNo configuration file (SELF_HEALING.md, CLAUDE.md, AGENTS.md) contained predefined fixes or off-limits areas for this task.\n\nESLint run on the changed file after the edit reported no errors. I did not run the full chrome-devtools:lint:ci task.","suggestedFixExecutionTime",34738,"verificationExecutionTime","reviewComment","We fixed the lint failure by prefixing the `chrome.devtools.inspectedWindow.eval` call with the `void` operator. The `@types/chrome` bump to ^0.3.0 most likely makes `eval` return a Promise even when a callback is passed, so the existing call was flagged by `@typescript-eslint/no-floating-promises`. The callback still handles the result, so behavior is unchanged and the lint error is resolved.","originalSuggestedFix","originalSuggestedFixDescription","originalSuggestedFixReasoning","userActionRecordedAt",["D",1791966732880],"suggestedAt",["D",1791966732879],"verifiedAt",["D",1791966752852],"RrNp","failureClassification","code_change","fileModeMap","suggestedFixFailureReason","suggestedFixFailureReasonDetails","suggestedFixFailureReasonType","assignedAgentName","autoApplySkipped","autoApplySkipReason","flakyRerunSkipped","flakyRerunPending","confidence",9,"confidenceReasoning","The fix is a one-token change (adding the void operator) at the single line flagged by @typescript-eslint/no-floating-promises. Only one task failed and it was rerun and verified. The void operator is the standard, idiomatic way to mark an intentionally ignored promise, and the existing callback still handles the result, so runtime behavior is unchanged. Alternatives such as await or .catch would alter control flow, so there is effectively one reasonable fix.","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:6443) [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",{"_506":504,"_507":508,"_509":-5,"_510":-5,"_511":-5,"_512":-5},"taskName","runLinkId","0D9DQD8qAq","dteExecutionId","agentName","launchTemplates","taskTarget","AmadeusITGroup",["D",1676054118998],["D",1681913345534],"allowedEmailDomains",[575],"planActivationDate",["D",1686144031537],"isEligibleForProTrial","planLimits",{"_561":562,"_563":564,"_565":424,"_566":348,"_567":348,"_568":569,"_570":571,"_572":571,"_573":574},"isAiEnabled","planTransitions",[],"id","memberships",[541,542,543,544,545,546,547,548],"privateCloudInstallationId","hasBillingInformation","hasLicense","isUnclaimed","isOnTrial","isHighPriority","vcsProfileLink","vcsConfiguration","lastMembersSyncedAt","isAiBringYourOwnKey","enterpriseTrial","disabledReasonMessage",{"_549":560,"_551":552},{"_549":559,"_551":554},{"_549":558,"_551":552},{"_549":557,"_551":554},{"_549":556,"_551":554},{"_549":555,"_551":554},{"_549":553,"_551":554},{"_549":550,"_551":552},"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",1791965874574],["D",1791966787110],["D",1791966787110],[],[],[],[],{},{},{},{"_77":587,"_79":-5},{"_90":588,"_92":589,"_94":590,"_96":591},{"_129":612,"_131":613,"_133":614},{"_121":606,"_123":607},{"_104":595,"_106":596,"_80":597,"_82":598},{"_98":592},[593],{"_73":101,"_102":594,"_79":-5},[],[605],[],[602],[599],{"_73":111,"_102":600,"_79":-5},{"_113":114,"_86":601},[],{"_73":111,"_102":603,"_79":-5},{"_113":117,"_118":604},[],{"_73":111,"_102":22,"_79":-5},[610],[608],{"_73":111,"_102":609,"_79":-5},[],{"_73":111,"_102":611,"_79":-5},[],[618],[617],[615],{"_73":101,"_102":616,"_79":-5},[],{"_73":101,"_102":22,"_79":-5},{"_73":101,"_102":139,"_79":-5},["D",1791965874574],["D",1791966787552],["D",1791966787110],[636],{"_188":295,"_296":295,"_297":298,"_299":300,"_301":-5,"_302":-5,"_303":304,"_305":306,"_307":308,"_309":310,"_311":312,"_313":314,"_315":316,"_317":318,"_319":-5,"_320":-5},[],[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,277,23,278,279,280,281,282,283,284,285,286,287,288,289,290,291,292,293,294],[],{"_41":630,"_43":631,"_45":28},{"_220":221,"_222":223,"_224":629},["D",1791966274282],{"_62":-5,"_63":-5},{"_46":22,"_47":22,"_48":22,"_49":28,"_50":22,"_51":632,"_53":-5,"_54":-5,"_55":633,"_57":634,"_59":635,"_61":-5},[],[],[],[],{"_79":146,"_15":147,"_148":576,"_150":577,"_152":578,"_154":155,"_156":-5,"_157":22,"_158":-5,"_159":-5,"_160":-5,"_161":579,"_163":22,"_164":165,"_166":28,"_167":637,"_169":581,"_80":582,"_172":-5,"_173":583,"_175":638,"_177":585,"_179":-5,"_180":28,"_181":182,"_183":586},[],{},["D",1676055838344],"type","PRIMARY","publicCloudCounterpartId","privateCloudCounterpartId","installationSource","user","remoteSourceIntegrationType","GITHUB_EVENTLESS","featureMarkers",{"_682":22,"_683":28,"_684":22},"manualSetAccessLevel","idAccessLevel","READ_ONLY","patAccessLevel",{"_675":318,"_676":677,"_678":679,"_680":681},"flakyTaskConfiguration",{"_671":672,"_673":674},"aiTaskFixingConfiguration",{"_46":22,"_47":22,"_48":22,"_49":28,"_50":22,"_51":667,"_54":-5,"_55":668,"_57":669,"_59":670},"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",689],"notifications",["P",691],"isSystemAdmin","isSingleTenant","isPATExpiryAfterLoginEnabled","isOrganizationAccessEnabled","isExecutiveReportDisabled","loginas","repositoryAccessProvidersToOffer",[],"redirectTo","/cipes/6acf3ab23e13b404a495bd3b/configurations/nx-agents?runGroup=38533549170-1","deferredUserOrganizations",["P",703],"sidebarCollapsed","toast","currentUserId","currentUserEmail","signedInUser","isImpersonating","isBotRequest","ENV",{"_774":22,"_352":28,"_775":22,"_776":22,"_777":22,"_778":779,"_780":781,"_782":28,"_783":784,"_785":786,"_716":787},"posthogBootstrap",{"_744":745,"_746":747},"ultracacheUiEnabled","pylon",{"_736":737,"_738":739,"_71":740,"_741":-7,"_742":743},"requestInfo",{"_720":721,"_84":351,"_88":722,"_723":724,"_725":726},"hints",{"_729":732,"_734":735},"/cipes/6acf3ab23e13b404a495bd3b/configurations/nx-agents","url","https://cloud.nx.app/cipes/6acf3ab23e13b404a495bd3b/configurations/nx-agents","userPreferences",{"_727":728},"theme",{"_71":182,"_729":730,"_731":732,"_733":732},"variant","system","resolvedVariant","light","clientColorScheme","timeZone","UTC","appId","a1074fe2-8172-4ebd-9889-879f8308a0a2","email","c5d0e676-f40e-4fc6-b183-6fe67b8b1625@nxcloud.invalid","Anonymous Nx Cloud Visitor","avatarUrl","emailHash","2bb0789f0e21532be0a3edb98284d8116edcb88cf48fecada3151d0fe7975a47","distinctID","c5d0e676-f40e-4fc6-b183-6fe67b8b1625","featureFlags",{"_748":749,"_750":22,"_751":46,"_752":46,"_753":28,"_754":22,"_755":28,"_756":757,"_758":22,"_759":22,"_760":22,"_761":22,"_762":22,"_763":764,"_765":22,"_766":22,"_767":22,"_768":28,"_769":22,"_770":22,"_771":22,"_772":28,"_773":22},"one_page_connect_workspace_manual","test","automated_add_ons","one_page_connect_workspace_github","one_page_connect_workspace_gitlab","feature_activation_guide","new_access_control","cipe_execution_timeline","welcome_view_cnw_experiment","variant-2","pylon_chat","non_dte_resource_usage","workspace_badges","config_yaml","teams_minimum_spend","cnw_empty_workspace_position","treatment","demo-mode","workspace_sandboxing_toggle","show_setup_self_healing_ci_alert","run_details_polling","resource_usage_toggle","resource_addon_default","workspace_rewind","new_layout","survey-targeting-8e88152ae4-custom","isProduction","isAnalyticsEnabled","isPosthogEnabled","isPylonEnabled","privateCloud",{"_806":797,"_350":351},"auth0",{"_800":801,"_802":803,"_804":805},"e2eTestMode","rollbar",{"_792":793,"_794":795,"_46":22,"_796":797,"_798":22,"_799":22},"posthog",{"_788":789,"_790":791},{"_736":737},"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