---
title: "theAuth API stability: SemVer rules for Go and TS"
description: "How theauth-go applies strict Semantic Versioning, which packages are stable or experimental, and what the TypeScript 1.x line promises."
canonical: https://theauth.dev/open/stability/
lastmod: 2026-10-31
---

API stability

# What is stable, and what is not

The Go module follows strict Semantic Versioning, and the document says exactly what counts as public API. The TypeScript core is on the 1.x line at 1.2.0 and follows semantic versioning, while many other TypeScript packages are still below 1.0. Go latest: v2.13.0.

[Read the stability policy](https://docs.theauth.dev/go/reference/stability) [How releases work](https://theauth.dev/open/releases/)

## Sources and review date

**Source**Last reviewed 2026-10-06

Go module

## Strict SemVer

From v1.0 the module follows Semantic Versioning strictly. The import path is github.com/glincker/theauth-go/v2.

- BreakingChanging a stable symbol's signature, name or documented behavior contract requires a new major version.
- AdditiveNew exported symbols, new optional Config fields and new methods on `*TheAuth` are non-breaking.
- DeprecationAnnounced one minor version before removal with a // Deprecated: godoc line.
- Not publicAnything under internal/, anything under examples/, test helpers, and the audit writer internals.

Surface

## Stable and experimental packages

The document lists stable symbols per package. In summary:

**Go packages**As of 2026-10-06

Stable

Experimental, may change in a minor release

- Storage interfaceAdding a method to Storage would break implementers, so new persistence operations land behind separate optional interfaces, detected at runtime. The base interface only grows in a major release.
- MigrationsPostgres and MySQL migrations are append-only. A rename ships as a new migration that adds the new column.
- Audit tableaudit_events is append-only by contract. Adapters expose insert and query, not update or delete.
- Stats countersExisting Stats counters keep their name and meaning. New fields are allowed.
- Without a majorBug fixes, performance work that keeps outputs, new optional config, new error sentinels and codes, and new audit actions.

Special rules

## What the document pins down

These rules exist so a minor upgrade does not break people who implement or depend on the interfaces.

TypeScript

## 1.x core, pre-1.0 elsewhere

Said plainly: the guarantee covers the 1.x core packages only.

The core package @glinr/theauth is at 1.2.0. The repository's [STABILITY.md](https://github.com/glincker/theauth/blob/main/STABILITY.md) puts @glinr/theauth, @glinr/theauth-client, @glinr/theauth-mcp and @glinr/theauth-cli on semantic versioning: breaking changes ship only in a major release. Packages still below 1.0, including most client, UI and tooling packages, may change between minor releases.

Its security policy gives the supported release line per package, and security fixes go to the latest line only. Pin versions and read release notes before upgrading. See [SECURITY.md](https://github.com/glincker/theauth/blob/main/SECURITY.md) for the current table.

## What we do not claim

- **No guarantee for pre-1.0 TypeScript packages.** Treat every minor release of a package below 1.0 as possibly breaking.
- **No guarantee for experimental Go APIs.** They are labeled experimental in the document for a reason.

## Related pages

- [Roadmap](https://theauth.dev/open/roadmap/)
- [Threat model](https://theauth.dev/open/threat-model/)
- [Governance](https://theauth.dev/open/governance/)
- [Releases](https://theauth.dev/open/releases/)
- [Compliance](https://theauth.dev/open/compliance/)
- [Open hub](https://theauth.dev/open/)
- [Security and disclosure](https://theauth.dev/security/)
