logquill

Versioning and stability

One version for every language

All packages (crates, PyPI, npm, RubyGems, NuGet, Maven Central, Go, Swift) share one lockstep version number, following Semantic Versioning. 3.2.1 of the Python package and 3.2.1 of the Node package speak the same record contract and have the same features.

CI checks that every manifest agrees on the version before a release.

What each part of the version means

Bump When
Major Anything in the cross-language contract changes (record shape, level weights, field names, the llm block, the content policy, hash-chain format), or a public API is removed or changes meaning. A contract change is always a major bump, even if no code in one binding changed
Minor New backward-compatible features: a transport, a plugin, an adapter, a CLI command, a new optional field
Patch Bug fixes and documentation, with no change in the contract

What is covered by the stability promise

Stable within a major version:

Not covered:

Records over time

Pre-releases

Release candidates (X.Y.Z-rc.N) are not picked up by default; install them explicitly. They carry no stability promise.

Deprecation

A feature to be removed is marked deprecated in a minor release, with a changelog entry and a replacement named, and is removed no earlier than the next major release.

Supported lines

See Support for which versions receive fixes.