denis256 notes and projects

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.

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

Google Search Console enters the catalog

The most visible change in v1.0.56 is Google Search Console support showing up in the connector catalog. The changelog calls out both adding Google Search Console to the connector catalog and work on the gsc source, so users browsing available sources should have a clearer path to this data source.

For operators, that matters more than a cosmetic catalog entry. Search Console data is usually part of the same reporting loop as web traffic, landing pages, SEO checks, and search query analysis. Having it listed in the catalog reduces the usual guesswork around whether the source is supported by ingestr at all.

The notes do not spell out every option for the new source. That is worth noticing. Treat this as a release where the source and catalog entry land, then check the project docs or examples before wiring it into a production job. The release notes are useful, but they are not a full setup guide.

Sitemap work sits beside the new source

The changelog also includes sitemaps, which looks related to the same web data area as Google Search Console. The notes are short, so there is not enough detail to say whether this changes extraction behavior, catalog metadata, examples, or source internals.

The practical takeaway is narrower: this release has more than one web discovery related change. If a team uses ingestr for marketing data, search data, or site reporting, this is the part of the release to review first.

That said, do not infer more than the notes provide. There is no stated breaking change, no migration step, and no named config key in the release text. Keep the review focused on the source and catalog behavior that is actually mentioned.

Schema evolution logic moves into destinations

v1.0.56 continues the schema evolution work that has appeared in nearby ingestr releases. The important line is that schema evolution DDL moved into destinations. In plain terms, the destination layer is taking more responsibility for how schema changes are applied.

That is a sensible direction for a tool that writes to multiple targets. DDL is not portable in the pleasant way people wish it were. Each warehouse or database has its own edge cases, and moving that logic closer to the destination can make behavior easier to reason about.

The release also includes review feedback for schema evolution and a refactor that shares the evolve apply body across destinations. That sounds like maintenance work, but it is the useful kind. Shared code can reduce duplicate behavior, while destination specific DDL can still keep the sharp parts near the systems that need them.

Telemetry gets a small cleanup

The release removes command_running telemetry. The notes do not describe a user interface change around this, so this is mainly an operator and observability detail.

Removing a telemetry event can matter if dashboards, alerts, or audit queries depend on that exact event name. Before upgrading a monitored deployment, search for command_running in local observability queries and runbooks. If nothing depends on it, this should simply mean one less signal emitted by ingestr.

This is also a reminder that release notes with short commit style entries can still carry operational changes. The absence of a long migration section does not mean every monitoring setup is unaffected.

Where to get it

• Release page: GitHub release page
• Repository: bruin-data/ingestr
• Tag: v1.0.56