build(deps): Bump minimatch and @typescript-eslint/eslint-plugin #22
dependabot[bot]Annotations
26 errors and 8 warnings
|
lint
Process completed with exit code 1.
|
|
unit tests (ubuntu-latest, 20)
Process completed with exit code 1.
|
|
unit tests (macos-latest, 20)
The strategy configuration was canceled because "tests.ubuntu-latest_20" failed
|
|
unit tests (macos-latest, 20)
The operation was canceled.
|
|
unit tests (windows-latest, 20)
The strategy configuration was canceled because "tests.ubuntu-latest_20" failed
|
|
unit tests (windows-latest, 20)
The operation was canceled.
|
|
unit tests (ubuntu-latest, 24)
The strategy configuration was canceled because "tests.ubuntu-latest_20" failed
|
|
unit tests (ubuntu-latest, 24)
The operation was canceled.
|
|
end-to-end (macos-latest)
Process completed with exit code 2.
|
|
end-to-end (macos-latest)
Property 'fuzz' does not exist on type 'It'.
|
|
end-to-end (macos-latest)
Property 'fuzz' does not exist on type 'It'.
|
|
end-to-end (macos-latest)
Property 'fuzz' does not exist on type 'It'.
|
|
end-to-end (ubuntu-latest)
The strategy configuration was canceled because "end-to-end.macos-latest" failed
|
|
end-to-end (ubuntu-latest)
The operation was canceled.
|
|
end-to-end (ubuntu-latest):
packages/fuzzer/addon.ts#L80
Cannot find name 'process'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node`.
|
|
end-to-end (ubuntu-latest):
packages/fuzzer/addon.ts#L76
Cannot find name '__dirname'. Did you mean 'dirName'?
|
|
end-to-end (ubuntu-latest):
packages/fuzzer/addon.ts#L75
Cannot find name '__dirname'. Did you mean 'dirName'?
|
|
end-to-end (ubuntu-latest):
packages/fuzzer/addon.ts#L74
Cannot find name '__dirname'. Did you mean 'dirName'?
|
|
end-to-end (ubuntu-latest):
packages/fuzzer/addon.ts#L73
Cannot find name '__dirname'. Did you mean 'dirName'?
|
|
end-to-end (ubuntu-latest):
packages/fuzzer/addon.ts#L41
Cannot find name 'Buffer'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node`.
|
|
end-to-end (ubuntu-latest):
packages/fuzzer/addon.ts#L24
Cannot find name 'Buffer'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node`.
|
|
end-to-end (ubuntu-latest):
packages/fuzzer/addon.ts#L21
Cannot find name 'Buffer'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node`.
|
|
end-to-end (ubuntu-latest):
packages/fuzzer/addon.ts#L18
Cannot find module 'path' or its corresponding type declarations.
|
|
end-to-end (ubuntu-latest):
packages/fuzzer/addon.ts#L17
Cannot find module 'fs' or its corresponding type declarations.
|
|
end-to-end (windows-latest)
The strategy configuration was canceled because "end-to-end.macos-latest" failed
|
|
end-to-end (windows-latest)
The operation was canceled.
|
|
lint
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. 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/
|
|
unit tests (ubuntu-latest, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
unit tests (macos-latest, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
unit tests (windows-latest, 20)
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 will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
unit tests (ubuntu-latest, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v3, actions/setup-node@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
end-to-end (macos-latest)
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. 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/
|
|
end-to-end (ubuntu-latest)
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. 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/
|
|
end-to-end (windows-latest)
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, ilammy/msvc-dev-cmd@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|