denis256 notes and projects

ingestr v1.0.37 was published on June 18, 2026, for the bruin-data/ingestr project. The main change is small but concrete: the ESPN source drops the dates URI param from its request path, so teams using that source should check any jobs that depend on date scoped ESPN pulls. This release is not marked as a prerelease.

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

ESPN source drops dates from the URI

The changelog has one user visible code change: the ESPN source no longer sends the dates URI param. That sounds small, and it is, but connector code often breaks on small request shape details. If an upstream API treats query params strictly, removing one param can be the difference between a clean sync and a confusing empty response.

For ingestr users, the relevant question is simple. Do you run the ESPN source, and do you expect date scoped output from it? If yes, test this release against a known slice of data and compare the result count with the older tag.

The release notes do not describe a schema change, a loader change, or a new CLI option. Treat this as an ESPN source request behavior update, not a broad ingestion change.

What operators should validate

Because the change is focused on URI construction, validation should be practical. Run the same ESPN source config on v1.0.37 and on the version currently used in production. Compare row counts, loaded tables, and any scheduler logs that capture source URL details.

Pay special attention to jobs that were pinned to a fixed date window. The release note says the param was dropped, but it does not say that all date handling was removed. That distinction matters. It means operators should verify outcome data instead of assuming the source now ignores dates.

If your pipeline wraps ingestr in Airflow, Dagster, cron, or another scheduler, keep the first rollout small. This is a connector change, so blast radius depends on which sources are active. Pipelines that do not use the ESPN source should not see a functional change from the notes in this release.

A narrow release surface

The second changelog entry is the merge entry for the ESPN change. There are no listed loader fixes, destination changes, dependency bumps, or migration notes. That makes v1.0.37 a narrow patch release.

This is useful in a boring way. When a release has one source change, review is easier. You can decide based on whether the ESPN source matters to your estate. If it does, test it with real configs. If it does not, this tag is unlikely to change your normal ingestr behavior, at least based on the published notes.

There is also no prerelease marker in the metadata. For users who avoid beta or release candidate tags in automation, v1.0.37 is a normal GitHub release.

Upgrade notes

The notes do not mention breaking changes, deprecations, or migration steps. There is no new config key to set and no old key called out for removal.

Still, source behavior changes deserve a short check before promotion. Save the before and after row counts for one ESPN run, then promote only if the output matches what your downstream model expects. Annoying, yes. Cheaper than explaining a silent data shape change later.

Where to get it

• Release page: ingestr v1.0.37
• Repository: bruin-data/ingestr
• Tag: v1.0.37