Definition for rule '@typescript-eslint/ban-types' was not found

Definition for rule '@typescript-eslint/ban-types' was not found

Definition for rule '@typescript-eslint/ban-types' was not found

Definition for rule '@typescript-eslint/ban-types' was not found

Definition for rule '@typescript-eslint/ban-types' was not found

Definition for rule '@typescript-eslint/ban-types' was not found

Definition for rule '@typescript-eslint/ban-types' was not found

Expected the Promise rejection reason to be an Error

Functions that return promises must be async. Consider adding an explicit return type annotation if the function is intended to return a union of promise and non-promise types

Definition for rule '@typescript-eslint/ban-types' was not found

The strategy configuration was canceled because "build-and-test._19_x" failed

Definition for rule '@typescript-eslint/ban-types' was not found

Definition for rule '@typescript-eslint/ban-types' was not found

Definition for rule '@typescript-eslint/ban-types' was not found

Definition for rule '@typescript-eslint/ban-types' was not found

Definition for rule '@typescript-eslint/ban-types' was not found

Definition for rule '@typescript-eslint/ban-types' was not found

Definition for rule '@typescript-eslint/ban-types' was not found

Expected the Promise rejection reason to be an Error

Functions that return promises must be async. Consider adding an explicit return type annotation if the function is intended to return a union of promise and non-promise types

Definition for rule '@typescript-eslint/ban-types' was not found

The strategy configuration was canceled because "build-and-test._19_x" failed

The operation was canceled.

The strategy configuration was canceled because "build-and-test._19_x" failed

The operation was canceled.

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@34e114876b0b11c390a56381ad16ebd13914f8d5, 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/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

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@34e114876b0b11c390a56381ad16ebd13914f8d5, 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/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

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@34e114876b0b11c390a56381ad16ebd13914f8d5, 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/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

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@34e114876b0b11c390a56381ad16ebd13914f8d5, 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/