denis256 notes and projects

ingestr v1.0.63 was published on July 2, 2026, with a small but practical release for data teams that use the project to move data between sources and destinations. The main user visible change is Google Sheets destination support, while the operator side gets a golang.org/x/net bump to v0.55.0 for CVE-2026-25680. This release is not marked as a prerelease.

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

Google Sheets as a destination

The clearest user facing item in v1.0.63 is Google Sheets destination support. The changelog is terse, but it includes a merge from the Google Sheets destination support branch and a separate gsheets dest commit, so the release should matter to teams that want ingestr output in a spreadsheet rather than only in a database or warehouse target.

That is useful in the boring way that often matters in real operations. A sheet is not a warehouse, but many teams still use it for shared checks, finance reviews, ad hoc QA, or a handoff to people who do not live in SQL all day. Having it as a destination inside the same ingestion tool can remove a side script from the flow.

Read this as destination availability, not full behavior documentation. The notes do not list auth modes, sheet naming rules, overwrite behavior, or schema mapping details. Spreadsheet targets tend to hide sharp edges around types, empty cells, and repeated runs, so test a small representative table before putting this into a scheduled job.

Network dependency security update

Operators should also notice the dependency bump. The changelog updates golang.org/x/net to v0.55.0 and names CVE-2026-25680 as the reason. That is not a config change, but it matters for anyone packaging ingestr into images or approving it through an internal dependency scan.

If your build process scans Go modules, this is the item likely to close a finding. If you build from source, make sure the build pulls this release tag rather than an older local checkout. The release notes do not describe any app level change tied to the module bump, so treat it as dependency hygiene with security value.

Dependabot and repo hygiene

The release also includes a Dependabot related fix and a bot commit. There is not enough detail in the notes to call these user facing changes. The practical read is that v1.0.63 carries a small amount of repo maintenance next to the Google Sheets work and the network dependency update.

For most users, that means there is no announced migration step in this release. For operators with private mirrors, pinned module caches, or strict build approval, it is still worth checking CI output after the upgrade. Dependency maintenance is exactly where local build rules can disagree with upstream in annoying ways.

What to verify before rollout

The release notes do not mention breaking changes, deprecations, or migration steps. That keeps the upgrade story short, but the Google Sheets destination deserves a real smoke test. Try strings, numbers, timestamps, null values, and a rerun of the same load.

Also check what happens to sheet creation and update behavior in your own workflow. The changelog does not spell out those semantics, so do not infer too much from the phrase gsheets dest. Small releases can still change the path that matters most to your runbook.

Where to get it

• Release page: ingestr v1.0.63
• Project repo: bruin-data/ingestr
• Tag: v1.0.63