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.
Conduit v0.17.0 makes Conduit faster to build with and easier for an agent to drive: live config hot-reload while a pipeline runs, direct pipeline lifecycle control from the CLI, a repair command, and agent-legible docs served over MCP.
Conduit v0.16.1 hardens the operational surface introduced in v0.16.0: deterministic exit codes, secret redaction in logs, and a build-time guarantee that user-facing errors carry a stable code.
Conduit v0.16.0 is the first release built end-to-end against the Phase 1 execution plan: a real first-five-minutes experience, structured errors instead of opaque strings, and the deployment basics — readiness, liveness, metrics, full env-config — that make Conduit boring to run in a container or a pod.
Deterministic CLI exit codes, connector-config redaction in logs, and a CI guard enforcing error-code coverage landed on main shortly after and ship in the upcoming v0.16.1.
Conduit v0.15.0 is out — the first stable release since the project came back from about 15 months dormant. This cut stabilizes the nightly build train we've been running since restarting, and clears out a handful of provisioning and compatibility bugs that had piled up.
Curious what's coming next? The roadmap tracks the phases we're executing against.
Conduit v0.15.1 is a same-day patch for a shutdown bug: Conduit only registered SIGINT, so SIGTERM — the signal docker stop, kubectl delete pod, and systemctl stop all send — bypassed graceful shutdown and killed the process immediately.
This wasn't silent data loss on its own — at-least-once delivery and crash-safe positions still recover an abrupt kill — but it meant every container or pod recycle skipped draining in-flight records and checkpointing, causing duplicate-delivery storms and unclean checkpoints on restart.
We're happy to announce the release of Conduit v0.14.0, introducing the split and clone processors, which enables one source record to trigger a write of multiple records in the destination.
The new processors return multiple records, which is currently only supported in the new v2 engine. If you want to try them out, you need to start Conduit using conduit run --preview.pipeline-arch-v2.
Conduit's ecosystem got richer with the release of a new connector: Box connector v0.1.0. This release brings us a destination for Box.
Conduit HTTP Connector v0.4.0 is now available, introducing a new configuration parameter for the source and destination connectors.