[Conductor SDK Error]: Failed to save schedule at handleSdkError (src/sdk/helpers/errors.ts:49:11) at SchedulerClient.saveSchedule (src/sdk/clients/scheduler/SchedulerClient.ts:32:21) at Object.<anonymous> (src/integration-tests/MetadataClient.complete.test.ts:321:7)

MetadataClient Complete Coverage › Task Tags › deleteTaskTag should remove a specific tag: src/integration-tests/MetadataClient.complete.test.ts#L258

expect(received).resolves.not.toThrow() Received promise rejected instead of resolved Rejected to value: [[Conductor SDK Error]: Failed to delete tag from task 'jsSdkTest-batch-task1-1776701902863'] at expect (node_modules/expect/build/index.js:2116:15) at Object.<anonymous> (src/integration-tests/MetadataClient.complete.test.ts:258:19)

MetadataClient Complete Coverage › Task Tags › setTaskTags should replace all tags: src/integration-tests/MetadataClient.complete.test.ts#L245

expect(received).resolves.not.toThrow() Received promise rejected instead of resolved Rejected to value: [[Conductor SDK Error]: Failed to set tags for task 'jsSdkTest-batch-task1-1776701902863'] at expect (node_modules/expect/build/index.js:2116:15) at Object.<anonymous> (src/integration-tests/MetadataClient.complete.test.ts:245:19)

MetadataClient Complete Coverage › Task Tags › getTaskTags should return the task tags: src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to get tags for task 'jsSdkTest-batch-task1-1776701902863' at handleSdkError (src/sdk/helpers/errors.ts:49:11) at MetadataClient.getTaskTags (src/sdk/clients/metadata/MetadataClient.ts:351:21) at Object.<anonymous> (src/integration-tests/MetadataClient.complete.test.ts:231:20)

MetadataClient Complete Coverage › Task Tags › addTaskTag should add a tag to a task definition: src/integration-tests/MetadataClient.complete.test.ts#L222

expect(received).resolves.not.toThrow() Received promise rejected instead of resolved Rejected to value: [[Conductor SDK Error]: Failed to add tag to task 'jsSdkTest-batch-task1-1776701902863'] at expect (node_modules/expect/build/index.js:2116:15) at Object.<anonymous> (src/integration-tests/MetadataClient.complete.test.ts:222:19)

MetadataClient Complete Coverage › Workflow Tags › deleteWorkflowTag should remove a specific tag: src/integration-tests/MetadataClient.complete.test.ts#L205

expect(received).resolves.not.toThrow() Received promise rejected instead of resolved Rejected to value: [[Conductor SDK Error]: Failed to delete tag from workflow 'jsSdkTest-metadata-wf-1776701902863'] at expect (node_modules/expect/build/index.js:2116:15) at Object.<anonymous> (src/integration-tests/MetadataClient.complete.test.ts:205:19)

MetadataClient Complete Coverage › Workflow Tags › setWorkflowTags should replace all tags: src/integration-tests/MetadataClient.complete.test.ts#L191

expect(received).resolves.not.toThrow() Received promise rejected instead of resolved Rejected to value: [[Conductor SDK Error]: Failed to set tags for workflow 'jsSdkTest-metadata-wf-1776701902863'] at expect (node_modules/expect/build/index.js:2116:15) at Object.<anonymous> (src/integration-tests/MetadataClient.complete.test.ts:191:19)

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

[Conductor SDK Error]: Failed to get tags for workflow 'jsSdkTest-metadata-wf-1776701902863' at handleSdkError (src/sdk/helpers/errors.ts:49:11) at MetadataClient.getWorkflowTags (src/sdk/clients/metadata/MetadataClient.ts:267:21) at Object.<anonymous> (src/integration-tests/MetadataClient.complete.test.ts:177:20)

MetadataClient Complete Coverage › Workflow Tags › addWorkflowTag should add a tag to a workflow definition: src/integration-tests/MetadataClient.complete.test.ts#L168

expect(received).resolves.not.toThrow() Received promise rejected instead of resolved Rejected to value: [[Conductor SDK Error]: Failed to add tag to workflow 'jsSdkTest-metadata-wf-1776701902863'] at expect (node_modules/expect/build/index.js:2116:15) at Object.<anonymous> (src/integration-tests/MetadataClient.complete.test.ts:168:19)

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

[Conductor SDK Error]: Failed to get all workflow definitions at handleSdkError (src/sdk/helpers/errors.ts:49:11) at MetadataClient.getAllWorkflowDefs (src/sdk/clients/metadata/MetadataClient.ts:207:21) at Object.<anonymous> (src/integration-tests/MetadataClient.complete.test.ts:154:28)

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.

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

SchemaClient › Schema CRUD › getAllSchemas should include the test schema: 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 Object.<anonymous> (src/integration-tests/SchemaClient.test.ts:35:20)

SchemaClient › Schema CRUD › getSchemaByName should return latest version: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SchemaClient › Schema CRUD › getSchema should return schema by name and version: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SchemaClient › Schema CRUD › registerSchema should create a new schema: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

E2E: 5-task workflow × 50 executions › 50 workflows with 5 sequential tasks each all complete with correct output: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

MetadataClient › Should unregister a task definition: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

MetadataClient › Should update a task definition: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

MetadataClient › Should register a task definition: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

TaskManager › Should create and run a workflow that sums two numbers: 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/readme.test.ts:199:41)

SDK Worker Registration › Worker execution (requires update-v2) › TaskHandler auto-discovers and executes decorated workers: src/integration-tests/utils/waitForWorkflowStatus.ts#L44

Workflow did not reach status COMPLETED within 60000ms at waitForWorkflowStatus (src/integration-tests/utils/waitForWorkflowStatus.ts:44:9) at Object.<anonymous> (src/integration-tests/WorkerRegistration.test.ts:139:28)

Node.js v22 - 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) › worker with concurrency processes multiple tasks: 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) › TaskHandler auto-discovers and executes decorated workers: 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() function registers workers in global registry: 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)

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

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

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

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

[Conductor SDK Error]: Failed to signal workflow at handleSdkError (src/sdk/helpers/errors.ts:49:11) at WorkflowExecutor.signal (src/sdk/clients/workflow/WorkflowExecutor.ts:634:21) at signalWithRetry (src/integration-tests/WorkflowExecutor.test.ts:698:17) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:713:11)

Node.js v22 - 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/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/WorkflowExecutor.complete.test.ts:64:14)

WorkflowExecutor Complete Coverage › Correlation IDs › getByCorrelationIds should return workflows by correlation: 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/WorkflowExecutor.complete.test.ts:64:14)

WorkflowExecutor Complete Coverage › Execution Info › search should find the workflow: src/integration-tests/WorkflowExecutor.complete.test.ts#L208

TypeError: Cannot read properties of undefined (reading 'startWorkflow') at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:208:35)

WorkflowExecutor Complete Coverage › Execution Info › search should find the workflow: 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/WorkflowExecutor.complete.test.ts:64:14)

WorkflowExecutor Complete Coverage › Execution Info › getWorkflowStatus should return status summary: src/integration-tests/WorkflowExecutor.complete.test.ts#L208

TypeError: Cannot read properties of undefined (reading 'startWorkflow') at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:208:35)

WorkflowExecutor Complete Coverage › Execution Info › getWorkflowStatus should return status summary: 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/WorkflowExecutor.complete.test.ts:64:14)

WorkflowExecutor Complete Coverage › Execution Info › getExecution should return full workflow with tasks: src/integration-tests/WorkflowExecutor.complete.test.ts#L208

TypeError: Cannot read properties of undefined (reading 'startWorkflow') at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:208:35)

WorkflowExecutor Complete Coverage › Execution Info › getExecution should return full workflow with tasks: 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/WorkflowExecutor.complete.test.ts:64:14)

WorkflowExecutor Complete Coverage › Start Methods › startWorkflowByName should start a workflow with direct params: 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/WorkflowExecutor.complete.test.ts:64:14)

WorkflowExecutor Complete Coverage › Start Methods › startWorkflows should start multiple workflows in batch: 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/WorkflowExecutor.complete.test.ts:64:14)

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

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

SchemaClient › Error Paths › getSchema should throw for non-existent schema: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SchemaClient › Schema Deletion › deleteSchemaByName should remove all versions: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SchemaClient › Schema Deletion › deleteSchema should remove a specific version: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SchemaClient › Schema CRUD › getSchema version 2 should return the updated schema: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SchemaClient › Schema CRUD › registerSchema with newVersion should create version 2: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SchemaClient › Schema CRUD › getAllSchemas should include the test schema: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SchemaClient › Schema CRUD › getSchemaByName should return latest version: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SchemaClient › Schema CRUD › getSchema should return schema by name and version: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SchemaClient › Schema CRUD › registerSchema should create a new schema: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

E2E: 5-task workflow × 50 executions › 50 workflows with 5 sequential tasks each all complete with correct output: src/sdk/helpers/errors.ts#L49

[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/E2EFiveTaskWorkflow.test.ts:113:20)

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.

Worker Advanced Features › MetricsCollector › should collect poll and execution metrics during workflow run: src/integration-tests/WorkerAdvanced.test.ts#L68

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/WorkerAdvanced.test.ts:68:9 at src/integration-tests/WorkerAdvanced.test.ts:67:11 at Object.<anonymous> (src/integration-tests/WorkerAdvanced.test.ts:38:19)

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)

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

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Certification worker metrics (#123) #521

Summary

Certification worker metrics (#123) #521

Uh oh!

pull_request.yml

Annotations