denis256 notes and projects

ingestr v1.0.40 was published on June 23, 2026, with a small but practical set of changes for teams moving product and marketing data. The main user visible item is a new Braze source, backed by catalog wiring so server based connector discovery can expose it. The same release also fixes a KPI window bug that could drop the start day from a metric range.

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

Braze source support arrives

The headline change is Braze source support. The changelog lists Add Braze source, followed by review work on that source. That means ingestr users get a new path for pulling Braze data through the same release channel as other sources, without treating Braze as an out of tree addition.

The release notes do not spell out endpoint coverage, table names, or auth fields. That is worth saying because connector releases often hide important details there. For this announcement, the safe read is simple: Braze is now present in the project, and the exact usage details should come from the project docs or code in the repo.

For teams already landing data from product, CRM, or messaging systems, this is the change to check first. Braze often sits close to customer engagement workflows, so a native source in ingestr can reduce the amount of glue code around campaign and messaging data. The release notes are sparse, so treat the first rollout like any new connector: test one dataset, verify row counts, then add it to scheduled jobs.

Server catalog wiring for Braze

The release also adds Braze to the server connector catalog. This is not just housekeeping. If a deployment reads that catalog to show available sources, validate configured connectors, or build connector lists, Braze should now appear through the normal catalog path.

That matters for operators because connector code alone is not always enough. A source can exist in the repo and still be awkward to use if the server side catalog cannot see it. This release closes that gap for Braze, which should make the connector easier to discover in deployments that depend on the server catalog.

The changelog does not describe a separate migration step for this catalog update. There is also no warning about renamed connector keys or removed sources. The practical action is to refresh any environment that consumes the catalog and confirm Braze appears where source connectors are listed.

KPI windows keep the start day

ingestr v1.0.40 also fixes a KPI window bug where the start day could be dropped. The release note calls it an off-by-one problem. In plain terms, a window that should include its first day could start one day late.

For data pipelines, this sort of bug is small in code and annoying in output. The result can be totals that look close enough to pass a quick scan but are wrong at a period boundary. Anyone using KPI windows should treat this as the operational fix in the release, especially if reports depend on exact start dates.

This is also the change most likely to affect old output. If a KPI job used affected windows before the update, compare one known range before and after the upgrade. The expected difference is not a new metric definition. It is the missing start day being included again.

Review cleanup and release shape

The changelog includes a Greptile review follow up on the Braze source and a merge commit for pull request #849. That points to review driven cleanup around the new connector rather than a separate feature area. It is useful context, but it should not be read as another user facing capability.

This release is not marked as a prerelease in the GitHub metadata. It is a compact stable release: one new source, one catalog entry, one KPI boundary fix, and review work around the source. No breaking change, deprecation, or manual migration step is called out in the release notes.

Where to get it

• Release page: ingestr v1.0.40 GitHub release
• Project repo: bruin-data/ingestr
• Tag: v1.0.40