Skip to content

chore: prepare Python SDK 3.1.0 and Testing 1.5.0 release - #965

Merged
ParidelPooya merged 2 commits into
mainfrom
release/sdk-v3.1.0
Nov 18, 2026
Merged

ParidelPooya merged 2 commits into
mainfrom
release/sdk-v3.1.0

Conversation

@ParidelPooya

@ParidelPooya ParidelPooya commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Issue #, if available

None.

Description of changes

Prepare the next coordinated Python release:

Package PyPI today New Change since the last release
Core SDK 3.0.2 3.1.0 pause_every retry option (#961)
Testing 1.4.1 1.5.0 Local pause support for pause_every (#961)
Extras 0.1.0a0 0.1.0a1 decider and llm (#928, #937), agentcore (#929), AgentCore session types (#959, #960), MicroVM changes (#906, #910, #913, #919)
Compute Worker 0.0.1a0 0.0.1a1 AgentCore worker, rename from microvm-worker (#922)
OpenTelemetry 2.1.0 unchanged No change since sdk-v3.0.2,otel-v2.1.0,testing-v1.4.1
Telemetry Exporter 1.0.0 unchanged No change since telemetry-exporter-v1.0.0

Update the three conformance packages to pin Core 3.1.0, as #917 did for 3.0.2. The OTel conformance pin stays at 2.1.0.

The commits are split:

  1. 32c48e01: Core, Testing and the conformance pins.
  2. 15cdd6ce: Extras and Compute Worker prereleases.

Why Extras and Compute Worker are bumped

  1. pypi-publish.yml builds and publishes every package in its matrix, whatever the tag prefix is (ci(release): publish extras and compute-worker #926).
  2. PyPI has Extras 0.1.0a0 and Compute Worker 0.0.1a0. The repository has 0.1.0 and 0.0.1.
  3. So the next release would publish 0.1.0 and 0.0.1 as stable versions of experimental packages.
  4. So this PR sets the next prereleases, 0.1.0a1 and 0.0.1a1. Drop commit 2 if these packages should go stable instead.

Design

Design note not needed: release metadata only. No runtime code or public API changes.

Assumptions

No new service assumptions.

Decisions not covered by the issue or the design note

  • Core 3.1.0 is a minor version, because pause_every is a new option and nothing breaks.
  • Testing 1.5.0 is a minor version, because it adds pause_durable_execution to the in-memory client. It keeps its Core minimum at 3.0.2. The client imports the pause types only for type checking, so it loads with older Core.
  • Release tag: sdk-v3.1.0,testing-v1.5.0,extras-v0.1.0a1,compute-worker-v0.0.1a1. The tag names the testing version, so ecr-release.yml publishes the testing emulator image 1.5.0.

Validation

  • Built wheels for Core 3.1.0, Testing 1.5.0, Extras 0.1.0a1 and Compute Worker 0.0.1a1 with hatch build.
  • hatch run dev-testing:pytest on package_metadata_test.py, e2e/step_pause_every_test.py and client_test.py: 12 passed.
  • Compared the published Extras and Compute Worker sdists against main to list the changes above.

Checklist

  • No new runtime conditions or branches.

Core 3.1.0 adds the experimental pause_every retry option (#961).
Testing 1.5.0 adds local pause support for it. Update the three
conformance packages to pin Core 3.1.0.
The publish workflow builds and publishes every package in its matrix.
PyPI has Extras 0.1.0a0 and Compute Worker 0.0.1a0. The repository
versions 0.1.0 and 0.0.1 would publish as stable releases. Both packages
are experimental, so this release publishes the next prereleases.

@yaythomas yaythomas left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@ParidelPooya
ParidelPooya marked this pull request as ready for review November 18, 2026 22:56
@ParidelPooya
ParidelPooya deployed to ai-pr-review-runtime November 18, 2026 22:56 — with GitHub Actions Active
@ParidelPooya
ParidelPooya merged commit 4ecdecd into main Nov 18, 2026
43 checks passed
@ParidelPooya
ParidelPooya deleted the release/sdk-v3.1.0 branch November 18, 2026 22:56

This branch was successfully deployed

1 active deployment
ai-pr-review-runtime — 15cdd6ce Deployed Nov 18, 2026 by ParidelPooya via notify / Generate notification summary #455
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.

2 participants