Conduit v0.21.0 is a security release. It closes exposures found in an internal audit — an unauthenticated API, environment and file exfiltration, server-side request forgery, plaintext SASL credentials, and record values in logs and errors — and backports the same fixes to v0.20.6.
Conduit v0.20.5 is a patch release that fixes three ways records could be changed without an error: copies of a record sharing nested data, Avro decoding dropping map keys, and Avro encoding rewriting the values it was given. It also stops a self-referencing Avro schema from hanging the pipeline and fixes a silent value conversion in the built-in Postgres destination. Every v0.20.x user should upgrade. These fixes were planned for v0.20.3; v0.20.3 and v0.20.4 do not have them. Two conduit-commons advisories cover the Avro fixes: GHSA-fhm8-v27h-q65j and GHSA-2cr9-8q6v-733r.
Skip v0.21.0 and v0.21.1. Upgrade to v0.21.2.
v0.21.0 refuses to start every pipeline that has no dead-letter-queue block, including the hello-pipeline example and the template gallery, with pipeline.dlq_not_recoverable. The default DLQ never receives a record (the first nack stops the pipeline and the record is not acked), so v0.21.2 refuses a hash-only log DLQ only when it does receive records. No data is lost by the refusal: the pipeline does not start. v0.21.1 was tagged but never built.
Correction (2026-11-03): an earlier version of this post described features that did not ship in v0.21.0. The post now describes what the release contains. The items that did not ship are listed at the end, with where each one is planned.
Conduit v0.21.0 ships the first slice of the Kafka Connect migration work: conduit migrate kafka-connect for Debezium Postgres, the S3 sink and MirrorMaker 2, five certified connectors, protocol v3 with lossless structured values, Protobuf decode, and secrets at rest. It also changes several defaults, so read the breaking changes below before you upgrade.
Conduit v0.20.3 is a patch release. It fixes a panic in the split processor and a 60-second stall on graceful shutdown with destination SDK batching.
Conduit v0.20.4 is a patch release. It fixes a source read that ignored its context, gives a malformed conduit.yaml a stable error code, and documents every exit code in connectors bundle --help.
Conduit v0.20.1 is a patch release. It fixes data-loss bugs in the built-in Postgres, S3 and Kafka connectors, plus lifecycle bugs where a failed status write could leave a pipeline that could not be stopped or let one run twice.
Conduit v0.20.2 is a patch release. It fixes a bug where avro.encode could silently write wrong data when two pipelines in one process use schemas that share type names, plus four security issues, and adds a guard that refuses to run pipelines stored by a newer minor.
Conduit v0.20.0 adds conduit generate, a Postgres-to-pgvector RAG pipeline template, outbound HTTP for WASM processors (closed by default), and signed release artifacts. It fixes a SEV-0 bug in v0.19.0 where the Postgres snapshot-to-CDC handoff could stall silently, and a gRPC server panic. It also changes how stopped pipelines are reported; read Behavior changes before you upgrade.
Conduit v0.19.0 is the "embed it, scaffold it, trust it" release: Conduit is now a library you can run in-process in a Go app, pipelines start from a one-command template, and the data path got a crash-safety fix that closes a real at-least-once gap.
Conduit v0.18.0 is the "trust your connectors, see your pipelines" release: a signed connector registry you can install from the CLI with signatures and SLSA provenance verified before anything runs, and a built-in UI served by conduit run for watching and operating your pipelines.