chore: release version 2.3.0

[github-actions]

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

Issue Link, if available

Java OpenTelemetry minor-release preparation. Already merged: #780, #766, #767 and #771. Remaining release prerequisites: #765, #769 and aws/aws-durable-execution-conformance-tests#131.

Description

Prepare 2.3.0 for the SDK, testing library, OpenTelemetry plugin and Workflow Insight plugin. All nine reactor POMs move from 2.2.2-SNAPSHOT to 2.3.0. The compatibility sweep also removes obsolete 2.2.2 lifecycle-version wording from the OTel README, core Javadoc and the configuration diagnostic; the capability check itself is unchanged. This head includes the formatting-only repair from #794. Production dependency updates are inherited from main.

Release preparation / do not merge until the release prerequisites below are complete. This PR prepares the October OTel minor-release scope; publishing remains a separate action.

The version edits are generated with the exact mvn versions:set -DnewVersion=2.3.0 -DgenerateBackupPoms=false command used by Prepare Maven Release. The existing BREAKING-label rules remain unchanged and must be rechecked on the final integrated release candidate. The existing release/v2.3.0 branch is retained; native workflow dispatch cannot reuse that branch. This preparation does not create a tag or publish a release/package.

The breaking factory migration #782 and service-model-dependent #768 are excluded. #721 was exactly reverted by #781, so its presence in history does not mean the factory API is included.

Demo/Screenshots

Not applicable (release metadata and compatibility guidance).

Checklist

• Release procedure and current release/tag/PR state inspected
• Repository BREAKING-label gate evaluated without changing its rules
• Version changes generated by the documented Maven command
• Merge fix: export synthetic OpenTelemetry roots #767 and fix: finalize invocation hooks on the handler thread #771
• Merge fix: carry invocation-local X-Ray headers in InvocationInfo #765 and fix: preserve OTel failure and replay semantics #769; merge shared conformance [maven]: Bump software.amazon.awssdk:bom from 2.42.2 to 2.42.3 #131
• Refresh from final main and recheck the release metadata, compatibility guidance and release notes
• Current integrated candidate passes required build, compatibility and conformance checks
• Release version PR approved for merge

Testing

Current head 4658ea03423adf6a004da5f9b8e801ba2350acb1 incorporates main 67bad28cd9ef1b0808bed193f8a15be75ce457ed. The upstream change skips operation-change metadata conversion when no plugins are registered, while preserving checkpoint storage/completion and registered-plugin notifications. Only ExecutionManager.java and its existing test file changed in this base integration; the PR's implementation, public API declarations, dependencies, workflows and release requirements are retained.

Java 17 validation on this exact source built all nine reactor modules: 2,965 tests passed, 31 conditional/cloud tests skipped, and zero failures/errors. All 49 ExecutionManagerTest cases, full Spotless checks and the 16/16 installed core/plugin API compatibility cases passed. New-head CI, including the supported Java-version matrix and deployed conformance, is tracked separately. The nine reactor versions and four release JAR versions were verified as 2.3.0. Final integrated release qualification remains pending until the listed prerequisites are merged.

Draft release notes

Release v2.3.0 — preparation draft

This minor release targets the Java OpenTelemetry fixes in work items 3–10. The SDK, testing library, OpenTelemetry plugin, and Workflow Insight plugin share version 2.3.0. This preparation includes current main 67bad28c, including #767, #771 and the no-plugin checkpoint conversion optimization. The remaining planned fixes below are not yet included.

Already merged

• #780: isolate incompatible OpenTelemetry API linkage failures so optional instrumentation does not fail a healthy durable handler. Preserve fatal JVM error propagation and existing 2.x plugin APIs.
• #766: reject configuring both durable OpenTelemetry views together with a clear configuration error.
• #771: propagate span context through handler execution and finalize invocation hooks on the handler thread.
• #767: export synthetic execution roots and preserve READY wait progress.

Other changes already on main since v2.2.1 include filesystem serialization for durable operation payloads (#755), per-operation step-result deserialization in local tests (#759), correct thread accounting when DurableFuture.anyOf blocks (#730), callback failures without an error payload (#774), and one pending Workflow Insight export slot per execution (#716). Existing dependency and CI maintenance is inherited from main; this preparation adds no production dependency constraints beyond those inherited from main.

Planned fixes — must merge before release

• #765: capture invocation-local X-Ray headers in InvocationInfo for both OpenTelemetry views, with legacy carrier fallback where the runtime accessor is unavailable.
• #769 with shared conformance #131: cover user callback context, status and replay behavior.

The pending implementation PRs also include validated sampling and continuation corrections. Final notes must be refreshed from their actual merged changes. CI success on each pending branch is not a substitute for validating the final combined release commit.

Compatibility

The 2.x plugin registration API remains. The factory migration in #782 is reserved for a later major release. The earlier #721 migration was fully reverted by #781. Backend/service-model-dependent chained-invoke propagation (#768) is excluded. Invocation-local header extraction alone does not resolve the separate shared-plugin concurrency issue on Lambda Managed Instances. The already-admitted-worker and large-result acknowledgment limitations remain tracked in #787 and are not repaired by this version preparation.

Accepted InvocationInfo record-shape exception in #765: existing constructors and already-compiled consumers remain compatible. Recompiling an existing seven-component record pattern requires an eighth binding. Reflection sees the additional component, and record equality/hash calculation includes the new header. This is not unconditional source or record-shape compatibility. Checkpoint formats and operation identity are unchanged.

Release gates

1. Merge the remaining Java fix: carry invocation-local X-Ray headers in InvocationInfo #765, fix: preserve OTel failure and replay semantics #769 and shared conformance [maven]: Bump software.amazon.awssdk:bom from 2.42.2 to 2.42.3 #131 prerequisites through their normal reviews; fix: export synthetic OpenTelemetry roots #767 and fix: finalize invocation hooks on the handler thread #771 are already included. Keep refactor(plugin)!: create one plugin instance per invocation #782 and feat(plugin): propagate chained invoke trace context in START checkpoints #768 out of this minor release.
2. Refresh this version PR from main, verify the nine POM version changes and reviewed capability-guidance corrections, confirm inherited formatting maintenance is no longer a separate release diff, and update these notes to distinguish the final included changes accurately.
3. Repeat the repository's BREAKING-label validation against the final main history. Recheck the accepted fix: carry invocation-local X-Ray headers in InvocationInfo #765 compatibility exception and released/current core-plugin checks.
4. Complete required CI and OTel/core conformance checks on the final integrated release candidate, and approve/merge the version PR.
5. Only after separate release authorization, create v2.3.0 at the version PR's merge commit and publish the GitHub release. That action triggers Maven staging and release notification. Sonatype Central publication remains manual (autoPublish=false). No tag, release, package or publish workflow has been created or run as part of this preparation.
6. After publication, follow RELEASE.md for artifact verification, the generated 2.3.1-SNAPSHOT PR, and shared documentation updates.

[zhongkechen]

Why is this a minor release instead of 2.2.1?

[hln33]

Why is this a minor release instead of 2.2.1?

It is a minor release because it includes the workflow insight feature which was added in #661.

[hln33]

Confirmed with team that we are not going to include the workflow insight plugin in the next release. Will close this PR and open a new release this is a patch version bump instead.

[hln33]

Should do a sweep through to see if there are any other inconsistencies

[zhongkechen]

Completed the sweep and updated this PR in 685db0ef. All nine reactor POMs, parent references and internal module dependencies agree on 2.3.0. I inspected the four freshly built release JARs: their Maven metadata is 2.3.0, the SDK version resource is 2.3.0, and the OTel diagnostic contains the corrected wording.

The sweep found stale 2.2.2 lifecycle-version references in the OTel README, configuration diagnostic and core Javadoc. Those now describe the actual same-thread capability, preserving the capability check and the instruction to upgrade core and plugin together. Intentional references to released 2.2.1 and old compatibility fixtures remain.

The latest external main merge is preserved, and the formatting-only repair from #794 is included. A fresh Java 17 spotless:check package -DskipTests passed; tests were intentionally skipped for this packaging check, and new-head CI remains separate. The description now reflects the guidance changes and retains the remaining release prerequisites and final validation gates.

[zhongkechen]

Fixed in 685db0ef. Removed the obsolete 2.2.2 release claim from the README, configuration diagnostic and core Javadoc. The check still requires DurableExecutor.supportsSameThreadInvocationHooks(), and the documentation still requires upgrading core and plugin together. The built 2.3.0 OTel JAR contains the corrected diagnostic; intentionally historical 2.2.1 references are retained.

[github-actions]

Codex AI review

No actionable findings. The nine reactor versions align at 2.3.0, and the prior compatibility-guidance issue is resolved. Residual test risk: builds and compatibility tests were not executed during this read-only review.

Reviewed commit 4658ea03423adf6a004da5f9b8e801ba2350acb1. Workflow run