ingestr v1.1.11 - Iceberg Interval Bound Correction

ingestr v1.1.11 was published on July 28, 2026. Its main operator visible change corrects Iceberg time interval bound normalization, a narrow data correctness fix in a release otherwise concerned with packaging and developer checks. The release is not marked as a prerelease.

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

Commit f295412d21237d6a5af245572c6471f0a599de9c corrects the normalization of Iceberg time interval bounds under PR #1028. For data engineers, this is the only documented change in v1.1.11 that touches data handling. Pipelines that exercise interval types against Iceberg are therefore the first place to test this release.

The notes do not identify the failing input forms, the affected Iceberg schema variants, or the before and after values. They also do not say whether the correction applies only to new writes or has any implication for existing table data. That limited detail matters. The safe validation path is to run representative interval values through a staging pipeline, inspect the resulting schema and rows, and compare the bounds with the source values.

Nothing in the v1.1.11 release notes calls for a schema migration or a backfill. Operators should not infer that either action is required. Existing Iceberg workloads still deserve a targeted regression test because the fix is explicitly about value normalization at a type boundary.

The release also stops publishing a macOS Intel wheel to PyPI. The merge commit 1e1e41bdc4aedf10b06df122eea0cadbd972d345 and the CI change c71a6ac69e916636fab0fe8c8bfab8c3cdd19709 describe the same packaging decision. They should not be counted as two separate user features.

This affects artifact availability rather than extraction or loading behavior. Teams with Intel Mac developer systems or self hosted runners should verify a clean installation from PyPI before adopting the tag. The notes do not name a replacement wheel, a support window, or an alternative installation procedure. They also do not announce changes to Linux or macOS Apple Silicon artifacts.

For most production ETL environments, the operational question is indirect: does any build or release job still resolve dependencies on an Intel Mac? If so, pinning v1.1.11 without a clean environment test can turn a packaging policy change into a failed deployment before a pipeline starts.

Commit 9932177097a4da4fe0634ee4b76c0190f017a94d speeds up local Go checks under PR #1037. The changelog provides no timing result, command name, cache detail, or change to the checks themselves. This is a contributor workflow improvement, not a documented runtime performance change.

That distinction keeps release evaluation grounded. There is no basis in these notes to expect lower extraction latency, higher load throughput, or shorter production job duration. Maintainers working on the Go portion of ingestr may see quicker local feedback, while platform operators have no new setting or deployment action associated with this commit.

Taken together, v1.1.11 is a small corrective release. The Iceberg fix warrants data level verification. The wheel change warrants an installation check on Intel Mac systems. The Go check change can remain outside the production rollout decision.