[Conductor SDK Error]: Failed to start workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.startWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:83:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:694:20)

WorkflowExecutor Complete Coverage › GoBack Methods › goBackToTask should rerun from a matching task: src/sdk/helpers/errors.ts#L49

WorkflowExecutor Complete Coverage › Update State › updateState should update workflow and task state: src/sdk/helpers/errors.ts#L49

WorkflowExecutor Complete Coverage › Update Variables › updateVariables should update workflow variables: src/sdk/helpers/errors.ts#L49

WorkflowExecutor Complete Coverage › Test Workflow › testWorkflow should simulate a workflow execution: src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to get workflow definition 'jsSdkTest-taskWf-1774640461685' at handleSdkError (src/sdk/helpers/errors.ts:49:11) at MetadataClient.getWorkflowDef (src/sdk/clients/metadata/MetadataClient.ts:153:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:576:21)

WorkflowExecutor Complete Coverage › Delete Workflow › deleteWorkflow should remove a completed workflow execution: src/sdk/helpers/errors.ts#L49

WorkflowExecutor Complete Coverage › Skip Task › skipTasksFromWorkflow should skip a scheduled task: src/sdk/helpers/errors.ts#L49

WorkflowExecutor Complete Coverage › Rerun › reRun should re-execute a completed workflow from a task: src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to update task by reference name at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.updateTaskByRefName (src/sdk/clients/workflow/WorkflowExecutor.ts:552:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:495:7)

WorkflowExecutor Complete Coverage › Task Updates › getTask should return task details: src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to get execution for 'undefined': Invalid UUID Provided {workflowId} at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.getExecution (src/sdk/clients/workflow/WorkflowExecutor.ts:293:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:392:25)

WorkflowExecutor Complete Coverage › Task Updates › updateTaskByRefName should complete a task by reference name: src/sdk/helpers/errors.ts#L49

Node.js v20 - integration v4 (shard 1/3)

Failed test were found and 'fail-on-error' option is set to true

Node.js v20 - integration v4 (shard 1/3)

Process completed with exit code 1.

TaskManager › update task example: src/integration-tests/readme.test.ts#L93

thrown: "Exceeded timeout of 60000 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/readme.test.ts:93:7 at Object.<anonymous> (src/integration-tests/readme.test.ts:13:9)

WorkflowExecutor › Should run workflow with http task with asyncComplete true: src/integration-tests/WorkflowExecutor.test.ts#L212

expect(received).toEqual(expected) // deep equality Expected: "IN_PROGRESS" Received: "FAILED_WITH_TERMINAL_ERROR" at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:212:24)

Node.js v20 - integration v5 (shard 1/3)

Failed test were found and 'fail-on-error' option is set to true

Node.js v20 - integration v5 (shard 1/3)

Process completed with exit code 1.

SDK Worker Registration › update-v2 endpoint verification › SDK detects and uses /api/tasks/update-v2 on v5 server: src/integration-tests/WorkerRegistration.test.ts#L674

thrown: "Exceeded timeout of 60000 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:674:9 at src/integration-tests/WorkerRegistration.test.ts:673:21 at Object.<anonymous> (src/integration-tests/WorkerRegistration.test.ts:25:9)

WorkflowExecutor › Should be able to execute workflow synchronously: src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to execute workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.executeWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:143:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:108:25)

Node.js v20 - integration v5 (shard 3/3)

Failed test were found and 'fail-on-error' option is set to true

Node.js v20 - integration v5 (shard 3/3)

Process completed with exit code 1.

SecretClient › Secret CRUD › getSecret should return the stored value: src/integration-tests/SecretClient.test.ts#L54

thrown: "Exceeded timeout of 60000 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/SecretClient.test.ts:54:9 at src/integration-tests/SecretClient.test.ts:42:11 at Object.<anonymous> (src/integration-tests/SecretClient.test.ts:14:9)

Node.js v22 - integration v5 (shard 2/3)

Failed test were found and 'fail-on-error' option is set to true

Node.js v22 - integration v5 (shard 2/3)

Process completed with exit code 1.

ConductorWorkflow DSL › SubWorkflow Task › toSubWorkflowTask() should embed child workflow in parent: src/sdk/helpers/errors.ts#L49

ConductorWorkflow DSL › Fork/Join › fork() should create parallel branches with auto-join: 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:62:21) at ConductorWorkflow.register (src/sdk/builders/ConductorWorkflow.ts:268:5) at Object.<anonymous> (src/integration-tests/ConductorWorkflow.test.ts:234:7)

Node.js v22 - integration v4 (shard 1/3)

Failed test were found and 'fail-on-error' option is set to true

Node.js v22 - integration v4 (shard 1/3)

Process completed with exit code 1.

WorkflowExecutor › Should run workflow with http task with asyncComplete true: src/integration-tests/WorkflowExecutor.test.ts#L212

expect(received).toEqual(expected) // deep equality Expected: "IN_PROGRESS" Received: "FAILED_WITH_TERMINAL_ERROR" at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:212:24)

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.

TaskManager › worker example: src/integration-tests/readme.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/readme.test.ts:29:7 at Object.<anonymous> (src/integration-tests/readme.test.ts:13:9)

Node.js v24 - integration v5 (shard 3/3)

Failed test were found and 'fail-on-error' option is set to true

Node.js v24 - integration v5 (shard 3/3)

Process completed with exit code 1.

TaskManager › TaskManager workflow execution › multi worker example: src/integration-tests/utils/waitForWorkflowCompletion.ts#L43

Workflow 26b949cd-2a16-11f1-863c-063f86a426d7 did not complete within 30000ms at waitForWorkflowCompletion (src/integration-tests/utils/waitForWorkflowCompletion.ts:43:9) at Object.<anonymous> (src/integration-tests/TaskManager.test.ts:356:28)

ApplicationClient › Role Management › Should add and remove role from application: src/integration-tests/ApplicationClient.test.ts#L23

thrown: "Exceeded timeout of 60000 ms for a hook. 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/ApplicationClient.test.ts:23:12 at Object.<anonymous> (src/integration-tests/ApplicationClient.test.ts:13: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 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 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 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 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 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 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 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 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 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 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/

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 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 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 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 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 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/

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

certification worker #510

Summary

certification worker #510

Uh oh!

pull_request.yml

Annotations