Repository navigation
v3.34.0
A platform-modernization release: Conductor moves to Spring Boot 4.1, Jackson 3, Jakarta EE 11, the Java 25 runtime, and Elasticsearch 8 as the default backend. This is a required-migration release -- plan an upgrade rather than a drop-in bump, especially if you build against the Maven artifacts, run a self-managed Elasticsearch 7 cluster, or pin the JVM.
Who needs to do what
- Running the Docker image? Boot it as before -- the runtime is self-contained and the Java 25 JRE ships inside the image. The one operational change is Elasticsearch: the image now ships ES8 by default (see below).
- Running the server JAR on your own JVM? The baseline moves to Java 25 -- the server ships Java 25 bytecode and must run on a Java 25 runtime.
- Building against the Maven artifacts (
org.conductoross:conductor-common/-core, custom system tasks, custom persistence, SDK/worker code)? This is a breaking recompile -- Jackson moved packages and Spring Boot/Jakarta are new majors. See the migration guide (#1754). - Self-managing an Elasticsearch 7 cluster? The ES8 client cannot talk to a 7.17 server -- upgrade your cluster to 8.x, or stay on the 3.33 line, which remains the last series that defaults to ES7.
Artifact availability
- Docker image (
conductoross/conductor:3.34.0, also:latest) and the server JAR are available now. - Maven Central libraries (
org.conductoross:conductor-common/-core/ etc.) are being published on a short delay and will appear on Maven Central in early December. If you build against the 3.34.0 Maven artifacts, expect them shortly -- the Docker image and JAR already carry this release. This note will be updated once the artifacts are live.
Platform
- Spring Boot 4.1 / Spring Framework 7 / Spring Security 7 / Jakarta EE 11 / Tomcat 11 (#1573) -- the framework stack moves up a major across the board, with springdoc 3 and Spring AI 2.0. Thanks @bradyyie.
- Jackson 3 -- the serialization stack moves from
com.fasterxml.jacksontotools.jackson. Date encoding and default property inclusion are preserved, so stored documents and API payloads keep their shape.
Elasticsearch
- ES8 is the default indexing backend (#1756) -- this removes the Elasticsearch 7 core jar (
org.elasticsearch:elasticsearch:7.17.x) from the shipped image, clearing CVE-2025-37731 (PKI-realm auth bypass), which has no fix on the 7.x line. - ES7 is deprecated but still ships (#1757) -- selectable with
-PindexingBackend=elasticsearch7for users who need a bridge while they upgrade their cluster. - ES6 support is removed (#1758) -- the
elasticsearch_v6indexing type is gone; use ES8 (or deprecated ES7).
Runtime
- Java 25 (#1775) -- the server builds Java 25 bytecode and ships on a Java 25 JRE, with Gradle 9.8.2 and GraalVM 25.0.5 alignment. Self-hosted deployments running the JAR must run Java 25.
- GraalJS restricted host-access mode (#1775) -- an opt-in policy (
conductor.app.graaljs.restricted-host-access=true) that closes the GHSA-77c4-x563-ccgr command-execution path by blocking JavaScript access to arbitrary Java methods on bound objects. It ships disabled by default this release; a startup warning notes the default flips to restricted in 3.35.
Image
- Server image on
eclipse-temurin:25-jre-alpine(#1613, #1775, #1818) -- the Alpine base clears OS-level CVEs (perl,libssh2,nginx) that no dependency bump could reach, and the runtime tag floats to25-jre-alpineso each rebuild picks up the latest 25.x JVM patch and Alpine updates.
Big changes at a glance
- The server runtime baseline is Java 25; running the JAR on an older JVM is unsupported.
ObjectMapperProvider.getObjectMapper()returns atools.jackson.databind.ObjectMapper;JacksonExceptionno longer extendsIOException.spring-retryis replaced byorg.springframework.core.retry;javax.injectsupport is gone.- Self-managed ES 7.17 clusters require a cluster upgrade to ES 8.x.
- The
elasticsearch_v6indexing type is removed.
Developer notes
- SDK-driven test-harness suites run against a Jackson 2 client for now (#1751) -- the gRPC and HTTP end-to-end harness suites drive the published
conductor-client, which is still a Jackson 2 artifact. On the in-repo test classpath that artifact's bundledconductor-commoncollides with this project's Jackson 3conductor-common, so those suites stay excluded from CI until a Jackson 3conductor-clientis published. This is a test-classpath split-package issue only -- real SDK users consuming the published client are unaffected. Tracked in #1751.
Full Changelog: v3.33.0...v3.34.0