Skip to content

Standardized metrics export - feature flagged #529

Standardized metrics export - feature flagged

Standardized metrics export - feature flagged #529

Triggered via pull request May 4, 2026 17:34
Status Failure
Total duration 15m 5s
Artifacts

pull_request.yml

on: pull_request
Matrix: integration-tests-v4
Matrix: integration-tests
Matrix: unit-tests
Fit to window
Zoom out
Zoom in

Annotations

30 errors and 22 warnings
linter: src/sdk/clients/worker/events/types.ts#L140
An interface declaring no members is equivalent to its supertype
linter: src/sdk/clients/worker/__tests__/LeaseTracker.test.ts#L2
'LEASE_EXTEND_DURATION_FACTOR' is defined but never used. Allowed unused vars must match /^_/u
linter: src/sdk/clients/worker/__tests__/LeaseTracker.test.ts#L1
'LeaseInfo' is defined but never used. Allowed unused vars must match /^_/u
linter: src/sdk/builders/tasks/pullWorkflowMessages.ts#L19
Type number trivially inferred from a number literal, remove type annotation
linter: src/integration-tests/LeaseExtension.validation.test.ts#L181
Forbidden non-null assertion
linter: src/integration-tests/LeaseExtension.validation.test.ts#L180
Forbidden non-null assertion
linter: src/integration-tests/LeaseExtension.validation.test.ts#L136
Forbidden non-null assertion
linter: src/integration-tests/LeaseExtension.validation.test.ts#L135
Forbidden non-null assertion
linter: src/integration-tests/LeaseExtension.validation.test.ts#L120
Forbidden non-null assertion
linter: src/integration-tests/LeaseExtension.validation.test.ts#L59
'taskClient' is assigned a value but never used. Allowed unused vars must match /^_/u
Node.js v20 - integration v5 (shard 2/3)
Failed test were found and 'fail-on-error' option is set to true
WorkflowExecutor Complete Coverage › Workflow Control (pause/resume/terminate/restart/retry) › pause and resume should work on a running workflow: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:63:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:115:5)
WorkflowExecutor Complete Coverage › Correlation IDs › getByCorrelationIds should return workflows by correlation: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:63:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:115:5)
WorkflowExecutor Complete Coverage › Execution Info › search should find the workflow: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to start workflow: No such workflow found by name: jsSdkTest-simpleWf-1777916115229, version: 1 at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.startWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:111:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:208:20)
WorkflowExecutor Complete Coverage › Execution Info › search should find the workflow: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:63:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:115:5)
WorkflowExecutor Complete Coverage › Execution Info › getWorkflowStatus (V4+) › getWorkflowStatus should return status summary: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to start workflow: No such workflow found by name: jsSdkTest-simpleWf-1777916115229, version: 1 at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.startWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:111:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:208:20)
WorkflowExecutor Complete Coverage › Execution Info › getWorkflowStatus (V4+) › getWorkflowStatus should return status summary: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:63:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:115:5)
WorkflowExecutor Complete Coverage › Execution Info › getExecution should return full workflow with tasks: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to start workflow: No such workflow found by name: jsSdkTest-simpleWf-1777916115229, version: 1 at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.startWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:111:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:208:20)
WorkflowExecutor Complete Coverage › Execution Info › getExecution should return full workflow with tasks: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:63:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:115:5)
WorkflowExecutor Complete Coverage › Start Methods › startWorkflowByName should start a workflow with direct params: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:63:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:115:5)
WorkflowExecutor Complete Coverage › Start Methods › startWorkflows should start multiple workflows in batch: src/sdk/helpers/errors.ts#L49
[Conductor SDK Error]: Failed to register workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.registerWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:63:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:115:5)
Node.js v22 - integration v5 (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
Node.js v22 - integration v5 (shard 1/3)
Process completed with exit code 1.
Node.js v24 - integration v5 (shard 1/3)
Failed test were found and 'fail-on-error' option is set to true
Node.js v24 - integration v5 (shard 1/3)
Process completed with exit code 1.
SDK Worker Registration › Worker execution (requires update-v2) › TaskHandler auto-discovers and executes decorated workers: src/integration-tests/WorkerRegistration.test.ts#L70
thrown: "Exceeded timeout of 90000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at src/integration-tests/WorkerRegistration.test.ts:70:7 at src/integration-tests/WorkerRegistration.test.ts:69:21 at Object.<anonymous> (src/integration-tests/WorkerRegistration.test.ts:25:9)
Node.js v24 - integration v5 (shard 2/3)
Failed test were found and 'fail-on-error' option is set to true
Node.js v24 - integration v5 (shard 2/3)
Process completed with exit code 1.
TaskRunner › worker example: src/integration-tests/TaskRunner.test.ts#L29
thrown: "Exceeded timeout of 120000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at src/integration-tests/TaskRunner.test.ts:29:7 at Object.<anonymous> (src/integration-tests/TaskRunner.test.ts:13:9)
WorkflowExecutor Complete Coverage › Workflow Control (pause/resume/terminate/restart/retry) › pause and resume should work on a running workflow: src/integration-tests/WorkflowExecutor.complete.test.ts#L283
thrown: "Exceeded timeout of 120000 ms for a test. Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout." at src/integration-tests/WorkflowExecutor.complete.test.ts:283:9 at src/integration-tests/WorkflowExecutor.complete.test.ts:282:21 at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:42:9)
linter
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. 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.js v20 - integration v4 (shard 1/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v24 - unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v20 - unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v22 - unit tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v20 - integration v5 (shard 1/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v20 - integration v4 (shard 2/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v20 - integration v5 (shard 3/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v20 - integration v5 (shard 2/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v20 - integration v4 (shard 3/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v22 - integration v4 (shard 1/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v22 - integration v5 (shard 2/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v22 - integration v4 (shard 2/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v22 - integration v4 (shard 3/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v22 - integration v5 (shard 3/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v24 - integration v4 (shard 1/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v22 - integration v5 (shard 1/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v24 - integration v4 (shard 2/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v24 - integration v5 (shard 1/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v24 - integration v4 (shard 3/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v24 - integration v5 (shard 3/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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.js v24 - integration v5 (shard 2/3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. 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/