Decaf Blog In-depth updates on Decaf software, tooling, and open-source experiments

ingestr v1.0.37 - ESPN Source Parameter Cleanup

3 min read

ingestr v1.0.37 was published on June 18, 2026, with one functional change for the ESPN source: the connector no longer sends the dates URI parameter. For data teams that pull sports data through ingestr, the practical value is a cleaner request shape and less connector logic around a query value that this release removes.

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

ESPN source requests are simpler

The changelog for v1.0.37 is small. It says that ingestr drops the dates URI parameter from the ESPN source. It does not list a new ESPN schema, a new destination path, or a broader source rewrite.

That narrow scope is still relevant for production ingestion. Query parameters often end up outside the connector code itself. They appear in request logs, replay fixtures, proxy cache keys, allow lists, and monitoring labels. If an ESPN job has tests that assert exact HTTP paths, this release can change those expectations even when the logical source stays the same.

The release notes do not explain why the parameter was removed. The safe reading is to treat this as source request cleanup, not a new data contract. Operators should verify the outbound ESPN request shape and then compare the resulting rows against the previous pinned version.

What changes for pipeline operators

Pipeline owners should scan any wrapper code that builds ESPN source runs through ingestr. The release notes do not mention a new config key, a breaking migration, or a replacement parameter. Jobs should stop expecting dates in the outbound ESPN source URI when they run v1.0.37.

The important checks sit around orchestration and observability. Review replay cassettes, request signing rules, URL based metrics, and source allow lists that match full paths. A removed query parameter can look like a new endpoint to those systems even when the connector is fetching the same source.

This also matters for incident review. If dashboards group ESPN calls by full URL, the release may split metric history between the old and new request forms. That is not a data issue by itself, but it can make a normal deploy look noisy.

Narrow release with limited blast radius

v1.0.37 is not marked as a prerelease. The changelog contains no dependency upgrade, no destination change, and no documented schema migration. The only functional note is the ESPN source parameter removal; the remaining item is the merge record for that work.

That makes this a small operational release. It is useful when an ESPN ingestion job is affected by the old parameter behavior, but it is not a reason to retest unrelated sources unless your own packaging process requires a full suite. The release should be judged at the connector boundary.

Test focus for ESPN ingestion

Before rolling this into scheduled jobs, compare one ESPN source run on the old version and v1.0.37. Check status codes, record counts, null rates, and any partition field derived from date input. The GitHub release page does not claim a schema change, so a data shape difference should be investigated as a job or source behavior issue.

Teams that pin ingestr in a Docker image or a workflow runner should also confirm that logs and alerts still group ESPN calls as expected. URL level metrics can be brittle. A removed query parameter may shift labels even when the connector fetches the same logical source.

Where to get it