[Conductor SDK Error]: Failed to generate authorization token: Unknown error (HTTP 502) at getNewToken (src/sdk/createConductorClient/helpers/handleAuth.ts:65:13) at handleAuth (src/sdk/createConductorClient/helpers/handleAuth.ts:123:7) at createConductorClient (src/sdk/createConductorClient/createConductorClient.ts:61:18) at Object.<anonymous> (src/integration-tests/MetadataClient.complete.test.ts:50:20)

MetadataClient Complete Coverage › Task Tags › addTaskTag should add a tag to a task definition: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

MetadataClient Complete Coverage › Workflow Tags › deleteWorkflowTag should remove a specific tag: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

MetadataClient Complete Coverage › Workflow Tags › setWorkflowTags should replace all tags: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

MetadataClient Complete Coverage › Workflow Tags › getWorkflowTags should return the workflow tags: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

MetadataClient Complete Coverage › Workflow Tags › addWorkflowTag should add a tag to a workflow definition: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

MetadataClient Complete Coverage › Batch Task Registration › getAllWorkflowDefs should return all workflow definitions: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

MetadataClient Complete Coverage › Batch Task Registration › getAllTaskDefs should return all task definitions: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

MetadataClient Complete Coverage › Batch Task Registration › registerTasks should register multiple task definitions at once: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

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

[Conductor SDK Error]: Failed to update state for workflow '96d4e0b5-31cf-11f1-8547-063f86a426d7' at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.updateState (src/sdk/clients/workflow/WorkflowExecutor.ts:786:21) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:639:22)

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

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

SDK Worker Registration › Worker execution (requires update-v2) › event listeners receive lifecycle events: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

[Conductor SDK Error]: Failed to generate authorization token: Unknown error (HTTP 503) at getNewToken (src/sdk/createConductorClient/helpers/handleAuth.ts:65:13) at handleAuth (src/sdk/createConductorClient/helpers/handleAuth.ts:123:7) at createConductorClient (src/sdk/createConductorClient/createConductorClient.ts:61:18) at createClientWithRetry (src/integration-tests/utils/createClientWithRetry.ts:15:14) at Object.<anonymous> (src/integration-tests/WorkerRegistration.test.ts:31:20)

SDK Worker Registration › Worker execution (requires update-v2) › NonRetryableException marks task as terminal failure: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SDK Worker Registration › worker with domain isolation: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SDK Worker Registration › Worker execution (requires update-v2) › worker with concurrency processes multiple tasks: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SDK Worker Registration › Worker execution (requires update-v2) › TaskHandler auto-discovers and executes decorated workers: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SDK Worker Registration › worker() function registers workers in global registry: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with DURABLE + BLOCKING_TASK_INPUT: 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:622:26)

WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with DURABLE + BLOCKING_TASK: src/sdk/helpers/errors.ts#L49

EventClient › Event Executions and Statistics › Should get all active event handlers (execution view): src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to add event handler at handleSdkError (src/sdk/helpers/errors.ts:49:11) at EventClient.addEventHandler (src/sdk/clients/event/EventClient.ts:75:21) at Object.<anonymous> (src/integration-tests/EventClient.test.ts:632:7)

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)

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

Workflow d1887c59-31cf-11f1-a524-8e8815462681 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)

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

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

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

Process completed with exit code 1.

WorkflowResourceService › Should test a workflow: src/integration-tests/WorkflowResourceService.test.ts#L24

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/WorkflowResourceService.test.ts:24:7 at Object.<anonymous> (src/integration-tests/WorkflowResourceService.test.ts:9:9)

Node.js v24 - integration v4 (shard 2/3)

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

Node.js v24 - integration v4 (shard 2/3)

Process completed with exit code 1.

WorkflowExecutor Complete Coverage › Start Methods › startWorkflows should start multiple workflows in batch: src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to start workflow: Response body object should not be disturbed or locked at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.startWorkflow (src/sdk/clients/workflow/WorkflowExecutor.ts:83:21) at async Promise.all (index 0) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:180:19)

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.

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

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

certification worker #514

Summary

certification worker #514

Uh oh!

pull_request.yml

Annotations