ingestr v1.1.12 was published on July 29, 2026. The main change for data pipelines is more complete BigQuery schema inspection: GetTableSchema now reads back maximum lengths for STRING and BYTES columns.
The full release notes and downloads are on the GitHub release page. GitHub marks v1.1.12 as a regular release, not a prerelease.
BigQuery length bounds return with the schema ¶
The BigQuery change is narrow, but it affects a useful schema contract. When GetTableSchema inspects a table, v1.1.12 reads the maximum length attached to STRING and BYTES fields. Earlier output could omit that part of the field definition even when BigQuery stored it.
That distinction matters to code which compares schemas. A bounded STRING column and an unbounded STRING column are not the same contract. If the reader drops the bound, a schema diff can miss a constraint or report an incomplete destination model. Catalog generation and validation code can also carry less information than the table actually contains.
The release notes do not describe a write path change, a table migration, or broader type handling. They only state that these two maximum length values are read back. Treat this as a schema fidelity correction, not a new BigQuery loading mode. Teams that added local workarounds for missing length metadata should compare the returned schema before removing them.
CLI telemetry gets an audit and a routing change ¶
Two changelog entries concern CLI telemetry. One audits and tightens telemetry events. The other changes the RudderStack base URI. These are separate changes: one concerns which CLI events are emitted or how they are shaped, while the other concerns where the telemetry client sends them.
The notes do not name event fields, the previous URI, or the replacement URI. That limits what can be concluded from the release announcement. In particular, there is no stated promise that telemetry is disabled, that payloads are compatible with an existing collector, or that network policy rules remain unchanged.
For restricted runners, check outbound requests during a representative command before promoting the version. A fixed egress allow list may need attention when a telemetry service changes its base URI. Environments that inspect telemetry payloads for compliance should also verify the actual event set instead of treating the word tighten as a complete data handling specification.
Scope and operator checks ¶
This is a small release with three substantive items: BigQuery length metadata, tighter CLI telemetry events, and a new RudderStack base URI. The changelog also records the merge for the BigQuery work, but that merge is not a fourth runtime change.
No breaking change or migration step is listed. Even so, schema sensitive pipelines should capture GetTableSchema output before and after the upgrade. Focus the comparison on BigQuery STRING and BYTES fields with explicit maximum lengths. This provides a direct check that the intended metadata now survives inspection.
Telemetry behavior deserves a separate smoke test where outbound access is controlled. Run the same CLI operation under the old and new versions, then compare destinations and event content using the observability already present in the runner. The sparse notes do not justify broader assumptions about collection policy.