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.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.0`](https://redirect.github.com/microsoft/tsdoc/blob/HEAD/tsdoc/CHANGELOG.md#0170)\n\nWed, 16 Sep 2026 01:24:29 GMT\n\n##### Minor changes\n\n- Update emitter to not replace line breaks\n\n

\n\n

modelcontextprotocol/typescript-sdk (@modelcontextprotocol/client)

\n\n### [`v2.1.0`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/releases/tag/%40modelcontextprotocol/client%402.1.0)\n\n[Compare Source](https://redirect.github.com/modelcontextprotocol/typescript-sdk/compare/@modelcontextprotocol/client@2.0.0...@modelcontextprotocol/client@2.1.0)\n\n##### Minor Changes\n\n- [#2629](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2629) [`dcc0102`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/dcc01028ff6a499a5728c2b6181c1727d52e2fab) Thanks [@gbshankar](https://redirect.github.com/gbshankar)! - Add DPoP (RFC 9449 / SEP-1932) sender-constrained access token support to the client.\n - Opt in by implementing `OAuthClientProvider.dpop()` returning a `DpopSession` (new, along with `generateDpopKeyPair`, `accessTokenHash`, `isDpopNonceChallenge`). `auth()` / `exchangeAuthorization` / `refreshAuthorization` / `fetchToken` then sign a DPoP proof into token requests (retrying once on an authorization-server `use_dpop_nonce` challenge, with client authentication re-applied per attempt), and `StreamableHTTPClientTransport`, `SSEClientTransport` and `withOAuth` present a `token_type: \"DPoP\"` access token as `Authorization: DPoP ` plus a fresh per-request proof, retry a resource-server `use_dpop_nonce` challenge once, and pick up a `DPoP-Nonce` delivered on any response. Tokens the AS issued as `Bearer` are still presented as Bearer.\n - DPoP is applied at the fetch layer: the transports wrap their resource-server `fetch` (including a caller-supplied `fetch` / `eventSourceInit.fetch`) with the new `withDpopFromProvider(provider)` middleware, so proofs are always bound to the request actually sent. `withDpop(session, getToken)` is exported for callers that manage tokens themselves (e.g. alongside a minimal `AuthProvider`); the `AuthProvider` interface itself is unchanged.\n - `auth()` now recovers from `invalid_dpop_proof` on refresh (e.g. a refresh token bound to a key that is no longer held) by discarding the tokens and re-authorizing, like `invalid_grant`. `OAuthErrorCode` gains `InvalidDpopProof` and `UseDpopNonce`; `extractWWWAuthenticateParams` recognizes the `DPoP` challenge scheme; `OAuthMetadataSchema` gains `dpop_signing_alg_values_supported`.\n\n##### Patch Changes\n\n- [#2726](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2726) [`6fa4227`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/6fa42279fecaba423635072f716bbb2f6f7c77f3) Thanks [@LuckTerence](https://redirect.github.com/LuckTerence)! - `SdkError` and `SdkHttpError` accept standard `ErrorOptions` as an optional fourth constructor argument and forward it to `Error`, so a wrapped error is reachable through the standard `Error.cause` chain. Version-negotiation probe failures (`SdkErrorCode.EraNegotiationFailed`) now use it: the underlying `TypeError: fetch failed` and the DNS or socket error beneath it surface via `error.cause`, so pino, Sentry, and `util.inspect` render `ENOTFOUND` / `ECONNREFUSED` / `ETIMEDOUT` instead of stopping at the `SdkError` ([#2657](https://redirect.github.com/modelcontextprotocol/typescript-sdk/issues/2657)). The previous `error.data.cause` slot is still populated for compatibility but is deprecated and slated for removal; read `error.cause` instead.\n\n- [#2654](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2654) [`03842cd`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/03842cd9cae9a9b142c77d2fb65e829fc4e03eab) Thanks [@pshah19](https://redirect.github.com/pshah19)! - Treat request id `0` as a real id. Two guards tested a `RequestId` for truthiness, so the legal JSON-RPC ids `0` and `''` were read as absent. Id `0` is not a corner case: the outbound request counter is zero-based, so it is the first id every peer assigns, which on the server→client leg is the first `sampling/createMessage`, `elicitation/create`, or `roots/list` a server sends.\n\n - `notifications/cancelled` carrying id `0` was ignored, and the in-flight handler ran to completion with its `AbortSignal` never fired.\n - A notification sent with `relatedRequestId: 0` wrongly passed the debounce gate (for methods opted into `debouncedNotificationMethods`). Because the pending set is keyed by method alone, a second such notification in the same tick was silently dropped rather than sent.\n\n Absent is now the only value that means \"no id\".\n\n- [#2043](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2043) [`c4248a9`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/c4248a935f245a86b2fb8b88b9c3d594e2bfea75) Thanks [@ChrisJr404](https://redirect.github.com/ChrisJr404)! - On Windows, stdio servers spawned by `StdioClientTransport` now also inherit `COMSPEC`, `PATHEXT`, `PROGRAMDATA`, `PROGRAMFILES(X86)`, `PROGRAMW6432`, and `WINDIR` (added to `DEFAULT_INHERITED_ENV_VARS`). Programs a server launches can depend on them: PowerShell finds no native executables without `PATHEXT`, and Windows OpenSSH exits 255 without `ProgramData`.\n\n- [#2668](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2668) [`3e90449`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/3e90449fd52997da43b79a536d2c19c446603cc7) Thanks [@KKonstantinov](https://redirect.github.com/KKonstantinov)! - Stop sending `notifications/cancelled` for the `initialize` handshake. The spec is explicit that a client MUST NOT attempt to cancel its `initialize` request, but the outbound cancel path fired for any in-flight request: aborting the `AbortSignal` passed to `connect()`, or letting the handshake hit its timeout, put a forbidden cancellation on the wire naming the initialize request id.\n\n The local behaviour is unchanged — the caller's promise still rejects with the same abort/timeout error, and `connect()` still tears the connection down. Only the wire notification is suppressed. Every other method keeps the existing cancellation path.\n\n- [#2475](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2475) [`b654261`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/b65426158ed9f29aea8ef3dc09ca22d7d9d6f970) Thanks [@sanjibani](https://redirect.github.com/sanjibani)! - `StreamableHTTPClientTransport` and `SSEClientTransport` now give their transport-managed headers precedence over same-named entries in `requestInit.headers`: `Authorization` when `authProvider` yields a token, `mcp-protocol-version`, and (Streamable HTTP) `mcp-session-id`. Header names compare case-insensitively and every `HeadersInit` form is covered (plain object, tuple array, `Headers` instance). Previously the caller-supplied value won, so a static `Authorization` placeholder (e.g. an env-var API key) kept overriding the OAuth token even after the provider obtained one and the fallback-to-OAuth flow never completed; a `Headers` instance or lowercase key produced a combined `Bearer , Bearer ` value instead. A configured `Authorization` is still sent while the provider has no token, and other configured headers pass through unchanged. Closes [#2208](https://redirect.github.com/modelcontextprotocol/typescript-sdk/issues/2208).\n\n- [#2581](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2581) [`5119ee7`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/5119ee7fd7790e335a3fb60ef36f85334e2a6326) Thanks [@hugosmoreira](https://redirect.github.com/hugosmoreira)! - Preserve the exact OAuth resource indicator from protected resource metadata when building authorization and token requests. Previously a pathless `resource` such as `https://example.com` was normalized to `https://example.com/` via `URL.href`, which breaks authorization servers that require the `resource` parameter to match the published value exactly (Microsoft Entra ID rejects it with `AADSTS9010010`). The exported OAuth helpers (`startAuthorization`, `exchangeAuthorization`, `refreshAuthorization`, `fetchToken`, `executeTokenRequest`) now also accept a `string` for `resource`; `selectResourceURL` still returns a `URL`, and a provider's `validateResourceURL` result is used unchanged. Fixes [#1968](https://redirect.github.com/modelcontextprotocol/typescript-sdk/issues/1968).\n\n- [`3924de9`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/3924de99df834302d89f5997a1b64ca268282284) - Let `saveTokens` failures surface after a successful token refresh. In `auth()`, one `try`\n wrapped both `refreshAuthorization()` and the `provider.saveTokens()` that persists its\n result, and the `catch` deliberately swallows anything that is not an `OAuthError` — plus\n `ServerError` — so that a failed refresh falls through to a fresh authorization request.\n A persistence error thrown by the provider landed in that same branch: it was discarded\n with no log and no rethrow, and `auth()` continued to `startAuthorization()` and returned\n `'REDIRECT'`.\n\n Against an authorization server that rotates refresh tokens (the OAuth 2.1 default, and\n Keycloak's) this loses credentials rather than merely hiding an error. The exchange has\n already succeeded server-side, so the old refresh token is invalidated at the moment the\n new one is issued; dropping the new token set leaves nothing usable on either side. On a\n headless or CLI client, where `redirectToAuthorization` is typically a no-op, the fallthrough\n is silent and the client is left with stale tokens and no indication of why.\n\n The `try`/`catch` now covers only `refreshAuthorization()`. Persisting the result happens\n after it, on an unguarded path, so a provider's I/O error propagates to the caller.\n\n Refresh-request failures keep their existing control flow exactly: a `ServerError` or an\n unknown error still falls through to a new authorization flow, a non-`ServerError`\n `OAuthError` is still rethrown, and `InsecureTokenEndpointError` is still surfaced. The\n SEP-2352 `issuer` stamp written with the refreshed tokens is unchanged.\n\n Those fallbacks no longer happen in silence, though. Both routes to an unexplained\n re-authorization now emit a `console.warn` naming the cause: the in-place fallthrough in\n the refresh block, and `auth()`'s outer recovery for `invalid_grant`, `invalid_client`,\n and `unauthorized_client`, which discards stored credentials and retries. The second one\n matters most in practice — an expired, revoked, or rotation-reuse-detected refresh token\n is reported as `invalid_grant`, which is precisely the state a dropped token set leaves\n behind for the next call.\n\n Consumers whose `OAuthClientProvider.saveTokens` can reject should note that `auth()` may\n now reject where it previously returned `'REDIRECT'` — that rejection is the failure that\n was being discarded.\n\n- [#2613](https://redirect.github.com/modelcontextprotocol/typescript-sdk/pull/2613) [`70de0c8`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/70de0c8b569b0d664a56b90be2f141d1d1645880) Thanks [@jwcarman](https://redirect.github.com/jwcarman)! - Emit and validate the `Mcp-Name` header for tasks requests per SEP-2663's Streamable HTTP binding: the client transport now mirrors `params.taskId` into `Mcp-Name` on `tasks/get` / `tasks/update` / `tasks/cancel` (previously omitted, causing conforming servers to reject every task poll with `-32020 HeaderMismatch`), and the server-side standard-header validation cross-checks it via the same shared `MCP_NAME_HEADER_SOURCE` table.\n\n On the server, `createMcpHandler` now answers a modern (2026-07-28) `tasks/get` / `tasks/update` / `tasks/cancel` POST that omits `Mcp-Name`, or whose header disagrees with `params.taskId`, with `400` / `-32020` (`HeaderMismatch`) at the `standard-header-validation` rung, the same treatment `tools/call` / `prompts/get` / `resources/read` already get. Legacy-era (2025-11-25) tasks traffic is unaffected. Clients built with this SDK release send the header; hand-rolled clients that omitted it must add it.\n\n- Updated dependencies \\[[`dcc0102`](https://redirect.github.com/modelcontextprotocol/typescript-sdk/commit/dcc01028ff6a499a5728c2b6181c1727d52e2fab)]:\n - [@modelcontextprotocol/core](https://redirect.github.com/modelcontextprotocol/core)@2.1.0\n\n

\n\n

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

\n\n### [`v2.41.0`](https://redirect.github.com/OpenAPITools/openapi-generator-cli/releases/tag/v2.41.0)\n\n[Compare Source](https://redirect.github.com/OpenAPITools/openapi-generator-cli/compare/v2.40.1...v2.41.0)\n\n##### Features\n\n- **release:** v7.25.0 release ([#1278](https://redirect.github.com/OpenAPITools/openapi-generator-cli/issues/1278)) ([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.54.3`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.54.3)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.54.2...@redocly/openapi-core@2.54.3)\n\n##### Patch Changes\n\n- Fixed an issue where generated clients attempted to parse compressed archives (`application/gzip`, `application/x-tar`), PDF files, Office documents, audio, video and font responses as JSON instead of decoding them as binary.\n- Added the value of the `REDOCLY_ENVIRONMENT` environment variable to the `user-agent` header of the `login`, `push`, and `push-status` requests.\n- Updated [@redocly/client-generator](https://redirect.github.com/redocly/client-generator) to v0.4.16.\n- Updated [@redocly/reunite-integration](https://redirect.github.com/redocly/reunite-integration) to v2.54.3.\n\n### [`v2.54.2`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.54.2)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/72572a9971e19b8ec2de9f1dee119b211b7dc84b...@redocly/openapi-core@2.54.2)\n\n##### Patch Changes\n\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.54.2.\n- Updated [@redocly/reunite-integration](https://redirect.github.com/redocly/reunite-integration) to v2.54.2.\n\n### [`v2.54.1`](https://redirect.github.com/Redocly/redocly-cli/compare/320e17f17aa10f1838807e2e74c86d5fe7fdaf75...72572a9971e19b8ec2de9f1dee119b211b7dc84b)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/320e17f17aa10f1838807e2e74c86d5fe7fdaf75...72572a9971e19b8ec2de9f1dee119b211b7dc84b)\n\n### [`v2.54.0`](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/cli@2.53.3...320e17f17aa10f1838807e2e74c86d5fe7fdaf75)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.53.3...320e17f17aa10f1838807e2e74c86d5fe7fdaf75)\n\n### [`v2.53.3`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.53.3)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.53.2...@redocly/openapi-core@2.53.3)\n\n##### Patch Changes\n\n- Fixed `respect` so a same-workflow `goto` no longer cleared `$steps` outputs from steps that already ran.\n Previously, this broke $steps expressions in the target step.\n- Updated [@redocly/respect-core](https://redirect.github.com/redocly/respect-core) to v2.53.3.\n\n### [`v2.53.2`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.53.2)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.53.1...@redocly/openapi-core@2.53.2)\n\n##### Patch Changes\n\n- Added `start` and `end` line and column positions to each problem location in the `--format=json` lint output.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.53.2.\n\n### [`v2.53.1`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.53.1)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.53.0...@redocly/openapi-core@2.53.1)\n\n##### Patch Changes\n\n- Added a deprecation warning to the `build-docs` command about the upcoming switch to Redoc 3.\n\n### [`v2.53.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.53.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.52.1...@redocly/openapi-core@2.53.0)\n\n##### Minor Changes\n\n- Added a `disallowDefault` option to the `operation-2xx-response` rule, which requires an explicit 2xx response when enabled.\n There is no change in current behavior.\n\n##### Patch Changes\n\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.53.0.\n\n### [`v2.52.1`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.52.1)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.52.0...@redocly/openapi-core@2.52.1)\n\n##### Patch Changes\n\n- Updated `redoc` to the `2.5.4` version to fix accessibility problems in the HTML produced by `build-docs`.\n Added the `lang` attribute to the default `build-docs` template.\n\n### [`v2.52.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.52.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.51.2...@redocly/openapi-core@2.52.0)\n\n##### Minor Changes\n\n- Added agent skills for AI coding assistants: `redocly-cli` for everyday CLI usage, `redocly-lint-rules` for writing configurable rules and custom plugins.\n Install them with `npx skills add https://redocly.com`.\n- Added an experimental `inspect-node-types` command to navigate the Redocly's node type tree of an API description.\n `inspect-node-types` helps pick the correct `subject` types for a configurable rule or the correct visitor for a custom plugin.\n- Added a `strategy` option to the `component-name-unique` rule, matching the `--component-names-strategy` option of the `bundle` command.\n- Added an experimental `introspect-mcp` command that analyzes a running MCP server and records its tools, prompts, resources, and capabilities.\n `introspect-mcp` records its findings in the `x-mcp` extension of an OpenAPI description.\n\n##### Patch Changes\n\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.52.0.\n\n### [`v2.51.2`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.51.2)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.51.1...@redocly/openapi-core@2.51.2)\n\n##### Patch Changes\n\n- Updated `fast-uri` to the `3.1.7` version to resolve `CVE-2026-75931`, `CVE-2026-75975`, `CVE-2026-75899`, and `CVE-2026-76172`.\n- Fixed `drift` and `coverage` failing to match a path template whose segment mixes literal text with parameters, such as `/instances/{worldId}:{instanceId}`.\n- Fixed an issue where Redocly config resolution failed when plugins used ESM syntax.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.51.2.\n\n### [`v2.51.1`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.51.1)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.51.0...@redocly/openapi-core@2.51.1)\n\n##### Patch Changes\n\n- Fixed an issue where `generate-arazzo` produced a malformed remote description URL in `sourceDescriptions` (`https://` collapsed to `https:/`) when `--output-file` was provided.\n- Fixed an issue where `$faker.string.email()` used without options generated addresses at the `undefined.com` domain.\n- Updated [@redocly/respect-core](https://redirect.github.com/redocly/respect-core) to v2.51.1.\n- Updated `@faker-js/faker` to the `10.6.0` version to resolve the high severity advisory `GHSA-qxc2-j82w-r537`.\n\n### [`v2.51.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.51.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.50.0...@redocly/openapi-core@2.51.0)\n\n##### Minor Changes\n\n- Enhanced the `generate-arazzo` command to print a ready-to-run `respect` command after generation, including an `--input` placeholder for every workflow input.\n- Added `--with-ai`, `--ai-provider`, `--ai-model`, `--ai-concurrency`, and `--max-workflows` options to the `generate-arazzo` command.\n `--with-ai` uses a local AI CLI (`claude`, `codex`, or `cursor`) and OpenAPI descriptions to redesign the generated one-workflow-per-operation skeleton into multi-step workflows.\n The AI designs at most `--max-workflows` workflows (default 10), and the generated file is marked as AI-inferred.\n For descriptions that don't fit a single prompt, the AI first selects scenarios from a compact operation index, then it designs each workflow separately.\n\n##### Patch Changes\n\n- Fixed an issue where `respect` and the `x-security-scheme-required-values` rule incorrectly rejected `x-security` HTTP schemes written with non-lowercase casing (such as `Basic`, `Bearer`, or `Digest`).\n RFC 7235 scheme names are case-insensitive.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.51.0.\n- Updated [@redocly/respect-core](https://redirect.github.com/redocly/respect-core) to v2.51.0.\n\n### [`v2.50.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.50.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.49.1...@redocly/openapi-core@2.50.0)\n\n##### Minor Changes\n\n- Added a new `schema` assertion for configurable rules.\n The assertion validates a property value against a JSON Schema.\n\n##### Patch Changes\n\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.50.0.\n\n### [`v2.49.1`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.49.1)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.49.0...@redocly/openapi-core@2.49.1)\n\n##### Patch Changes\n\n- Fixed an issue where rule incorrectly reported a duplicate parameter when two or more `$ref`s pointed to the same path item.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.49.1.\n\n### [`v2.49.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.49.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.48.0...@redocly/openapi-core@2.49.0)\n\n##### Minor Changes\n\n- Added the `no-illogical-composition-keywords` rule.\n\n **Note**: the rule is set to `warn` in the `recommended` ruleset and to `error` in `recommended-strict`. Existing API descriptions may report new problems.\n\n##### Patch Changes\n\n- Fixed an issue where telemetry silently failed to send when `npm` was not available.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.49.0.\n\n### [`v2.48.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.48.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.47.0...@redocly/openapi-core@2.48.0)\n\n##### Minor Changes\n\n- Added agent-friendly client generation: `python`, `go`, `php`, and `cli` generators beside the TypeScript client, each self-documenting with `--docs`, configurable per generator, and available as source in your own repository through `eject-generator`.\n\n##### Patch Changes\n\n- Fixed an issue where the `bundle` command didn't resolve `$ref`s inside an AsyncAPI 3 Multi Format Schema Object.\n- Fixed an issue where `respect --har-output` recorded an empty `postData` for every request.\n Request bodies are written to the HAR.\n Captures replayed through `drift` can have their request bodies validated instead of silently passing.\n- Updated [@redocly/client-generator](https://redirect.github.com/redocly/client-generator) to v0.4.0.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.48.0.\n\n### [`v2.47.0`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.47.0)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.46.2...@redocly/openapi-core@2.47.0)\n\n##### Minor Changes\n\n- Added a Vendor Extensions metric to the `stats` command that reports how many distinct `x-` extensions a description file uses and how often each one occurs.\n\n##### Patch Changes\n\n- Fixed the `stats` command reporting wrong parameter count for AsyncAPI descriptions.\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.47.0.\n\n### [`v2.46.2`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.46.2)\n\n[Compare Source](https://redirect.github.com/Redocly/redocly-cli/compare/@redocly/openapi-core@2.46.1...@redocly/openapi-core@2.46.2)\n\n##### Patch Changes\n\n- Updated [@redocly/openapi-core](https://redirect.github.com/redocly/openapi-core) to v2.46.2.\n\n### [`v2.46.1`](https://redirect.github.com/Redocly/redocly-cli/releases/tag/%40redocly/cli%402.46.1)\n\n[Compare Source](htt\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","375e5bcc5b1ba663c107a22322c84adc981edfb4","a2cda21431765a24755f1eaf75135773fe245355",{"_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":433,"_494":495,"_496":497,"_498":499,"_500":-5,"_501":499},"suggestedFixId","6ac10d94837774922b6620c5","fixedTasks",[502],"otherFailedTasks",[],"verificationStatus","COMPLETED","verificationTasksExecuted",[502],"userAction","NONE","userActionOrigin","userCommitMessage","suggestedFix","diff --git a/apps/chrome-devtools/src/app-components/app.ts b/apps/chrome-devtools/src/app-components/app.ts\nindex 2e256df01..f320cfbdd 100644\n--- a/apps/chrome-devtools/src/app-components/app.ts\n+++ b/apps/chrome-devtools/src/app-components/app.ts\n@@ -148,7 +148,7 @@ export class App {\n \n private requestSelectedComponentInfo() {\n /* eslint-disable @typescript-eslint/restrict-template-expressions -- we want to print the content of the functions */\n- chrome.devtools.inspectedWindow.eval(\n+ void chrome.devtools.inspectedWindow.eval(\n `function getTranslations(node){ return (${getTranslationsRec})(node, getTranslations); } `\n + `function getAnalyticEvents(node){ return (${getAnalyticEventsRec})(node, getAnalyticEvents); } `\n + `(${getSelectedComponentInfo})(getTranslations, getAnalyticEvents);`,\n","suggestedFixDescription","fix(chrome-devtools): mark inspectedWindow.eval promise as ignored","suggestedFixStatus","suggestedFixReasoning","The failing task was chrome-devtools:lint:ci. It reported one error: @typescript-eslint/no-floating-promises at apps/chrome-devtools/src/app-components/app.ts:151.\n\nThe PR updates @types/chrome from ^0.1.0 to ^0.3.0. The call to chrome.devtools.inspectedWindow.eval most likely returns a Promise under the new typings, which is why the rule now fires. I did not inspect the installed typings to confirm this.\n\nThe call already passes updateSelectedComponentInfoCallback as the callback, so its result is not needed. The fix is to prefix the call with the void operator. This marks the promise as intentionally ignored, the approach the rule's message itself suggests. It keeps the existing behaviour and does not weaken the lint rule or add a suppression comment.\n\nNo predefined fixes or off-limits areas exist in AGENTS.md or CLAUDE.md, and there is no .nx/SELF_HEALING.md. The similar-failure check found no matching failure on branch 4442.\n\nI ran ESLint on the changed file and it reported no errors. I did not rerun the full chrome-devtools:lint:ci task.","suggestedFixExecutionTime",41281,"verificationExecutionTime","reviewComment","We fixed the lint failure by marking the chrome.devtools.inspectedWindow.eval call with the void operator. After the @types/chrome bump to ^0.3.0, that call most likely returns a Promise, which @typescript-eslint/no-floating-promises flags. The result is already handled through the callback, so the promise is now explicitly ignored. ESLint on the changed file passes locally.","originalSuggestedFix","originalSuggestedFixDescription","originalSuggestedFixReasoning","userActionRecordedAt",["D",1791036820153],"suggestedAt",["D",1791036820153],"verifiedAt",["D",1791036837086],"RBPe","failureClassification","code_change","fileModeMap","suggestedFixFailureReason","suggestedFixFailureReasonDetails","suggestedFixFailureReasonType","assignedAgentName","autoApplySkipped","autoApplySkipReason","flakyRerunSkipped","flakyRerunPending","confidence","confidenceReasoning","One task failed with one lint error, and the fix is a single-line change: adding the void operator to one call. It is the standard way to satisfy no-floating-promises, it keeps the existing callback behaviour, and it does not weaken the rule. The failure matches the @types/chrome bump in this PR and does not appear on branch 4442. The rerun of chrome-devtools:lint:ci was reported as verified, though I did not see its output. The score is not 10 because the change is not a predefined deterministic fix and the typings were not inspected directly.","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:6433) [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",{"_504":502,"_505":506,"_507":-5,"_508":-5,"_509":-5,"_510":-5},"taskName","runLinkId","gYjG8Ck1ux","dteExecutionId","agentName","launchTemplates","taskTarget","AmadeusITGroup",["D",1676054118998],["D",1681913345534],"allowedEmailDomains",[573],"planActivationDate",["D",1686144031537],"isEligibleForProTrial","planLimits",{"_559":560,"_561":562,"_563":422,"_564":347,"_565":347,"_566":567,"_568":569,"_570":569,"_571":572},"isAiEnabled","planTransitions",[],"id","memberships",[539,540,541,542,543,544,545,546],"privateCloudInstallationId","hasBillingInformation","hasLicense","isUnclaimed","isOnTrial","isHighPriority","vcsProfileLink","vcsConfiguration","lastMembersSyncedAt","isAiBringYourOwnKey","enterpriseTrial","disabledReasonMessage",{"_547":558,"_549":550},{"_547":557,"_549":552},{"_547":556,"_549":550},{"_547":555,"_549":552},{"_547":554,"_549":552},{"_547":553,"_549":552},{"_547":551,"_549":552},{"_547":548,"_549":550},"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",1791036062411],["D",1791037044222],["D",1791037044222],[],[],[],[],{},{},{},{"_77":585,"_79":-5},{"_90":586,"_92":587,"_94":588,"_96":589},{"_129":610,"_131":611,"_133":612},{"_121":604,"_123":605},{"_104":593,"_106":594,"_80":595,"_82":596},{"_98":590},[591],{"_73":101,"_102":592,"_79":-5},[],[603],[],[600],[597],{"_73":111,"_102":598,"_79":-5},{"_113":114,"_86":599},[],{"_73":111,"_102":601,"_79":-5},{"_113":117,"_118":602},[],{"_73":111,"_102":22,"_79":-5},[608],[606],{"_73":111,"_102":607,"_79":-5},[],{"_73":111,"_102":609,"_79":-5},[],[616],[615],[613],{"_73":101,"_102":614,"_79":-5},[],{"_73":101,"_102":22,"_79":-5},{"_73":101,"_102":139,"_79":-5},["D",1791036062411],["D",1791037044718],["D",1791037044222],[634],{"_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":628,"_43":629,"_45":28},{"_219":220,"_221":222,"_223":627},["D",1791036378213],{"_62":-5,"_63":-5},{"_46":22,"_47":22,"_48":22,"_49":28,"_50":22,"_51":630,"_53":-5,"_54":-5,"_55":631,"_57":632,"_59":633,"_61":-5},[],[],[],[],{"_79":146,"_15":147,"_148":574,"_150":575,"_152":576,"_154":155,"_156":-5,"_157":22,"_158":-5,"_159":-5,"_160":-5,"_161":577,"_163":22,"_164":165,"_166":28,"_167":635,"_169":579,"_80":580,"_172":-5,"_173":581,"_175":636,"_177":583,"_179":-5,"_180":28,"_181":182,"_183":584},[],{},["D",1676055838344],"type","PRIMARY","publicCloudCounterpartId","privateCloudCounterpartId","installationSource","user","remoteSourceIntegrationType","GITHUB_EVENTLESS","featureMarkers",{"_680":22,"_681":28,"_682":22},"manualSetAccessLevel","idAccessLevel","READ_ONLY","patAccessLevel",{"_673":317,"_674":675,"_676":677,"_678":679},"flakyTaskConfiguration",{"_669":670,"_671":672},"aiTaskFixingConfiguration",{"_46":22,"_47":22,"_48":22,"_49":28,"_50":22,"_51":665,"_54":-5,"_55":666,"_57":667,"_59":668},"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",687],"notifications",["P",689],"isSystemAdmin","isSingleTenant","isPATExpiryAfterLoginEnabled","isOrganizationAccessEnabled","isExecutiveReportDisabled","loginas","repositoryAccessProvidersToOffer",[],"redirectTo","/cipes/6ac10a9e24b4d46208ba825e/configurations/config-yaml?runGroup=37127893589-1","deferredUserOrganizations",["P",701],"sidebarCollapsed","toast","currentUserId","currentUserEmail","signedInUser","isImpersonating","isBotRequest","ENV",{"_772":22,"_351":28,"_773":22,"_774":22,"_775":22,"_776":777,"_778":779,"_780":28,"_781":782,"_783":784,"_714":785},"posthogBootstrap",{"_742":743,"_744":745},"ultracacheUiEnabled","pylon",{"_734":735,"_736":737,"_71":738,"_739":-7,"_740":741},"requestInfo",{"_718":719,"_84":350,"_88":720,"_721":722,"_723":724},"hints",{"_727":730,"_732":733},"/cipes/6ac10a9e24b4d46208ba825e/configurations/config-yaml","url","https://cloud.nx.app/cipes/6ac10a9e24b4d46208ba825e/configurations/config-yaml","userPreferences",{"_725":726},"theme",{"_71":182,"_727":728,"_729":730,"_731":730},"variant","system","resolvedVariant","light","clientColorScheme","timeZone","UTC","appId","a1074fe2-8172-4ebd-9889-879f8308a0a2","email","28b45dee-f51f-426c-8aeb-dd545571b6d0@nxcloud.invalid","Anonymous Nx Cloud Visitor","avatarUrl","emailHash","270bfdbc443f237bf608d0854e16a0b938c84bd0b67793d82267a24e8f68a06a","distinctID","28b45dee-f51f-426c-8aeb-dd545571b6d0","featureFlags",{"_746":46,"_747":22,"_748":22,"_749":22,"_750":22,"_751":28,"_752":22,"_753":754,"_755":22,"_756":22,"_757":22,"_758":28,"_759":22,"_760":22,"_761":22,"_762":28,"_763":22,"_764":22,"_765":46,"_766":28,"_767":768,"_769":22,"_770":771},"one_page_connect_workspace_gitlab","demo-mode","teams_minimum_spend","automated_add_ons","pylon_chat","run_details_polling","resource_usage_toggle","welcome_view_cnw_experiment","variant-2","workspace_sandboxing_toggle","resource_addon_default","survey-targeting-8e88152ae4-custom","feature_activation_guide","workspace_badges","show_setup_self_healing_ci_alert","config_yaml","cipe_execution_timeline","workspace_rewind","new_access_control","one_page_connect_workspace_github","new_layout","cnw_empty_workspace_position","treatment","non_dte_resource_usage","one_page_connect_workspace_manual","test","isProduction","isAnalyticsEnabled","isPosthogEnabled","isPylonEnabled","privateCloud",{"_804":795,"_349":350},"auth0",{"_798":799,"_800":801,"_802":803},"e2eTestMode","rollbar",{"_790":791,"_792":793,"_46":22,"_794":795,"_796":22,"_797":22},"posthog",{"_786":787,"_788":789},{"_734":735},"apiKey","phc_eTmACxF0EKeNRjAZbfpdszbHYumyKhWqsIpMU4Wi53c","apiHost","https://pha-prx.ops.cloud.nx.app","accessToken","d0e4070ed1d54ed29429808f497ffbab3e77f1c74c2a9427fa5c5e418eea62ca96294bc716a7e8210acf93f0d37b6d29","environment","production","codeVersion","2610.14.0002","captureUncaught","captureUnhandledRejections","domain","auth.nx.app","clientId","Ron6k221B4IaH0QK9hmHuCneTovLLPpX","audience","https://api.nrwl.io/","containerVersionTimestamp"]

Config YAML