How ingestia.io identifies versions, communicates changes and preserves compatibility — so you can plan integrations with confidence.
What changed for users
Screen and behavior changes, in the Portuguese used by end users, are in Novidades.
Version format#
Each build carries a deterministic commit-based version in the format
v1.<day-of-year>.<commits-in-day>, with the commit hash and build timestamp.
Example (synthetic): v1.251.2 · commit 4a4ec2f · 2026-09-08T11:29:31Z.
- The version is auto-generated in the build (not hand-edited).
- It serves to trace which build is running and correlate with support.
- It is not a commercial release number: it identifies the build, not a package for sale.
Source of truth for state#
The state of each feature (available, limited access, planned) changes together with the code: state change = doc change in the same release — the doc never "preempts" a state the code does not support.
Track the consolidated state in Status and availability.
Compatibility and versioned formats (N−1)#
Formats that travel across versions — widgets, filters, theme, URL state and embed token — use versioned envelopes and a mandatory N−1 decoder:
- A newer reader always can read the previous version's format.
- An unknown field is never silently discarded on read.
- When a format version is bumped, the previous decoder is kept.
This means shared links, saved dashboards and embed tokens remain valid across updates.
Changes that break compatibility (breaking changes)#
When a change can affect integrations, the policy is:
- Prefer additive: new fields/options instead of removing/renaming.
- Signal the state: the feature page changes accordingly (e.g., it starts saying "planned" if something is postponed).
- Communicate first: changes that affect integrations (API/OData, embed, SSO/SCIM) are announced in What's new and through support.
- Database schema is additive: schema changes are additive and versioned (migrations), without breaking existing reads.
Migrations#
- Content formats (widget/filter/theme/URL/embed): automatic migration on read via the N−1 decoder — you don't need to rewrite anything.
- Metadata schema (control database): versioned migrations applied by the platform; no manual action from the customer.
- Business data (datalake): governed by the customer (controller) — see Governança e LGPD.
Deprecation#
- Deprecated features receive the
Discontinuedbadge in the docs; avoid depending on them. - Features that are not yet built remain under
Roadmap(e.g., true CDC, public webhooks, write API, per-member API key) — see Status and availability.
State changes already published#
A state change is a documentation change in the same release. What has changed so far:
| What | Before | Now | Why |
|---|---|---|---|
| Amazon S3 and Google object storage as source | Roadmap | Limited access | gained real read capability (listing and downloading the customer's bucket); general release depends on validation with a real bucket |
| Bling, Conta Azul and HubSpot | registration refused | Limited access | automatic renewal of access is now stored by the platform; the refusal no longer exists |
| Azure Blob Storage | registration refused | Limited access | container reading entered the same source flow as the others |
| Connector catalog | 21 | 110, in 14 categories | ERPs, stores, payment methods, CRMs, marketing, productivity, public data, warehouses, remote folders, generic APIs and compatible databases |
Every new connector entered as Limited access, never as available: each specification was written from the public API documentation, without real credentials. Promotion to available is a human decision, one connector at a time, after validation with a real account and 30 days of monitored execution. The full list, with the state of each one, is in Conectores.
TOTVS Protheus, Senior and PagBank were entered as Planned: their APIs are not public/stable or do not list records, so there is no connector — and saying that is better than offering one that would fail on the first call.
How to know "what changed for me"#
- Check Novidades for what changed in the product.
- Consult Status and availability for the overall picture.
- For integrations, monitor the behavior of the
/api/v1routes (error format and limits are in Erros e limites).
Limits of this page#
- The published history is What's new: changes the customer notices, not every build.
Related#
Last reviewed: 2026-09-08. Deterministic version per commit; N−1 compatibility of versioned formats.