ingestr v1.0.54 - JSON Progress Output

ingestr v1.0.54 was published on June 30, 2026, and the release centers on --progress json for structured progress output. For ETL and ELT operators, the practical value is machine readable progress from ingestr runs without adding a wrapper that parses terminal text.

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

The new --progress json mode is the only feature called out in the v1.0.54 notes. That makes the release small, but not empty for platform teams. Progress output is one of the places where CLI tools often leak operational state through text that was written for people. A JSON mode gives job runners a cleaner boundary.

In Airflow, cron based runners, GitHub Actions, and container entrypoints, the useful part is not the display format. It is the contract. A parent process can capture stdout, split records, and feed a log backend or alert rule with fewer assumptions about wording. That matters when a sync job is long enough that “still alive” and “stuck” need different signals.

Structured progress is most useful when the logs are consumed after the job exits. Operators can attach fields from --progress json to run ids, dataset names, task attempts, or container metadata outside ingestr. The release notes do not describe a schema, so consumers should treat the exact fields as an observed interface until they verify output in their own jobs.

That caveat is important. JSON output reduces the cost of parsing, but it does not remove versioning risk by itself. Any log processor that branches on field names should have tests around a sample ingestr run. If the pipeline uses strict JSON decoding, it should also decide what happens when progress output is mixed with normal error text.

For web processing jobs, this is also useful around backfill runs that need progress visible in the same place as request logs, queue logs, and container events. A JSON progress stream can be indexed beside normal job metadata. That gives an operator enough context to compare a slow run with prior runs without reading a full terminal transcript.

There are no connector changes named in the release notes. No source or destination is called out, and there is no migration step listed for existing ingestr tasks. That is useful context because recent ingestr posts on this site covered StarRocks, Oracle, Vitess, Postgres CDC, Braze, GitLab, and BigQuery behavior. v1.0.54 is not another connector patch based on the published notes.

The GitHub metadata also does not mark v1.0.54 as a prerelease. Treat it as a normal release, with the normal caution for any CLI output change: test the exact command line used by the scheduler before changing dashboards or alert rules. The GitHub release page is the source of record for this tag.

Use the release tag from the project rather than a nearby ingestr version if scheduler code depends on JSON progress.