Skip to main content
This is the only list of minimum versions. Other pages link here instead of stating their own. It is generated from the compatibility manifest in the autter-runtime repository, which the SDKs bundle and the ingester serves at GET /v1/compat.

What “compatible release” means

A feature works when both sides are at least the version in its row:
  • the SDK that sends it. 1.4.0+ means 1.4.0 or any later 1.x release, the same as the npm range ^1.4.0;
  • the ingester that stores it, with its ClickHouse migrations applied.
On Autter cloud (otlp.autter.dev) the ingester is always current, so only the SDK column matters. Self-hosted, upgrade the ingester first: its migrations run at startup. ”–” means that package does not send the feature. Features with no SDK version are things the ingester does with whatever it receives (any OTLP sender, @autter/runtime-cli, or the dashboard). Don’t read the table by hand for a real setup. doctor lists which of these are active for the SDKs installed in your project and the ingester you point it at, and flags version skew either way:

Table

Notes

  • Ingester 1.3.0 created the latency table but rejected numeric delta temporality, so endpoint latency needs ingester 1.3.1.
  • Ingesters older than 1.8.0 reject a whole browser batch with a 400 when it contains an event type they don’t know, errors included. Upgrade the ingester before the browser SDK.
  • The SDKs warn once at runtime when a feature you use needs a newer ingester, naming both versions and the fix.