Skip to main content

Conduit v0.16.0 release

· 2 min read

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.

tip

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 release

· One min read

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.

tip

Curious what's coming next? The roadmap tracks the phases we're executing against.

Conduit v0.15.1 release

· One min read

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.

tip

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.

Conduit v0.14.0 release

· One min read

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.

tip

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.