Skip to main content
Support status and end-of-life follow the upstream Kotlin, JDK, framework, and Gradle schedules; the pinned lines live in sdk/jvm/compatibility-matrix.toml in the release.

​
Security posture

The Java SDK documents the shared baseline in full:
  • Proxy, TLS, and mTLS via HttpTransportOptions (explicit proxy with credentials, a borrowed SSLContext for mutual TLS, allowlisted TLS 1.2/1.3 and ciphers, redirects disabled) — see Configuration.
  • Redaction. The SDK’s own diagnostics, observer events, telemetry, exception messages, and model toString() are credential- and payload-free. The SDK does not scrub PII you place inside an event payload — that data is the event you publish and is sent to Repost as-is.
  • Native image. One framework-neutral-core GraalVM native smoke (25.0.3) is validated; the framework modules are not native-certified.
  • FIPS. This release is not FIPS-certified. Using it in a FIPS deployment requires your own certified provider and JDK.

​
Continue

Java SDK

The same runtime with builders, CompletionStage, and the Maven plugin.

SDKs

The behavior every generated client shares, in every language.

Schema workflow

Version the schema with migrations and deploy it to your environment.