chore(deps): update dependency @types/node to v24 #784
renovate[bot]Annotations
63 errors and 10 warnings
|
Build and test (9):
node_modules/@types/node/fs.d.ts#L337
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (9):
node_modules/@types/node/fs.d.ts#L331
Property 'asyncDispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (9):
node_modules/@types/node/fs.d.ts#L331
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (9):
node_modules/@types/node/events.d.ts#L403
Cannot find name 'Disposable'.
|
|
Build and test (9):
node_modules/@types/node/dgram.d.ts#L595
Property 'asyncDispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (9):
node_modules/@types/node/dgram.d.ts#L595
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (9):
node_modules/@types/node/child_process.d.ts#L310
Property 'dispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (9):
node_modules/@types/node/child_process.d.ts#L310
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (9):
node_modules/@types/node/web-globals/streams.d.ts#L17
'DecompressionStream' is referenced directly or indirectly in its own type annotation.
|
|
Build and test (9):
node_modules/@types/node/web-globals/streams.d.ts#L10
'CompressionStream' is referenced directly or indirectly in its own type annotation.
|
|
Build and test (14):
node_modules/@types/node/fs.d.ts#L337
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (14):
node_modules/@types/node/fs.d.ts#L331
Property 'asyncDispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (14):
node_modules/@types/node/fs.d.ts#L331
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (14):
node_modules/@types/node/events.d.ts#L403
Cannot find name 'Disposable'.
|
|
Build and test (14):
node_modules/@types/node/dgram.d.ts#L595
Property 'asyncDispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (14):
node_modules/@types/node/dgram.d.ts#L595
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (14):
node_modules/@types/node/child_process.d.ts#L310
Property 'dispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (14):
node_modules/@types/node/child_process.d.ts#L310
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (14):
node_modules/@types/node/web-globals/streams.d.ts#L17
'DecompressionStream' is referenced directly or indirectly in its own type annotation.
|
|
Build and test (14):
node_modules/@types/node/web-globals/streams.d.ts#L10
'CompressionStream' is referenced directly or indirectly in its own type annotation.
|
|
Build and test (8)
The strategy configuration was canceled because "build._9" failed
|
|
Build and test (8):
node_modules/@types/node/fs.d.ts#L337
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (8):
node_modules/@types/node/fs.d.ts#L331
Property 'asyncDispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (8):
node_modules/@types/node/fs.d.ts#L331
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (8):
node_modules/@types/node/events.d.ts#L403
Cannot find name 'Disposable'.
|
|
Build and test (8):
node_modules/@types/node/dgram.d.ts#L595
Property 'asyncDispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (8):
node_modules/@types/node/dgram.d.ts#L595
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (8):
node_modules/@types/node/child_process.d.ts#L310
Property 'dispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (8):
node_modules/@types/node/child_process.d.ts#L310
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (8):
node_modules/@types/node/web-globals/streams.d.ts#L17
'DecompressionStream' is referenced directly or indirectly in its own type annotation.
|
|
Build and test (8):
node_modules/@types/node/web-globals/streams.d.ts#L10
'CompressionStream' is referenced directly or indirectly in its own type annotation.
|
|
Build and test (11)
The strategy configuration was canceled because "build._9" failed
|
|
Build and test (11)
The operation was canceled.
|
|
Build and test (12)
The strategy configuration was canceled because "build._9" failed
|
|
Build and test (12)
The operation was canceled.
|
|
Build and test (13)
The strategy configuration was canceled because "build._9" failed
|
|
Build and test (13):
node_modules/@types/node/fs.d.ts#L337
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (13):
node_modules/@types/node/fs.d.ts#L331
Property 'asyncDispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (13):
node_modules/@types/node/fs.d.ts#L331
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (13):
node_modules/@types/node/events.d.ts#L403
Cannot find name 'Disposable'.
|
|
Build and test (13):
node_modules/@types/node/dgram.d.ts#L595
Property 'asyncDispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (13):
node_modules/@types/node/dgram.d.ts#L595
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (13):
node_modules/@types/node/child_process.d.ts#L310
Property 'dispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (13):
node_modules/@types/node/child_process.d.ts#L310
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (13):
node_modules/@types/node/web-globals/streams.d.ts#L17
'DecompressionStream' is referenced directly or indirectly in its own type annotation.
|
|
Build and test (13):
node_modules/@types/node/web-globals/streams.d.ts#L10
'CompressionStream' is referenced directly or indirectly in its own type annotation.
|
|
Build and test (10)
The strategy configuration was canceled because "build._9" failed
|
|
Build and test (10)
The operation was canceled.
|
|
Build and test (16)
The strategy configuration was canceled because "build._9" failed
|
|
Build and test (16)
The operation was canceled.
|
|
Build and test (17)
The strategy configuration was canceled because "build._9" failed
|
|
Build and test (17):
node_modules/@types/node/fs.d.ts#L337
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (17):
node_modules/@types/node/fs.d.ts#L331
Property 'asyncDispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (17):
node_modules/@types/node/fs.d.ts#L331
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (17):
node_modules/@types/node/events.d.ts#L403
Cannot find name 'Disposable'.
|
|
Build and test (17):
node_modules/@types/node/dgram.d.ts#L595
Property 'asyncDispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (17):
node_modules/@types/node/dgram.d.ts#L595
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (17):
node_modules/@types/node/child_process.d.ts#L310
Property 'dispose' does not exist on type 'SymbolConstructor'.
|
|
Build and test (17):
node_modules/@types/node/child_process.d.ts#L310
A computed property name in an ambient context must refer to an expression whose type is a literal type or a 'unique symbol' type.
|
|
Build and test (17):
node_modules/@types/node/web-globals/streams.d.ts#L17
'DecompressionStream' is referenced directly or indirectly in its own type annotation.
|
|
Build and test (17):
node_modules/@types/node/web-globals/streams.d.ts#L10
'CompressionStream' is referenced directly or indirectly in its own type annotation.
|
|
Build and test (15)
The strategy configuration was canceled because "build._9" failed
|
|
Build and test (15)
The operation was canceled.
|
|
Build and test (9)
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/
|
|
Build and test (14)
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/
|
|
Build and test (8)
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/
|
|
Build and test (11)
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/
|
|
Build and test (12)
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/
|
|
Build and test (13)
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/
|
|
Build and test (10)
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/
|
|
Build and test (16)
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/
|
|
Build and test (17)
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/
|
|
Build and test (15)
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/
|