ingestr v1.1.45 - Satismeter Docs Image Removed

ingestr v1.1.45 landed on 31 August 2026 as a documentation patch. The tag merges pull request 1160 and drops a broken Satismeter image reference from the docs tree. If you pin this CLI for extract and load jobs, the binary behavior does not change at this tag.

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

bruin-data/ingestr tagged v1.1.45 with a short changelog. One commit is the merge of pull request 1160 from the fix-satismeter-docs-image branch. The other is the docs edit labeled fix(docs): remove broken satismeter image reference.

The merge hash is 83ab82bbcf7d09f997c1af519d9b8cca74ce5543. The docs hash is 76ed02c930fbf779368c042d41e1b28bbd143cf8. Those two lines are the entire published list. There is no connector patch, no destination write path change, and no CLI flag.

Treat that list as complete. If a source or destination you run is missing from it, it did not ship in this tag. Operators who bump pins on every GitHub release will rebuild images and recompute checksums for a docs only delta. Operators who gate bumps on words such as source, dest, cli, or breaking can skip the tag. The notes give enough signal to choose.

Pull request 1160 is the only pull request named. The branch name fix-satismeter-docs-image is the scope. The conventional prefix fix(docs) marks the docs lane, not a runtime source or dest lane.

A broken image in generated docs is a small defect with a noisy failure mode. Link checkers, docs CI, and HTML preview jobs fail on a missing image even when the extract job is healthy. Readers of the Satismeter page then see a gap where the screenshot or diagram should be.

Removing the reference is the right fix when the asset is gone and nobody restored the file. A dead src in Markdown or HTML keeps the docs site red until main is patched and a tag is cut. Shipping the delete as v1.1.45 lets doc mirrors and tag tracking builds pick up the cleanup without waiting for the next feature tag.

The cost is tag noise. Auto bump jobs will open PRs, rebuild container layers, and roll CLI pins. That work is real even when the CLI binary is unchanged. If your bump job keys only on the GitHub release event, add a changelog filter or a human approval step for docs only tags. If you already filter on fix(docs), this release is the example that filter is for.

If your pipeline renders the project docs into an internal portal, rebuild that portal from v1.1.45 and confirm the Satismeter page no longer 404s an image. If you never render the docs, this tag does not change your extract or load path.

Nothing in the notes names a table, a cursor, a SQL dialect, a file format, or a secret. No incremental key. No merge strategy. No load mode change. No checkpoint. The word Satismeter appears because an image on a docs page was broken, not because an extract path changed.

Do not infer a Satismeter source schema change from a docs commit message. The message says the image reference was removed. It does not mention request paths, page size, auth, or field lists.

If you are waiting on a runtime fix, stay on the tag that actually contains that fix. If your current pin already runs your jobs, staying there is correct until a later tag lists a source or destination change you care about.

Pin verification is still cheap. After a bump, run one job against a small table and compare row counts to the previous pin. For this release that check should match. If it does not, the delta is not in the published notes, and that is a bug report.

This is not a prerelease. GitHub marks it as a full release. The notes list no migration steps and no breaking changes.

Skip v1.1.45 if your pin policy only moves on runtime or security diffs. Take it if you vendor or publish the docs tree from Git tags and you want the Satismeter image 404 gone. Either way, read the GitHub release page before you change a production pin. The notes are short enough to read in full.

If you wrap ingestr in a container image, a docs only tag still rebuilds the image layer when the Dockerfile checks out the tag. Keep the previous image digest if you need to prove the binary did not move. The two commit hashes above are the audit trail.