[hln33]

Issue #, if available

Release bump for #871, fixed by #872 (merged in 73b9d68).

Description of changes

Bump aws-durable-execution-sdk-python from 3.0.0 to 3.0.1 for a patch release
that ships the oversized first-operation batching fix (#872). No runtime code
changes.

Six lines change, in two commits:

1. chore: release SDK 3.0.1
   • packages/aws-durable-execution-sdk-python/src/aws_durable_execution_sdk_python/__about__.py: 3.0.0 → 3.0.1.
   • .github/tests/otel_lifecycle_compatibility_test.py:45 and
     .github/tests/otel_legacy_registration_rejection_test.py:33: these assert
     the installed core version equals the wheel built from this checkout
     (install_otel_test_wheels.py), so they move to 3.0.1.
2. chore: bump conformance SDK pins to 3.0.1
   • packages/aws-durable-execution-sdk-python-conformance-tests{,-otel,-telemetry}/pyproject.toml:
     aws-durable-execution-sdk-python==3.0.0 → ==3.0.1. The hatch test
     environment installs every packages/* member from the checkout. An exact
     ==3.0.0 pin cannot resolve against a local 3.0.1. Same pattern as the
     2.0.1 release (2313fcb).

After merge: create a GitHub Release with tag sdk-v3.0.1; pypi-publish.yml
publishes on the release: published event (see RELEASING.md).

Design

• Design note (rule 3): not needed, version bump only.
• Simpler options considered (rule 2): n/a, no logic added.
• Root cause (rule 5): n/a, not a bug fix.
• Net change in source lines and in public API members: 0 source lines, 0 API members (__version__ value only).

Assumptions

• uv.lock is not tracked on main, so no lockfile update is needed. Verified with git ls-tree origin/main uv.lock.
• PyPI rejects re-upload of the unchanged otel/testing/telemetry-exporter packages; RELEASING.md documents this as expected (fail-fast: false).

Decisions not covered by the issue or the design note

• docs/migration-2.x-to-3.0.md keeps its 3.0.0 references: it documents the 2.x → 3.0 migration target, not the current release.

Checklist

• Every new branch has a test that fails without it (rule 4): n/a, no branches added.
• For a bug fix: the first commit adds a test that fails on the current code (rule 5): n/a.
• Every edited test expectation is listed in the description, with the reason (rule 5): the two .github/tests version assertions, listed above.

Local verification: hatch run test:all on the conformance packages (83 passed);
hatch build core + otel; hatch run test-wheel-otel:test (805 + 12 passed);
hatch run test-wheel-otel-legacy:test (4 passed).

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

Codex AI review

No actionable findings or violations of CONTRIBUTING.md rules 1–9 identified. The version bump, dependency pins, and wheel-test assertions are consistent. Residual risk: builds and tests were not executed during this read-only review.

Reviewed commit 34c672dc511516d2d19cdc63ecfa02d9b92314c2. Workflow run

[yaythomas]

Besides __about__.py, this release had to edit three conformance pyproject.toml files and two .github/tests files. Those files hard-code the core version. #877: Let a patch or minor release edit only __about__.py proposes ranges and major-version checks instead.