Skip to content

Release v2.0.0

Latest

Choose a tag to compare

@github-actions github-actions released this 24 Jun 21:02
· 3 commits to main since this release

What's Changed

Breaking Changes

See the migration guide for upgrade instructions from 1.x to 2.x.

  • StepConfig.semantics(...) has been removed. Use semanticsPerRetry(...) instead, and add retryStrategy(RetryStrategies.Presets.NO_RETRY) when preserving old AT_MOST_ONCE_PER_RETRY behavior by @zhongkechen in #476
  • Logger MDC fields were renamed to align with the other Durable Execution SDKs: durableExecutionArn -> executionArn, contextId -> operationId, and contextName -> operationName by @zhongkechen in #465
  • Replay-sensitive logging and replay APIs were updated to use per-context replay state. isReplaying() now belongs on DurableContext, and StepContext no longer exposes replay state by @zhongkechen in #481
  • Invalid context usage now throws IllegalStateException instead of IllegalDurableOperationException by @zhongkechen in #477
  • Serialized operation results and exceptions are now deserialized before checkpointing by default, so custom SerDes implementations must support SDK-managed round trips by @zhongkechen in #480

New Preview Feature: OpenTelemetry Plugin

See the OpenTelemetry plugin documentation.

  • Added the plugin-otel preview artifact for OpenTelemetry instrumentation, with support for X-Ray context extraction and trace ID priority by @ayushiahjolia in #464
  • Prepared plugin-otel for independent publishing to Maven Central by @ayushiahjolia in #494
  • Renamed the OpenTelemetry plugin artifact to plugin-otel by @ayushiahjolia in #496
  • Renamed OpenTelemetryDurablePlugin to OtelPlugin by @ayushiahjolia in #497
  • Added X-Ray end-to-end integration tests for span validation by @ayushiahjolia in #444
  • Fixed span emission for cross-invocation operations and replay by @ayushiahjolia in #482

Features

Fixes and Improvements

New Contributors

Full Changelog: v1.2.1...v2.0.0