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

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

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

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

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

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

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

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

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

WorkflowExecutor Complete Coverage › Update Task Sync › updateTaskSync should complete a task and return workflow: src/sdk/helpers/errors.ts#L49

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

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#L214

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

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) › 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

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:624: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

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

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

WorkflowExecutor Complete Coverage › Correlation IDs › getByCorrelationIds should return workflows by correlation: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

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

WorkflowExecutor Complete Coverage › Execution Info › getWorkflowStatus (V4+) › 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 (V4+) › getWorkflowStatus should return status summary: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

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

WorkflowExecutor Complete Coverage › Start Methods › startWorkflowByName should start a workflow with direct params: src/sdk/createConductorClient/helpers/handleAuth.ts#L65

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

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

The run was canceled by @v1r3n.

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

The run was canceled by @v1r3n.

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

The run was canceled by @v1r3n.

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

The operation was canceled.

Continuous Integration

The run was canceled by @v1r3n.

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 - 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 - 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 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 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 v20 - integration v5 (shard 3/3)

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

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

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

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

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

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

Codecov: Failed to properly upload report: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: add --provenance to npm publish to trigger OIDC trusted publishing #525

Summary

fix: add --provenance to npm publish to trigger OIDC trusted publishing #525

Uh oh!

pull_request.yml

Annotations