Repository navigation
chore: prepare Python minor releases - #764
Draft
zhongkechen wants to merge 1 commit into
Draft
zhongkechen wants to merge 1 commit into
zhongkechen wants to merge 1 commit into
Conversation
This branch has not been 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.
Prepare the Python nonbreaking OTel minor release by bumping the testing package from 1.2.1 to 1.3.0. Scoped PR #758 fixes callback update delivery and empty-error history round trips in testing package runtime code, so those fixes need a new testing artifact. This PR contains only the version bump; unmerged fixes are release prerequisites and are not cherry-picked here.
The existing Lambda layer SDK pin is already 2.1.0. Production dependency floors remain unchanged. Following
RELEASING.md, the intended combined tag issdk-v2.1.0,otel-v1.1.0,testing-v1.3.0, created only after the release changes are merged and all publication gates pass.Draft release notes
aws-durable-execution-sdk-python v2.1.0
Already merged: reject competing OTel views before discovered factories run, with explicit opt-in validation and cleanup (#753). Configurations enabling both views must select one before upgrading the coordinated SDK 2.1/OTel 1.1 pair.
Pending: handler-worker OTel context propagation (#756) and callback terminal notification delivery/replay corrections (#758).
aws-durable-execution-sdk-python-otel v1.1.0
Already merged: correct operation/retry status mappings (#752), enforce one view with SDK 2.1 and recover log enrichment after rejected-instance reuse (#753).
Pending: first-invocation sampled fallback-root export (#754), handler context propagation (#756), and expanded replay/status/user-callback conformance checks (#758 and aws/aws-durable-execution-conformance-tests#131).
aws-durable-execution-sdk-python-testing v1.3.0
Pending scoped fixes: report callback success/failure/timeout through
UpdatedOperationIds, consume checkpoint-delivered updates while retaining newer changes, and preserve empty-error history round trips (#758). Main also contains virtual-clock, per-execution worker and local chained-invoke improvements since the published 1.2.1 artifact.Release gates
f225d880, fix: run invocation lifecycle on handler worker #756's actual OTel metadata requires core>=2.1.0and removes the optionalhandler_contextdesign; test: cover OTel replay and status mappings #758 ata6c8c904still has that design and core>=2.0.0. This preparation preserves main's dependency floors and does not claim old-core compatibility for the unmerged redesign.ef683592currently fails plugin conformance case 10-18, with missing middle-resume WAIT hook records despite backend success; the root cause is unconfirmed.RELEASING.md.Validation
On main
ef683592plus this one-line version change, using the publisher's Hatch 1.16.5 and Python 3.13.15:git diff --checkpass.These checks validate release preparation, not the unmerged fixes or final release commit. No release, tag, package, layer or merge is created by this PR.