[zhongkechen]

Superseded: this manually created PR is closed so the documented Prepare Maven Release workflow can prepare version 3.0.0 and create the replacement PR. The original commit is preserved on release/v3.0.0-manual-20261021. No tag, GitHub Release or Maven publication was created.

Set the Java reactor from 3.0.0-SNAPSHOT to 3.0.0, and document the matching Maven coordinates in the 2.x-to-3.x migration guide. These version changes were prepared manually; this PR was not created by the Prepare Maven Release workflow.

Issue Link, if available

Prepares the major version boundary for the factory-only plugin API merged in #782.

Description

Artifact	Release version
aws-durable-execution-sdk-java	3.0.0
aws-durable-execution-sdk-java-testing	3.0.0
aws-durable-execution-sdk-java-plugin-otel	3.0.0
aws-durable-execution-sdk-java-plugin-telemetry-exporter (preview)	3.0.0

The 10 reactor POMs share that version. The standalone OTel conformance project remains 1.0.0 and resolves the candidate SDK through durable.sdk.version. External dependency versions and runtime code are unchanged.

The release contains main's merged plugin factories, invocation-local X-Ray snapshot and handler-owned plugin lifecycle. Plugin registrations and provider/layer JARs must be rebuilt for 3.x; the migration guide covers direct factories, ServiceLoader providers, exclusive-view metadata and InvocationInfo record patterns. The Telemetry Exporter retains its preview stability contract. The unmerged deadline and executor follow-ups in #733/#735 are outside this snapshot.

Merging this preparation PR does not publish packages. Per RELEASE.md, publication starts later when a maintainer manually publishes GitHub release v3.0.0; Sonatype Central Portal then has its own manual publish step.

Release notes

The source delta since v2.3.0 is the development-version bump plus #782. Upgrade the core, testing library and plugin/provider JARs together. The 2.3.0 checkpoint/replay and chained-invoke propagation fixes are retained.

Demo/Screenshots

Not applicable; release metadata and migration documentation.

Checklist

• I have filled out every section of the PR template
• Local release packaging and compatibility validation completed

Testing

• Java 17: all 10 reactor modules package and install with mvn clean spotless:check install -DskipTests in an isolated Maven repository. The 4 binary artifacts plus their source/Javadoc JARs have recorded checksums; binary Maven metadata and the SDK version resource are 3.0.0.
• Java 25: 78 existing factory/provider, legacy constructor/record-pattern and X-Ray carrier tests pass across 7 test classes.
• Java 17: the installed core/testing/OTel release artifacts pass all 4 API compatibility cases (both views with OTel API 1.49.0 and 1.66.0).
• The standalone OTel conformance project packages successfully with durable.sdk.version=3.0.0; its shaded SDK metadata is verified as 3.0.0 while its own project version stays 1.0.0.

Unit Tests

Existing relevant controls were run. No runtime code changed, so unrelated unit suites were not repeated for this version-only preparation.

Integration Tests

The installed-artifact matrix verifies provider discovery, per-invocation factory creation, class origins and completed-step replay using the release JARs. These are local checks.

Examples

Examples and conformance modules are compiled against the 3.0.0 reactor during local packaging. Cloud deployment and package publication are separate later actions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

Codex AI review

No actionable findings. The reactor versions and migration coordinates consistently use 3.0.0. Residual test risk: Maven packaging and tests were not executed during this read-only review.

Reviewed commit fb7c9ada75287fad1b5db63d2eac6b4a4c80fb34. Workflow run

[zhongkechen]

Superseded by #813, which was created by the documented Prepare Maven Release workflow: https://github.com/aws/aws-durable-execution-sdk-java/actions/runs/39654054546.

The workflow validated the previous tag v2.3.0, identified BREAKING #782, checked the major bump to3.0.0, updated the POMs and opened the replacement PR. This earlier PR was created manually and is closed. Its commit is preserved on release/v3.0.0-manual-20261021. No release tag or package publication was performed.