ingestr v1.0.75 - Amplitude Source And Stream Export

ingestr v1.0.75 was published on 2026 07 10 at 14:14:03 UTC, with the release centered on Amplitude source support and stream export to disk. For data engineers, the practical change is a wider ingestion surface plus a more explicit path for moving streamed data through local storage.

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

The main application change in ingestr v1.0.75 is the Amplitude source work. The release notes list a merged pull request for adding the Amplitude source, followed by the source implementation itself. That is enough to treat this release as a connector surface change, not just routine maintenance.

For teams pulling product analytics into warehouse tables, this matters because Amplitude often sits beside billing, CRM, support, and event systems. A direct source in ingestr reduces the amount of glue code needed around that extract path. It also keeps the connector inside the same operational model as the rest of an ingestr based pipeline.

The notes do not list connector flags, schema details, paging behavior, auth fields, or rate limit handling. Operators should check the actual source documentation or code before putting this into a scheduled job. The release announcement only confirms that Amplitude source work landed in v1.0.75, not that every Amplitude API edge case is covered.

The second operator visible change is stream export to disk. That sounds small, but it is relevant for pipelines that need a local handoff before loading, inspection, replay, or transfer into another process. Disk backed export can be useful when stdout is too fragile as the only boundary between extract and downstream handling.

For data workflows, this can help with staged movement. A pipeline can extract a stream, write it to disk, then let another step validate or load that file. That creates a clearer failure boundary than a purely in memory handoff. It also gives operators something concrete to inspect when a run has partial output or malformed records.

The release notes do not specify file naming, format, cleanup behavior, atomic writes, or retry semantics. Those are the details that decide whether disk export is safe for unattended runs. Treat the feature as a new path to evaluate rather than a complete durability story.

This is a narrow release. It is not framed as a broad runtime change, and the notes do not mention breaking changes, migrations, or security fixes. The useful read is that v1.0.75 expands where ingestr can read from and adds a more tangible export path for streamed data.

The Amplitude source is the higher level product change. It can remove a custom extractor from a product analytics pipeline if its behavior matches the target workload. The stream export to disk change is lower level, but it may matter more for incident response and run debugging because it gives pipeline owners a file based artifact to inspect.

There is also a limit to what can be inferred from this release. The notes are short and mostly commit level. They do not document schema mapping, incremental state, idempotency, checkpoint handling, or back pressure. Those topics should be tested against a representative Amplitude account before this version becomes part of a production schedule.

The GitHub release page is the source of truth for the tag, publication time, and release assets.

The release is not marked as a prerelease. It is published as v1.0.75, and the metadata marks prerelease as false.

No breaking changes are listed in the release notes. Existing ingestr users should still run the normal connector smoke tests, especially if the deployment packages all sources together. For new Amplitude work, start with a small extract, inspect the output shape, and verify that stream export to disk behaves correctly under retry and cleanup conditions.