Repository navigation
chore: prepare testing 1.4.0 and exporter 0.0.2 for the 3.0 release - #841
Merged
Merged
Conversation
This comment has been minimized.
This comment has been minimized.
yaythomas
force-pushed
the
chore/release-mechanics-3.0
branch
from
October 25, 2026 20:35
49e1be0 to
6905407
Compare
This comment has been minimized.
This comment has been minimized.
yaythomas
added a commit
that referenced
this pull request
Oct 25, 2026
The guide named one breaking change. Main now has three: plugin factories (#737), subtypes as strings (#837), and None kept in batch results (#765). Add a section for each of the two new ones, with the searches that find affected code. The dependency table moves testing to 1.4.0 and adds the telemetry exporter at 0.0.2, the versions #841 publishes. The lifecycle section states where each hook runs after plugin hooks moved off the checkpoint thread.
yaythomas
added a commit
that referenced
this pull request
Oct 25, 2026
The guide named one breaking change. Main now has three: plugin factories (#737), subtypes as strings (#837), and None kept in batch results (#765). Add a section for each of the two new ones, with the searches that find affected code. The dependency table moves testing to 1.4.0 and adds the telemetry exporter at 0.0.2, the versions #841 publishes. The lifecycle section states where each hook runs after plugin hooks moved off the checkpoint thread.
Testing moves to 1.4.0: it now requires core 3.0.0 and reads the operation subtype as a string. The telemetry exporter moves to 0.0.2: the published 0.0.1 uses the core 2 plugin contract. The telemetry conformance package pins the exporter exactly, so its pin moves with it.
yaythomas
force-pushed
the
chore/release-mechanics-3.0
branch
from
October 25, 2026 21:31
6905407 to
4fa6446
Compare
Contributor
Codex AI reviewNo actionable findings. The version bumps and telemetry conformance dependency pin are consistent. Residual test risk: builds, installation, and tests were not executed under the read-only review constraints. Reviewed commit |
ParidelPooya
approved these changes
Oct 25, 2026
yaythomas
added a commit
that referenced
this pull request
Oct 26, 2026
The guide named one breaking change. Main now has three: plugin factories (#737), subtypes as strings (#837), and None kept in batch results (#765). Add a section for each of the two new ones, with the searches that find affected code. The dependency table moves testing to 1.4.0 and adds the telemetry exporter at 0.0.2, the versions #841 publishes. The lifecycle section states where each hook runs after plugin hooks moved off the checkpoint thread.
yaythomas
added a commit
that referenced
this pull request
Oct 26, 2026
The guide named one breaking change. Main now has three: plugin factories (#737), subtypes as strings (#837), and None kept in batch results (#765). Add a section for each of the two new ones, with the searches that find affected code. The dependency table moves testing to 1.4.0 and adds the telemetry exporter at 0.0.2, the versions #841 publishes. The lifecycle section states where each hook runs after plugin hooks moved off the checkpoint thread.
This branch was successfully deployed
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.
Issue #, if available
Release preparation for core 3.0.
Description of changes
An earlier revision also set
skip-existing: trueon the PyPI publish step. Removed: with these bumps every package in the release matrix is a new version, so the flag changes nothing for this release. Hatch builds are reproducible and PyPI accepts a byte-identical re-upload with 200, so the only case the flag would change is a package whose code changed without a version bump, where the current 400 is a useful signal. Idempotent publishing stays with #716.Design
See Rules for every change.
Assumptions
None about the service, Lambda, the runtime or another library.
Decisions not covered by the issue or the design note
>=3.0.0and theOperation.sub_typetype change go in its release notes.Checklist
Validation
hatch buildproducesaws_durable_execution_sdk_python_testing-1.4.0andaws_durable_execution_sdk_python_telemetry_exporter-0.0.2wheels and sdists.sdk-v3.0.0,otel-v2.0.0,testing-v1.4.0,telemetry-exporter-v0.0.2parses to testing1.4.0inparse_testing_version.pyand to SDK3.0.0inresolve_layer_sdk_version.py.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.