ingestr v1.0.56 - Google Search Console and Schema Evolution

ingestr v1.0.56 was published on June 30, 2026, with a small but useful set of changes for teams that move web and marketing data into warehouses. The main item is Google Search Console support, backed by catalog work, a gsc source, and sitemap handling.

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

The visible connector change in this release is Google Search Console. The notes name three related entries: Add Google Search Console to connector catalog, gsc source, and sitemaps. That points to a practical path for teams that already treat search data as part of their content or acquisition data model.

For data engineers, the connector catalog item matters because catalog metadata is usually where discoverability starts. A source that exists only in code is easy to miss. A source that is represented in the catalog can be found, reviewed, and fitted into normal ingestion planning.

The gsc source line is also the part to test first. The release notes do not spell out table names, auth fields, cursor behavior, or rate limit handling. That means production use should begin with a small extraction and a destination table review. Search Console data often has natural grain choices around query, page, country, device, and date. The release notes do not say which of those are exposed here, so do not infer a schema from the product name alone.

Sitemap handling is worth a separate mention. Sitemaps sit near the boundary between web crawling, content inventory, and SEO reporting. When they are ingested alongside Search Console data, they can help compare declared site structure with actual search traffic. The notes only say sitemaps, so the safe read is that sitemap support was added or connected as part of this source work, not that a full crawler was introduced.

v1.0.56 also continues schema evolution work. The release notes call out Address schema evolution review feedback, Move schema evolution DDL into destinations, and refactor(schemaevolution): share evolve apply body across destinations.

The important part is the DDL placement. Schema evolution can look generic in the planner, but DDL is never fully generic at execution time. Warehouses differ on column addition, type widening, nullability, quoting, and transaction behavior. Moving schema evolution DDL into destinations is a sensible boundary because the destination is where those rules are known.

The shared evolve apply body suggests the project is also trying to keep common flow logic out of each destination implementation. That is a reasonable split: share the orchestration and keep the SQL details local to the destination. It should reduce repeated control flow while preserving destination specific DDL behavior.

There is not enough detail in the release notes to claim a new migration feature or a change in backward compatibility. Treat this as implementation cleanup around an already visible area. If you depend on automatic schema changes, test with a destination that matches production before rolling this tag into scheduled jobs.

The release removes command_running telemetry. The note is short, but it is operationally relevant. Command lifecycle telemetry can be useful when debugging CLI behavior, yet it also adds another event type that operators may need to filter, route, or account for.

Removing this signal should make telemetry output a little narrower. It may also affect any local dashboards, traces, or log queries that expected a command_running event. The release notes do not mention a replacement event, so the safe assumption is that consumers should stop depending on that name.

This is not a data plane change. It does not read like a connector behavior change or a destination write change. It is still worth checking if ingestr telemetry feeds into internal observability or audit pipelines.

Several changelog lines are merge or review items, including the workspace review branch and the Google Search Console source branch. Those lines are useful mainly as context. They show where the release work came from, but they do not describe independent operator facing behavior.

For a release this small, that matters. The signal is concentrated in three areas: the Google Search Console source work, the schema evolution DDL refactor, and the telemetry removal. The rest should be read as project maintenance unless you are auditing the exact commit history behind the tag.

No breaking change is stated in the release notes, and v1.0.56 is not marked as a prerelease. The cautious upgrade path is still to validate two things before broad rollout: one sample Google Search Console extraction, and one schema evolution case against the destination you actually use.

The release notes are available on the GitHub release page. Use them as the source of record for this tag, since the notes do not include expanded migration guidance.

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