➔ ingestr v1.0.67 - Metrics Type Defaults
ingestr v1.0.67 was published on July 7, 2026. This release is not marked as a prerelease, and the one clear user facing change in the notes is an adjustment to default metrics types. For teams that run ingestr in scheduled data movement jobs, this is the kind of small data shape change that deserves a quick schema and downstream check before the next run.
➔ ingestr v1.0.64 - Snowflake Multi Table Deadlock Fix
ingestr v1.0.64 was published on July 2, 2026, as a stable GitHub release for the ingestr project. The release fixes a Snowflake multi table write deadlock caused by connection pool exhaustion, which is exactly the kind of small change that matters when a data job hangs and gives little signal. It is not marked as a prerelease.
➔ ingestr v1.0.56 - Google Search Console and Schema Evolution
ingestr v1.0.56 was published on June 30, 2026, with the main user visible change being Google Search Console work in the connector catalog and source layer. The release also keeps moving schema evolution logic toward destination owned DDL and removes command_running telemetry, which matters for teams that watch data pipeline behavior closely.
➔ ingestr v1.0.51 - Oracle Destination and CDC Updates
ingestr v1.0.51 was published on June 29, 2026, and the practical headline is Oracle destination support. The release also adds Vitess CDC via VStream, new Square and Recurly sources, and fixes around Square data shape and dependency risk. It is not marked as a prerelease.
➔ ingestr v1.0.44 - Streaming Sources and Braze Series
ingestr v1.0.44 was published on June 24, 2026, with streaming platform sources as the main user visible change. The release also extends the Braze source with more series tables, so teams moving event and marketing data through ingestr have a wider surface to sync. It is not marked as a prerelease.
➔ ingestr v1.0.42 - GitLab Users and Fan Out
ingestr v1.0.42 was published on June 24, 2026. This regular release is mainly about the GitLab source, with per project fan out for issue and merge request reads, a GitLab users table, and error handling cleanup. For teams moving GitLab data into a warehouse with ingestr, this is the part to check before the next scheduled sync.