[github-actions]

Sets the Maven project version to 3.0.0. After this PR is approved and merged, manually create and publish GitHub release v3.0.0.

[zhongkechen]

The documented Prepare Maven Release workflow created this PR. It validated v2.3.0 as the previous tag, identified BREAKING #782, and verified the major increment to3.0.0. This replaces manually created #812; the generated ten-POM change is retained exactly.

Supplemental local validation used identical POM, runtime and test inputs: Java17 packaging and Spotless for all10 reactor modules;78 Java25 factory/provider/record/carrier tests;4 installed OTel API compatibility cases; and standalone OTel conformance packaging against3.0.0. Binary Maven metadata and the SDK version resource were verified as3.0.0. No release tag or package publication was performed.

Draft notes for the later GitHub Release

Java SDK 3.0.0 release notes

This major release introduces a factory-only plugin API. The SDK creates a separate plugin instance for each Lambda invocation, preventing concurrent Lambda Managed Instances invocations from sharing mutable instrumentation state. Reusable exporters and provider resources retain their execution-environment lifetime.

Upgrade

Use 3.0.0 for the core SDK, testing library, OpenTelemetry plugin and preview Durable Execution Telemetry Exporter. These Maven artifacts share the repository version.

Recompile applications that register plugins and rebuild/redeploy every plugin provider or Lambda layer against 3.x. Replace instance registration with a DurableExecutionPluginFactory, such as withPlugins(info -> new MyPlugin(info)). Bundled OTel registrations use InvocationOtelPlugin.factory(...) or ExecutionOtelPlugin.factory(...). Move shared resources outside the per-invocation factory.

The provider method is now createPlugin(InvocationInfo). The old zero-argument provider method, instance-based withPlugins, getPluginRunner, and API-version/type accessors are removed; no 2.x compatibility adapter is provided. Selected stale ServiceLoader providers fail configuration with a diagnostic identifying the provider JAR. Read the 2.x-to-3.x migration guide before upgrading custom providers.

Included changes

• Pass the same invocation metadata snapshot to the factory and Start hook, including the invocation-local runtime X-Ray header captured before worker dispatch. Preserve authoritative empty headers and custom extractor behavior.
• Validate mutually exclusive OTel views using factory metadata before construction, and retain effective factory registrations when configuration is copied.
• Preserve handler-owned lifecycle ordering: Start, user work and scope cleanup, operation/checkpoint drain, output preparation, then End in reverse registration order. JVM fatal failures retain their invocation failure semantics and actual worker visibility.
• Keep the 2.3.0 checkpoint, replay, serialization and outbound chained-invoke propagation fixes. This release does not change durable checkpoint formats or operation identities.

InvocationInfo includes the xRayTraceId record component. Existing constructor overloads/accessors are retained; newly compiled record deconstruction patterns must account for the added component. See the migration guide for the binary/source distinction.

The Telemetry Exporter remains a preview API. The separate invocation-deadline and configurable-executor work in #733/#735 is not included in this release snapshot.

Full source comparison: v2.3.0...953c377