chore(deps): update dependency @types/proxy to v2 #2020
renovate[bot]Annotations
14 errors and 15 warnings
|
check
Process completed with exit code 1.
|
|
typescript(TS7016):
test/options.dispatcher.test.ts#L3
Could not find a declaration file for module 'proxy'. '/home/runner/work/urllib/urllib/node_modules/.pnpm/proxy@1.0.2/node_modules/proxy/proxy.js' implicitly has an 'any' type.
|
|
Test (macos-latest, 22)
Process completed with exit code 1.
|
|
Test (macos-latest, 20)
Process completed with exit code 1.
|
|
Test (windows-latest, 22)
Process completed with exit code 1.
|
|
Test (windows-latest, 20)
Process completed with exit code 1.
|
|
Test (ubuntu-latest, 20)
Process completed with exit code 1.
|
|
Test (ubuntu-latest, 24)
Process completed with exit code 1.
|
|
Test (ubuntu-latest, 25)
Process completed with exit code 1.
|
|
Test (ubuntu-latest, 22)
Process completed with exit code 1.
|
|
Test (windows-latest, 25)
Process completed with exit code 1.
|
|
Test (windows-latest, 24)
Process completed with exit code 1.
|
|
Test (macos-latest, 24)
Process completed with exit code 1.
|
|
Test (macos-latest, 25)
Process completed with exit code 1.
|
|
check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@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/
|
|
eslint(no-extend-native):
src/utils.ts#L269
String prototype is read-only, properties should not be added.
|
|
eslint(no-extend-native):
src/utils.ts#L254
String prototype is read-only, properties should not be added.
|
|
Test (macos-latest, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@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/
|
|
Test (macos-latest, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@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/
|
|
Test (windows-latest, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@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/
|
|
Test (windows-latest, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@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/
|
|
Test (ubuntu-latest, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@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/
|
|
Test (ubuntu-latest, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@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/
|
|
Test (ubuntu-latest, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@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/
|
|
Test (ubuntu-latest, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@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/
|
|
Test (windows-latest, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@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/
|
|
Test (windows-latest, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@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/
|
|
Test (macos-latest, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@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/
|
|
Test (macos-latest, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: voidzero-dev/setup-vp@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/
|