denis256 notes and projects

ingestr v1.0.47 was published on June 25, 2026, with user visible work around Reddit Ads authentication, account discovery, and the new Chargebee source. The main change is OAuth refresh token support for Reddit Ads, because it makes recurring ad data jobs less dependent on manual credential handling. This release is not marked as a prerelease.

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

Reddit Ads OAuth Gets Refresh Token Auth

The biggest operational change in v1.0.47 is the addition of OAuth refresh token auth for the Reddit Ads source. For teams that pull paid media data on a schedule, this is the part that matters first.

Before this kind of change, the awkward bit is usually token lifetime. A source can be useful in a local test, then become noisy in production when credentials expire and a scheduled sync starts failing. The release notes do not describe the full user setup flow, so there is no point inventing one here. What they do say is enough: Reddit Ads can now use refresh token based OAuth credentials.

That should make the source a better fit for repeat runs. It also reduces the need for brittle side work around credential renewal. In data ingestion, boring auth is good auth. Nobody wants a dashboard gap because an ad API token aged out overnight.

Account Discovery and Table Scope Are Clearer

The release also adds account auto discovery and per table account scoping. That is a practical change for users with more than one ad account, which is common in agency setups, multi brand companies, and teams that split spend by business unit.

Auto discovery helps the connector find the available accounts instead of forcing users to wire every target manually. Per table account scoping is the other side of the same problem. It lets a table run with a tighter account boundary, which is useful when different tables should not all read the same account set.

This matters most when a pipeline grows from one quick export into a real scheduled job. Loose account selection can create messy data, bigger pulls, and harder debugging. More explicit scope keeps the ingestion path easier to reason about.

OAuth Token Requests Now Retry POST Failures

Another Reddit Ads related fix is retry support for POST requests that hit 429 or 5xx responses during the OAuth token request. That is a small note, but it is the kind of small note that operators notice.

OAuth token endpoints can return rate limit errors or transient server errors. Without retry behavior, a temporary API problem can fail the whole run before the source has even started reading business data. With retry behavior for these POST requests, ingestr has a better chance of riding out short API trouble.

This is not a promise that every API failure disappears. It does narrow one common failure path. For scheduled ingestion, that is usually enough to turn some random failed runs into successful retries, which means fewer manual reruns and fewer noisy alerts.

Chargebee Source Lands

v1.0.47 adds a Chargebee source. The release notes only state the source addition, so the safe reading is simple: ingestr can now target Chargebee as another upstream system.

That is still useful news for teams that already use ingestr as a lightweight path into their warehouse. Chargebee data is often tied to billing, subscriptions, customers, and account state. Getting it through the same ingestion tool as other sources can simplify the operational shape, even if users still need to inspect the project docs or source configuration before wiring it into production.

The changelog also includes a test change that swaps in a low entropy fake token to satisfy gitleaks. That is internal hygiene, not a runtime feature. It is still worth noting because secret scanning friction is real, and keeping tests friendly to scanners helps avoid noisy CI failures.

Where to get it

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