Skip to content

Conversation

AnatoliB
Copy link
Collaborator

@AnatoliB AnatoliB commented Oct 2, 2025

Allow overriding orchestration version when starting orchestrations via out-of-proc SDKs (PowerShell, Python, and Node.js). If a version is explicitly specified, it will be used instead of the value in defaultVersion.

This PR passes the optional orchestration version value through two code paths:

  1. Orchestrations started from the Durable client. The version is passed as a new optional HTTP URL query parameter (see HttpApiHandler).
  2. Suborchestrations started from orchestrations via a context object in language-specific SDKs. The version is appended to the orchestrator function name (see OutOfProcOrchestrationShim) - this is done to avoid changing the interfaces potentially exposed to user code.

Pull request checklist

  • My changes do not require documentation changes
    • Otherwise: Documentation PR is ready to merge and referenced in pending_docs.md
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • I have added all required tests (Unit tests, E2E tests)
  • My changes do not require any extra work to be leveraged by OutOfProc SDKs
  • My changes do not change the version of the WebJobs.Extensions.DurableTask package
    • Otherwise: major or minor version updates are reflected in /src/Worker.Extensions.DurableTask/AssemblyInfo.cs
  • My changes do not add EventIds to our EventSource logs
    • Otherwise: Ensure the EventIds are within the supported range in our existing Windows infrastructure. You may validate this with a deployed app's telemetry. You may also extend the range by completing a PR such as this one.
  • My changes should be added to v2.x branch.
    • Otherwise: This change applies exclusively to WebJobs.Extensions.DurableTask v3.x. It will be retained only in the dev and main branches and will not be merged into the v2.x branch.

@AnatoliB AnatoliB changed the title Use orchestration and sub-orchestration versions explicitly specified via APIs Allow overriding orchestration version when starting orchestrations via APIs Oct 3, 2025
@AnatoliB AnatoliB changed the title Allow overriding orchestration version when starting orchestrations via APIs Allow overriding orchestration version when starting orchestrations via APIs in PowerShell, Python, and Node.js Oct 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant