ingestr v1.0.56 - GSC Source And Schema Evolution

bruin-data/ingestr v1.0.56 was published on June 30, 2026, at 17:46:24 UTC. The main operator visible change is Google Search Console entering the connector path, with source work and catalog coverage landing beside schema evolution changes in destination code. This is not marked as a prerelease.

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

The release notes call out Google Search Console in two places: source work and connector catalog coverage. That matters for teams that treat search analytics as pipeline input rather than a dashboard export. Once this connector path is wired into ingestr, Search Console data can sit closer to the same operational flow as other extraction jobs.

The notes do not spell out every stream, field, or auth mode. That is worth stating because Search Console data can vary by site property, date window, and dimension set. For a production rollout, the practical checks are still the same: confirm the configured source maps to the expected property, inspect row counts across adjacent date ranges, and verify that retries do not duplicate records in the destination.

The catalog entry is also useful from an operations point of view. Catalog coverage is how users discover whether a source is meant to be first class or just present in code. This release moves Google Search Console toward the visible supported surface of the project, which reduces guesswork for teams building recurring extraction jobs.

The more structural change is the move of schema evolution DDL into destinations. That is the right layer to care about DDL because each destination has its own behavior around column changes, type widening, table metadata, permissions, and transactional guarantees.

The changelog also mentions shared evolve apply body work across destinations. That reads like internal refactor, but it is still relevant for data engineers. Schema evolution code tends to fail in the edges: nullable columns, late arriving fields, name casing, and destination specific DDL quirks. Sharing common apply logic while leaving DDL decisions in destination code can reduce duplicated behavior without pretending that every warehouse handles schema changes the same way.

The release notes mention review feedback around schema evolution as well. There is no stated breaking change or migration step, so this looks like maintenance of the evolution path rather than a new user facing contract. Operators should still test this release with a table that receives a new column, since schema evolution bugs usually show up only when real payload shape changes arrive.

The release removes command_running telemetry. For platform teams, less command telemetry can be useful when a tool runs inside scheduled jobs, shared runners, or environments with strict audit expectations. The notes do not say that all telemetry changed, only that this specific event was removed.

The changelog also includes sitemaps. The release notes do not expand on scope, so this should be treated as a small web processing change unless the local pipeline depends directly on sitemap extraction or discovery. If sitemap input is part of a crawl or content ingestion flow, this is the area to smoke test after upgrade.

Taken together, v1.0.56 is a small release with one clear source addition and a few maintenance changes around schema handling and runtime metadata. The GitHub release page is terse, so this is not a release where operators can infer support details beyond the lines listed there.