ingestr v1.0.37 - ESPN URI Parameter Cleanup

ingestr v1.0.37 was published on June 18, 2026, with a narrow ESPN source change: the connector drops the dates URI parameter from its requests. This is not marked as a prerelease, and the useful signal for data engineers is request shape, not a broad feature set.

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

The functional item in this release is simple: the ESPN source no longer sends the dates URI parameter. For an ingestion tool, that is still an operator visible change. URI parameters are part of the contract between a source connector and the upstream endpoint, and small request differences can affect cache behavior, endpoint routing, and retry patterns.

The release notes do not state the upstream reason for the change. That matters. Treat this as a compatibility cleanup for the ESPN source, not as a schema update or a new data coverage claim. There is no note about added fields, removed fields, pagination behavior, rate limit handling, or destination changes.

For scheduled ETL and ELT jobs, the practical check is whether ESPN source runs become quieter after this release. Look at request failures, empty result windows, and any job logic that assumed the previous URI contained dates. If downstream logs or tests compare full request URLs, update those expectations with care.

One behavior change, one merge entry ¶

The changelog contains one functional entry and one merge entry. That is a small release by design. It should not be read as a general ingestr connector refresh.

This distinction is useful for platform operators. A merge entry confirms how the change arrived in the release, but it does not describe a second runtime behavior. The runtime point remains the ESPN source request cleanup.

There is also no prerelease flag on this tag. Operators who pin release versions can treat v1.0.37 as a normal release tag, while still doing the usual connector level validation before moving scheduled ingestion jobs. The notes do not mention migrations, config changes, new CLI flags, or credential changes.

Start with the ESPN source jobs that are most sensitive to date window behavior. The release says the URI parameter was dropped, so date filtering, if used by a pipeline, should be verified at the data contract level rather than assumed from the old request string.

Check three areas. First, compare row counts for the same expected window before and after the upgrade. Second, review any monitoring that parses source request URLs, since dates may no longer appear. Third, inspect downstream partitions or destination tables where ESPN data lands, especially if the pipeline uses date based loads.

This is also a good place to separate connector behavior from orchestration behavior. If a job still passes a date argument into a higher level schedule, that schedule may remain valid even though the ESPN source request no longer includes the old URI parameter. The release note only says the source drops the URI param. It does not say schedules, state handling, or destinations changed.

The limited changelog is useful because it reduces the review surface. There is no evidence in the release notes of destination changes, broad dependency churn, or framework refactoring. For teams running ingestr in production, that means the upgrade review can stay close to ESPN source behavior.

The risk is also narrow. A small connector change can still break an extraction path if local assumptions are too strict. Tests that assert exact URLs, monitors that match query strings, and replay tooling that records raw request paths are the main places to check.

If your ingestr deployment does not use the ESPN source, the release notes do not point to an urgent reason to move. If it does, the GitHub release page is worth reading before the next scheduled run.