Releases & changelog

LiteORM’s release notes and version history live with the source, not in these docs. This page points you to the authoritative places and states the versioning and supported-Go policy, so what you read here never drifts from what was actually shipped.

• GitHub Releases — the canonical, per-version changelog, with highlights and upgrade notes for each tagged release: github.com/go-again/liteorm/releases.
• pkg.go.dev version history — every published module version, with the exact release dates and diffable docs: pkg.go.dev/liteorm.org?tab=versions.

To pin or upgrade, use the standard Go tooling against those versions:

go get liteorm.org@latest        # newest release
go get liteorm.org@v1.2.3        # a specific tag

The backend and tooling subpackages (liteorm.org/dialect/postgres, liteorm.org/studio, and so on) are separate modules with their own tags — check each on pkg.go.dev.

LiteORM follows semantic versioning. Within a major version, minor releases add features and patch releases fix bugs without breaking the public API; a breaking change bumps the major version. Anything under an internal/ path or documented as experimental is exempt and may change at any time.

LiteORM targets the two most recent Go releases; the authoritative minimum is pinned in each module’s go.mod. This narrow, current window is deliberate — it lets the code use generics, iter.Seq2, and log/slog without compatibility shims. See Supported Go versions for the rationale and upgrade guidance.

• Supported Go versions — the two-release policy and why it exists.
• Backends — the backends and their driver modules.
• Full API: liteorm.org.