denis256 notes and projects

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.

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

Oracle destination support

The most direct operator change in v1.0.51 is Oracle destination support. For teams that already use ingestr as a small data movement tool, this adds another target system without asking them to build a separate load path.

The release notes do not list every Oracle option or caveat, so treat this as a feature to test with real tables before moving scheduled jobs. That is normal for a new destination. The important point is that Oracle now appears in the project scope as a write target, not only as something around the edges of the data stack.

This matters for boring enterprise data, which is usually where the hard work lives. If a pipeline has to land data near existing Oracle reporting or operational systems, fewer custom scripts means fewer places to hide broken retry logic.

Vitess CDC via VStream

Vitess also gets a meaningful update in this release. The changelog adds CDC support via VStream and documents Vitess and PlanetScale CDC usage. That gives users a clearer path for change capture instead of only batch style movement.

There are fixes around this work too. The release mentions matching keyspace qualified table names and streaming the copy phase from explicit shards. Those details are not glamorous, but they decide whether CDC behaves under real Vitess layouts.

For operators, the useful signal is that the Vitess work is not just a checkbox feature. The release includes docs, tests, and fixes around table naming and shard handling. That usually means the maintainers hit the rough parts while wiring it up, then made them explicit.

More sources and Square data fixes

v1.0.51 adds Square as a source. It also fixes Square catalog and cash drawer handling by always surfacing catalog tombstones, using a composite primary key for cash drawers, and materializing location_id on cash drawer shift rows.

Those are small words for data that can otherwise be annoying to reconcile. Tombstones matter when downstream systems need to know that something was deleted, not just that it stopped appearing. A better primary key matters when repeated syncs have to land cleanly.

Recurly is also added as a source in this release. The notes are sparse here, so there is not much to say without inventing behavior. The safe read is that ingestr now covers another billing related SaaS source, and users should check the release page and project docs before assuming exact table coverage.

Dependency and audit guidance

The release bumps go-chi/chi/v5 to v5.3.0 for IP spoofing advisories. That is a maintenance item, but it is the kind that should not be ignored by anyone shipping ingestr inside a service boundary or wrapped automation.

There is also new remediation guidance for license audit failure messages, plus refreshed audit lock data for the Vitess dependency tree and go-chi/chi/v5. This is mostly internal hygiene, but it has a real effect on contributors and packagers. A failing audit that explains the next step wastes less time than a failing audit that only says no.

None of the notes call out a breaking change or migration step. Still, this release touches destinations, sources, CDC, and dependencies, so pin the tag and test the paths you actually run.

Where to get it

• Release page: GitHub release page
• Repository: project repo
• Tag: v1.0.51