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

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)

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/integration-tests/WorkflowExecutor.test.ts#L361

Failed to register workflows: [Conductor SDK Error]: Failed to register workflow definition: Response body object should not be disturbed or locked at registerAllWorkflows (src/integration-tests/WorkflowExecutor.test.ts:361:15) at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:307:7)

WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with DURABLE + BLOCKING_TASK: src/integration-tests/WorkflowExecutor.test.ts#L361

WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with DURABLE + BLOCKING_WORKFLOW: src/integration-tests/WorkflowExecutor.test.ts#L361

WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with DURABLE + TARGET_WORKFLOW: src/integration-tests/WorkflowExecutor.test.ts#L361

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/integration-tests/WorkflowExecutor.test.ts#L361

WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with SYNC + BLOCKING_TASK: src/integration-tests/WorkflowExecutor.test.ts#L361

WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with SYNC + BLOCKING_WORKFLOW: src/integration-tests/WorkflowExecutor.test.ts#L361

WorkflowExecutor › Execute with Return Strategy and Consistency › Execute Workflow with Return Strategies and Consistency Levels › Should execute complex workflow with SYNC + TARGET_WORKFLOW and validate all aspects: src/integration-tests/WorkflowExecutor.test.ts#L361

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

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

ConductorWorkflow DSL › Start Workflow › startWorkflow() with correlationId should set 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/ConductorWorkflow.test.ts:49:14)

ConductorWorkflow DSL › Start Workflow › startWorkflow() should start asynchronously and return ID: 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/ConductorWorkflow.test.ts:49:14)

ConductorWorkflow DSL › Execute Workflow › execute() should run workflow synchronously and return result: 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/ConductorWorkflow.test.ts:49:14)

ConductorWorkflow DSL › Build and Register › toWorkflowDef should return a valid WorkflowDef: 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/ConductorWorkflow.test.ts:49:14)

ConductorWorkflow DSL › Build and Register › getName and getVersion should return correct values: 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/ConductorWorkflow.test.ts:49:14)

ConductorWorkflow DSL › Build and Register › should build a workflow with add() and register it: 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/ConductorWorkflow.test.ts:49:14)

IntegrationClient › Deletion › deleteIntegrationProvider should remove the provider: src/integration-tests/IntegrationClient.test.ts#L383

expect(received).resolves.not.toThrow() Received promise rejected instead of resolved Rejected to value: [[Conductor SDK Error]: Failed to delete integration provider 'jsSdkTest_provider_1775059887983'] at expect (node_modules/expect/build/index.js:2116:15) at Object.<anonymous> (src/integration-tests/IntegrationClient.test.ts:383:19)

IntegrationClient › Deletion › deleteIntegrationApi should remove the API: src/integration-tests/IntegrationClient.test.ts#L372

expect(received).resolves.not.toThrow() Received promise rejected instead of resolved Rejected to value: [[Conductor SDK Error]: Failed to delete integration API 'jsSdkTest_api_1775059887983' for provider 'jsSdkTest_provider_1775059887983'] at expect (node_modules/expect/build/index.js:2116:15) at Object.<anonymous> (src/integration-tests/IntegrationClient.test.ts:372:19)

IntegrationClient › Prompt Association › getPromptsWithIntegration should return associated prompts: src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to get prompts for integration 'jsSdkTest_api_1775059887983' at handleSdkError (src/sdk/helpers/errors.ts:49:11) at IntegrationClient.getPromptsWithIntegration (src/sdk/clients/integration/IntegrationClient.ts:343:21) at Object.<anonymous> (src/integration-tests/IntegrationClient.test.ts:356:23)

IntegrationClient › Prompt Association › associatePromptWithIntegration should link a prompt: src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to save prompt 'jsSdkTest_prompt_for_integration_1775059887983' at handleSdkError (src/sdk/helpers/errors.ts:49:11) at PromptClient.savePrompt (src/sdk/clients/prompt/PromptClient.ts:38:21) at Object.<anonymous> (src/integration-tests/IntegrationClient.test.ts:324:9)

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

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

SecretClient › Secret CRUD › listSecretsThatUserCanGrantAccessTo should return an array: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SecretClient › Secret CRUD › listAllSecretNames should include the test secret: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SecretClient › Secret CRUD › putSecret should update an existing secret: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SecretClient › Secret CRUD › getSecret should return the stored value: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SecretClient › Secret CRUD › secretExists should return true for existing secret: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SecretClient › Secret CRUD › putSecret should store a new secret: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

SchedulerClient › Should be able to retrieve next (default 3) execution times for a scheduler: src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to get next few schedules at handleSdkError (src/sdk/helpers/errors.ts:49:11) at SchedulerClient.getNextFewSchedules (src/sdk/clients/scheduler/SchedulerClient.ts:183:21) at Object.<anonymous> (src/integration-tests/SchedulerClient.test.ts:165:20)

SchedulerClient › Should be able to delete the schedule: src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to delete schedule 'jsSdkTestSchedule_1775060093741' at handleSdkError (src/sdk/helpers/errors.ts:49:11) at SchedulerClient.deleteSchedule (src/sdk/clients/scheduler/SchedulerClient.ts:134:21) at Object.<anonymous> (src/integration-tests/SchedulerClient.test.ts:148:5)

SchedulerClient › Should be able to pause the schedule: src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to pause schedule 'jsSdkTestSchedule_1775060093741' at handleSdkError (src/sdk/helpers/errors.ts:49:11) at SchedulerClient.pauseSchedule (src/sdk/clients/scheduler/SchedulerClient.ts:98:21) at Object.<anonymous> (src/integration-tests/SchedulerClient.test.ts:136:5)

SchedulerClient › Should be able to see the result in executed schedule: src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to search schedules at handleSdkError (src/sdk/helpers/errors.ts:49:11) at SchedulerClient.search (src/sdk/clients/scheduler/SchedulerClient.ts:62:21) at Object.<anonymous> (src/integration-tests/SchedulerClient.test.ts:123:20)

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

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

Process completed with exit code 1.

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)

WorkflowExecutor › Should return workflow status detail: src/integration-tests/WorkflowExecutor.test.ts#L138

expect(received).toBeDefined() Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:138:25)

WorkflowExecutor › Should be able to get workflow execution status: src/integration-tests/WorkflowExecutor.test.ts#L123

expect(received).toBeDefined() Received: undefined at Object.<anonymous> (src/integration-tests/WorkflowExecutor.test.ts:123:25)

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

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

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

Worker Advanced Features › MetricsCollector › toPrometheusText should produce valid Prometheus format: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

Worker Advanced Features › MetricsCollector › should collect poll and execution metrics during workflow run: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

ApplicationClient › Error Handling › Should throw error when toggling status of non-existent access key: src/sdk/helpers/errors.ts#L49

[Conductor SDK Error]: Failed to create application at handleSdkError (src/sdk/helpers/errors.ts:49:11) at ApplicationClient.createApplication (src/sdk/clients/application/ApplicationClient.ts:55:21) at Object.<anonymous> (src/integration-tests/ApplicationClient.test.ts:511:26)

ApplicationClient › Error Handling › Should throw error when deleting non-existent access key: src/sdk/helpers/errors.ts#L49

ApplicationClient › Tag Management › Should delete multiple tags from an application: src/sdk/helpers/errors.ts#L49

ApplicationClient › Tag Management › Should delete a single tag from an application: src/sdk/helpers/errors.ts#L49

ApplicationClient › Tag Management › Should get tags for an application: src/sdk/helpers/errors.ts#L49

ApplicationClient › Tag Management › Should add multiple tags to an application: src/sdk/helpers/errors.ts#L49

ApplicationClient › Tag Management › Should add a single tag to an application: src/sdk/helpers/errors.ts#L49

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)

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 › Execution Info › search should find the workflow: src/integration-tests/WorkflowExecutor.complete.test.ts#L207

thrown: "Exceeded timeout of 120000 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/WorkflowExecutor.complete.test.ts:207:14 at src/integration-tests/WorkflowExecutor.complete.test.ts:204:11 at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:42:9)

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

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

WorkflowExecutor Complete Coverage › Start Methods › startWorkflowByName should start a workflow with direct params: src/integration-tests/WorkflowExecutor.complete.test.ts#L134

thrown: "Exceeded timeout of 120000 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/WorkflowExecutor.complete.test.ts:134:12 at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:42:9)

WorkflowExecutor Complete Coverage › Start Methods › startWorkflows should start multiple workflows in batch: src/integration-tests/WorkflowExecutor.complete.test.ts#L134

thrown: "Exceeded timeout of 120000 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/WorkflowExecutor.complete.test.ts:134:12 at Object.<anonymous> (src/integration-tests/WorkflowExecutor.complete.test.ts:42:9)

linter

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 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 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 v22 - unit tests

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js v20 - integration 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 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 1/3)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

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

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js v22 - integration 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 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 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 v5 (shard 1/3)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, codecov/codecov-action@v4, dorny/test-reporter@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js v24 - integration v4 (shard 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 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

test ci on main #513

Summary

test ci on main #513

Uh oh!

pull_request.yml

Annotations