A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Cannot find name 'Disposable'.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'dispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

'DecompressionStream' is referenced directly or indirectly in its own type annotation.

'CompressionStream' is referenced directly or indirectly in its own type annotation.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Cannot find name 'Disposable'.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'dispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

'DecompressionStream' is referenced directly or indirectly in its own type annotation.

'CompressionStream' is referenced directly or indirectly in its own type annotation.

The strategy configuration was canceled because "build._13" failed

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Cannot find name 'Disposable'.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'dispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

'DecompressionStream' is referenced directly or indirectly in its own type annotation.

'CompressionStream' is referenced directly or indirectly in its own type annotation.

The strategy configuration was canceled because "build._13" failed

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Cannot find name 'Disposable'.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'dispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

'DecompressionStream' is referenced directly or indirectly in its own type annotation.

'CompressionStream' is referenced directly or indirectly in its own type annotation.

The strategy configuration was canceled because "build._13" failed

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Cannot find name 'Disposable'.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'dispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

'DecompressionStream' is referenced directly or indirectly in its own type annotation.

'CompressionStream' is referenced directly or indirectly in its own type annotation.

The strategy configuration was canceled because "build._13" failed

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Cannot find name 'Disposable'.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'dispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

'DecompressionStream' is referenced directly or indirectly in its own type annotation.

'CompressionStream' is referenced directly or indirectly in its own type annotation.

The strategy configuration was canceled because "build._13" failed

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Cannot find name 'Disposable'.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'dispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

'DecompressionStream' is referenced directly or indirectly in its own type annotation.

'CompressionStream' is referenced directly or indirectly in its own type annotation.

The strategy configuration was canceled because "build._13" failed

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Cannot find name 'Disposable'.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'dispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

'DecompressionStream' is referenced directly or indirectly in its own type annotation.

'CompressionStream' is referenced directly or indirectly in its own type annotation.

The strategy configuration was canceled because "build._13" failed

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Cannot find name 'Disposable'.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'dispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

'DecompressionStream' is referenced directly or indirectly in its own type annotation.

'CompressionStream' is referenced directly or indirectly in its own type annotation.

The strategy configuration was canceled because "build._13" failed

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Cannot find name 'Disposable'.

Property 'asyncDispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

Property 'dispose' does not exist on type 'SymbolConstructor'.

A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.

'DecompressionStream' is referenced directly or indirectly in its own type annotation.

'CompressionStream' is referenced directly or indirectly in its own type annotation.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/