ingestr v1.1.3 - SQL Server CDC and NATS Reliability

ingestr v1.1.3 was published on July 20, 2026. The main operator visible change is hardened SQL Server CDC ingestion. This stable release also addresses a NATS streaming EOF path and two integration test reliability issues.

The full release notes and downloads are on the GitHub release page.

SQL Server CDC is the only source connector named in the changelog as receiving hardening. The notes do not identify a particular query, checkpoint, log sequence value, or recovery path. That limited detail matters. This should be treated as a targeted correctness or resilience fix, not as evidence of a new CDC mode or a changed connector contract.

For existing pipelines, validate the same behaviors that make CDC upgrades risky. Run a controlled insert, update, and delete sequence. Compare source events with destination rows, then restart ingestion at a known checkpoint and check for gaps or duplicates. A long running test should also cross a period with no source changes so that idle recovery gets exercised.

Nothing in the release notes names a new flag, connection setting, or migration step. Operators can keep the current configuration while testing the patch against a representative change stream. The practical winner is any SQL Server pipeline affected by the hardened path. Pipelines on other sources should not assume a connector level change from this entry.

Two changelog entries concern NATS. One merge is titled fix-nats-streaming-eof, which points to EOF handling in the streaming path. The notes do not say whether the EOF was treated as terminal, retryable, or tied to a specific NATS server state. They also do not state whether checkpoint behavior changed.

That leaves a clear test boundary for NATS users. Publish a finite batch, interrupt the connection, restore it, and verify the final record count. Also inspect duplicate handling after recovery. Those checks cover the common data integrity risks around an EOF without assuming an implementation detail that the release does not provide.

The other NATS entry fixes a flaky integration test container connection. That item is explicitly test scope. It should improve confidence in the connector test suite, but the notes do not claim a production client change from that commit. The distinction is useful: one entry addresses the streaming path, while the other makes its integration test environment less sensitive to container connection timing.

The changelog also replaces deprecated WithStartupTimeout usage with WithDeadline on ForAll. Based on the names in the release entry, this is test container lifecycle maintenance rather than an ingestion data plane feature. It removes deprecated API usage and makes the intended startup bound explicit at the call site.

No deadline value, affected suite, or timing result is included. There is therefore no basis for claiming faster tests or a wider startup window. Read this as maintenance that supports repeatable integration testing. Together with the flaky NATS container connection fix, it shows that half of this patch release is concerned with test reliability rather than new connector behavior.

The release is narrow. SQL Server CDC and NATS operators have concrete paths to validate, while users of unrelated connectors get no stated runtime change from these notes.