typecheck tests in CI/CD #290
mistvalci.yml
on: push
test_node_lts
24s
Matrix: test_node_other
Annotations
17 errors and 5 warnings
|
test_node_lts:
plugins/redis/test_redis_cache.ts#L0
Type 'RedisCache' is not assignable to type 'INodeFetchCacheCache'.
|
|
test_node_lts:
plugins/redis/test_redis_cache.ts#L0
Type 'RedisCache' is not assignable to type 'INodeFetchCacheCache'.
|
|
test_node_lts:
plugins/redis/test_redis_cache.ts#L0
Type 'RedisCache' is not assignable to type 'INodeFetchCacheCache'.
|
|
test_node_lts:
plugins/redis/test_redis_cache.ts#L0
Type 'RedisCache' is not assignable to type 'INodeFetchCacheCache'.
|
|
test_node_lts:
plugins/redis/test_redis_cache.ts#L0
Type 'RedisCache' is not assignable to type 'INodeFetchCacheCache'.
|
|
test_node_lts:
plugins/redis/test_redis_cache.ts#L0
Type 'RedisCache' is not assignable to type 'INodeFetchCacheCache'.
|
|
test_node_lts:
plugins/redis/test_redis_cache.ts#L0
Type 'RedisCache' is not assignable to type 'INodeFetchCacheCache'.
|
|
test_node_lts:
plugins/redis/test_redis_cache.ts#L0
Type 'RedisCache' is not assignable to type 'INodeFetchCacheCache'.
|
|
test_node_lts:
plugins/redis/redis_cache.ts#L0
Property 'set' in type 'RedisCache' is not assignable to the same property in base type 'INodeFetchCacheCache'.
|
|
test_node_lts:
plugins/redis/redis_cache.ts#L0
Property 'get' in type 'RedisCache' is not assignable to the same property in base type 'INodeFetchCacheCache'.
|
|
test_node_other (20.x)
Process completed with exit code 89.
|
|
test_node_other (18.19.0)
The strategy configuration was canceled because "test_node_other._20_x" failed
|
|
test_node_other (18.19.0)
The operation was canceled.
|
|
test_node_other (18.x)
The strategy configuration was canceled because "test_node_other._20_x" failed
|
|
test_node_other (18.x)
The operation was canceled.
|
|
test_node_other (23.x)
The strategy configuration was canceled because "test_node_other._20_x" failed
|
|
test_node_other (23.x)
The operation was canceled.
|
|
test_node_lts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/setup-node@v1. 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/
|
|
test_node_other (20.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/setup-node@v1. 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/
|
|
test_node_other (18.19.0)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/setup-node@v1. 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/
|
|
test_node_other (18.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/setup-node@v1. 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/
|
|
test_node_other (23.x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v2, actions/setup-node@v1. 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/
|