One release history for Burst Load and CDC.
Omni Loader now presents bulk movement and continuous replication as peer capabilities on one engine. Release notes keep connector, behavior, deployment, and compatibility changes in one place.
Performance, recovery, mapping, and warehouse-loading changes.
Capture, apply, topology, schema, and correctness changes.
Agents, security, deployment, catalog, and control-plane changes.
Release notes
Changes are grouped by customer-visible behavior.
Each entry identifies the affected capability, connector or deployment surface, and any prerequisite, compatibility, or recovery consideration that operators need to carry into an upgrade.
Upgrade planning
Review contracts before changing a production pipeline.
Check source and target versions, capture mode, schema behavior, durable state, agent placement, and rollback expectations against the support matrix and the release note for the version you intend to deploy.
Keep exploring
See the connected parts of the platform.
Upgrade with the operational contract visible.
Tell us the deployed version, engines, capture modes, and topology. We will map the relevant release and compatibility checks.