v1.10.0 Release

[Varshitha Bachu (bachuv)]

For the v1.10.0 release, this PR prepares the Durable Task Java SDK build and release pipelines to publish the new large-payload and export-history modules alongside the existing SDK packages.

Changes

• Bump the following packages from  1.9.0  to  1.10.0 :
  durabletask-client 
  durabletask-azure-functions 
  durabletask-azuremanaged 
• Keep the initial versions of the new packages:
  durabletask-azure-blob-payloads:1.10.0
  durabletask-exporthistory:1.10.0-preview.1
• Add ESRP release jobs for  durabletask-azure-blob-payloads  and  durabletask-exporthistory .
• Release  durabletask-client  before packages that depend on it.
• Include all five publishable package outputs in build validation artifacts.
• Upload large-payload and export-history integration test reports.
• Update the v1.10.0 changelog to cover all features merged since v1.9.0.
• Add documentation for the Azure Blob large-payload module.
• Update the root README with all Maven Central packages.

Validation

• Ran  gradlew clean build -PskipSigning .
• Confirmed all five packages produce their expected binary, source, and Javadoc JARs.
• Validated the modified GitHub Actions and Azure DevOps YAML files.

Pull request checklist

• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes are added to the CHANGELOG.md
• I have added all required tests (Unit tests, E2E tests)

[Copilot]

🟡 Changes recommended

Three review findings remain unresolved, including the payload package version mismatch.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

Prepares the Durable Task Java SDK v1.10.0 release, including package versioning, release automation, validation artifacts, documentation, and changelog updates.

Changes:

• Updates package versions and release sequencing.
• Adds publishing jobs and CI artifacts for new modules.
• Updates Maven documentation and release notes.

File summaries

File	Summary
README.md	Documents new modules and Maven packages.
exporthistory/README.md	Updates preview package documentation.
exporthistory/build.gradle	Sets the export-history preview version.
eng/templates/build.yml	Updates build task metadata.
eng/ci/release.yml	Adds and sequences release jobs.
client/build.gradle	Bumps the client version.
CHANGELOG.md	Adds v1.10.0 release notes. nit (2 votes): Uses getParent() instead of the actual getParentInstance() API.
azuremanaged/build.gradle	Bumps the Azure Managed package version.
azurefunctions/build.gradle	Bumps the Azure Functions package version.
azure-blob-payloads/README.md	Documents the large-payload package. nit (3 votes): Uses 1.10.0 instead of the intended 1.1.0.
azure-blob-payloads/build.gradle	Configures the payload package version. moderate (3 votes): Sets 1.10.0 instead of the requested 1.1.0.
azdevops-pipeline/build-release-artifacts.yml	Includes publishable package artifacts.
.github/workflows/build-validation.yml	Uploads new reports and package artifacts.

Review details

• Files reviewed: 13/13 changed files
• Comments generated: 3
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

🟢 Approval recommended

Release versions and pipeline sequencing are consistent, with only minor documentation wording discrepancies remaining.

Review details

Suppressed comments (2)

Previously missed (2) — in code that hasn't changed since the last review.

README.md:45

• The interceptor externalizes payloads whose size is equal to the threshold as well (size < threshold is the inline case), so “exceed” documents the boundary incorrectly. Say “meet or exceed” to match the API behavior.
  azure-blob-payloads/README.md:3
• This leaves payloads exactly equal to the configured threshold unaccounted for, although LargePayloadInterceptor externalizes them. Describe the second case as “at or above the threshold” so the installation guide matches the actual boundary.

• Files reviewed: 13/13 changed files
• Comments generated: 1
• Review effort level: Balanced

[wangbill (YunchuWang)]

Reviewed commit 9ab4bc8. No blocking findings in the release-preparation changes. The five package versions, Maven publication and staging paths, and client-first release dependencies are consistent. Export History remains explicitly versioned as a preview, and the changelog and payload documentation align with the release scope and implementation.

[wangbill (YunchuWang)]

Non-blocking: the Packages artifact is missing the sources and Javadoc JARs for azurefunctions and azuremanaged.

I inspected the artifact from this PR's CI run: it contains 11 JARs rather than the expected 15 (binary, sources, and Javadoc for each of the five modules). The earlier ./gradlew clean test deletes the initially assembled outputs, and the later integration-test builds recreate the sources/Javadoc JARs only for client, azure-blob-payloads, and exporthistory.

Could we run ./gradlew assemble immediately before this upload so all five modules have complete outputs? All binary JARs are present, and the separate official release pipeline assembles and publishes independently, so this is a CI artifact completeness issue rather than a runtime or production-release blocker.