chore(deps): update jest monorepo to v30 (major) #3092
Annotations
23 errors and 3 warnings
|
node v22
Process completed with exit code 1.
|
|
node v22:
packages/block-tracking/__tests__/block-tracking.test.ts#L419
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v22:
packages/block-tracking/__tests__/block-tracking.test.ts#L394
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v22:
packages/block-tracking/__tests__/block-tracking.test.ts#L372
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v22:
packages/block-tracking/__tests__/block-tracking.test.ts#L350
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v22:
packages/block-tracking/__tests__/block-tracking.test.ts#L328
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v22:
packages/block-tracking/__tests__/block-tracking.test.ts#L307
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v22:
packages/block-tracking/__tests__/block-tracking.test.ts#L286
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v22:
packages/block-tracking/__tests__/block-tracking.test.ts#L268
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v22:
packages/block-tracking/__tests__/block-tracking.test.ts#L250
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v20
The strategy configuration was canceled because "node._22" failed
|
|
node v20
Process completed with exit code 1.
|
|
node v20:
packages/block-tracking/__tests__/block-tracking.test.ts#L419
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v20:
packages/block-tracking/__tests__/block-tracking.test.ts#L394
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v20:
packages/block-tracking/__tests__/block-tracking.test.ts#L372
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v20:
packages/block-tracking/__tests__/block-tracking.test.ts#L350
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v20:
packages/block-tracking/__tests__/block-tracking.test.ts#L328
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v20:
packages/block-tracking/__tests__/block-tracking.test.ts#L307
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v20:
packages/block-tracking/__tests__/block-tracking.test.ts#L286
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v20:
packages/block-tracking/__tests__/block-tracking.test.ts#L268
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v20:
packages/block-tracking/__tests__/block-tracking.test.ts#L250
Property 'toThrowError' does not exist on type 'JestMatchers<() => void>'.
|
|
node v18
The strategy configuration was canceled because "node._22" failed
|
|
node v18
The operation was canceled.
|
|
node v22
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
node v20
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|
|
node v18
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@cdca7365b2dadb8aad0a33bc7601856ffabcc48e, styfle/cancel-workflow-action@85880fa0301c86cca9da44039ee3bb12d3bedbfa. 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/
|