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. Release prerequisites: #765, #767, #769, #771 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; there are no source-code or production dependency changes in this version PR.

Draft / do not merge until the release prerequisites below are complete. This refreshes the earlier unmerged 2.3.0 preparation for the October OTel minor-release scope. The previous September preparation was closed in favor of 2.2.1; no 2.3.0 tag or release exists.

The version edits are generated with the exact mvn versions:set -DnewVersion=2.3.0 -DgenerateBackupPoms=false command used by Prepare Maven Release. Its unchanged BREAKING-label validation was replayed against live GitHub data: 22 PRs and five BREAKING issue timelines, with no matching release blocker. 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 version metadata).

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: carry invocation-local X-Ray headers in InvocationInfo #765, fix: export synthetic OTel roots and retain READY wait progress #767, test: cover OTel replay and user callback context in Java #769 and fix: finalize invocation hooks on the handler thread #771; 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 version-only diff and release notes
• Current integrated candidate passes required build, compatibility and conformance checks
• Release version PR approved for merge

Testing

Java17 mvn -o -B clean install passed: 2,203 tests reported, 31 existing conditional/cloud skips, zero failures/errors; all nine modules built successfully. The installed released/current core-plugin compatibility matrix passed 16/16 cases. All four published JARs embed version2.3.0; the SDK's filtered version resource also reports2.3.0. XML/diff checks confirm nine POM version-only edits and no production dependency changes. git diff --check passes. These results cover current main plus version metadata; the final combined fixes still require the release gates above.

Unit Tests

Run the existing Java 17 reactor suite with mvn -o -B clean install on the generated version candidate.

Integration Tests

Run existing local integration/example tests in the same reactor. Complete deployed core/OTel conformance on the final integrated candidate after pending fixes merge.

Examples

No new example. Existing example artifacts inherit the reactor version and are built by the validation command.

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 is a preparation draft; pending changes below are not yet included in the candidate built from main 0c8618e42d3b16e9b7115ab943a93253c0fe936c.

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.

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 version PR changes no dependency constraints.

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.
• #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.
• #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.

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 Java fix: carry invocation-local X-Ray headers in InvocationInfo #765, fix: export synthetic OTel roots and retain READY wait progress #767, test: cover OTel replay and user callback context in Java #769, fix: finalize invocation hooks on the handler thread #771 and shared conformance [maven]: Bump software.amazon.awssdk:bom from 2.42.2 to 2.42.3 #131 through their normal reviews; 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 that its only diff is the nine POM version changes, 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.