Repository navigation
Release durabletask 1.13.0 and Azure Functions 2.0.0rc4 - #321
Merged
Bernd Verst (berndverst) merged 2 commits intoNov 2, 2026
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Bernd Verst (berndverst)
previously approved these changes
Nov 2, 2026
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The replay-safety guidance omits bare-set and nested-container limitations, and sorting alone can remain nondeterministic for frozenset values.
3 open issues
What changed in this PR
Prepares a coordinated release of the core SDK and both providers, aligning dependency minimums and documenting upgrade considerations.
Changes:
- Bumps core and Azure Managed to
1.13.0, and Azure Functions to2.0.0rc4. - Raises provider core dependencies to
1.13.0, including applicable extras. - Adds release changelog sections and documents query filters, set conversion, immutable entity IDs, and replay considerations.
| File | Description |
|---|---|
README.md |
Documents query filters, set conversion, and immutable entity IDs. |
pyproject.toml |
Sets core version to 1.13.0. |
durabletask-azuremanaged/pyproject.toml |
Updates provider version and core dependency minimums. |
durabletask-azuremanaged/CHANGELOG.md |
Adds the 1.13.0 section and inherited feature coverage. |
CHANGELOG.md |
Adds the core 1.13.0 section and clarifies feature descriptions. |
azure-functions-durable/README.md |
Documents inherited query filtering and entity-ID behavior. |
azure-functions-durable/pyproject.toml |
Sets 2.0.0rc4 and raises the core dependency minimum. |
azure-functions-durable/CHANGELOG.md |
Adds the prerelease section and updates upgrade references. |
Review effort: Balanced
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Bernd Verst (berndverst)
approved these changes
Nov 2, 2026
Bernd Verst (berndverst)
deleted the
andystaples-release-1-13-0-and-rc4
branch
November 2, 2026 20:31
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
Prepare the coordinated release of all three packages:
durabletask1.13.0v1.13.0durabletask.azuremanaged1.13.0azuremanaged-v1.13.0azure-functions-durable2.0.0rc4azurefunctions-v2.0.0rc4Both providers now require
durabletask>=1.13.0, including the Azure Managed blob-payload extra. Each changelog retains an emptyUnreleasedsection above its release section.Release coverage
The release includes changes since
v1.12.0,azuremanaged-v1.12.0, andazurefunctions-v2.0.0rc3:The provider changelogs now include inherited task-hub filtering and entity-ID changes; Azure Managed also documents the new set-conversion options. The core changelog now explicitly introduces set support instead of only describing its optimization. Root and Functions READMEs document the applicable query and entity-ID behavior, and the root README explains set conversion and replay safety. Functions retains its separate shared codec. Internal GitHub Actions updates are excluded from release notes.
Warning
Python 3.10 is no longer supported by core or Azure Managed; Functions still requires Python 3.13+. Non-retriable failure handling and the callback aggregate exception change can affect replay of existing histories. Drain or isolate affected instances before upgrading. Set reconstruction remains opt-in, and entity IDs now reject attribute assignment and deletion.
Publishing coordination
After merge, publish
durabletask1.13.0first and confirm availability on PyPI before publishing either provider. Create the package-specific tags above on the merged release commit. Mark the Azure Functions release as a prerelease. This PR does not create tags or GitHub releases.Prepared release bodies
v1.13.0
What's Changed
Review the release changelog before upgrading: retry and aggregate-exception changes can affect replay, and orchestrator finalizers now run at each dispatch boundary. Set reconstruction remains disabled by default.
External Links
Contributors
andystaples, Bernd Verst (@berndverst), Hardik K (@hardikkaurani), Tamir Dresher (@tamirdresher)
azuremanaged-v1.13.0
What's Changed
durabletask>=1.13.0, including the blob-payload extra. Client and worker context managers preserve subclass types in type checkers.Review the release changelog and its core upgrade guidance before upgrading. Retry and aggregate-exception changes can affect existing histories; orchestrator finalizers now run at each dispatch boundary. Set reconstruction remains disabled by default.
External Links
Contributors
andystaples, Bernd Verst (@berndverst), Hardik K (@hardikkaurani), Tamir Dresher (@tamirdresher)
azurefunctions-v2.0.0rc4
What's Changed
DFApp.configure_serialization(ensure_ascii=False)for opt-in Unicode JSON across durable payload boundaries.EntityId, are immutable and hashable.durabletask>=1.13.0andazure-functions>=2.4.0b1. Python 3.13+ remains required.This is a prerelease. Review the release changelog and its core upgrade guidance before upgrading. Retry and aggregate-exception changes can affect existing histories; orchestrator finalizers now run at each dispatch boundary. Unicode encoding is opt-in and must be configured consistently at startup.
External Links
Contributors
andystaples, Bernd Verst (@berndverst), Hardik K (@hardikkaurani), Tamir Dresher (@tamirdresher)