8.1 Documentation versions

Every article shows its product, documentation set and the software version it was reviewed against at the top. This page lists every registered documentation set and explains how version numbers are updated.

Available documentation

Product	Documentation set	Reviewed against	Release status	Reviewed on
Free open-source Web	Latest verified · Alpha	0.2.0-alpha.6	Candidate, not publicly released	2026-09-24

This "latest verified" documentation opens by default. It is updated with the source code and its date is refreshed after each review; it is not a frozen snapshot of a release.

Pro, Cloud and Enterprise are still planned and only have planning pages: Pro, Cloud, Enterprise.

Fixed-version documentation

When the first release with complete release evidence ships, a copy of the documentation will be frozen at the same time under /v/<version>/, for example /v/0.2.0/start/quickstart. Frozen text, screenshots and navigation do not change afterwards; a correction gets a new revision while the original link keeps working.

Until then there is no fixed-version documentation. Versions 0.2.0-alpha.1 to alpha.3 did not save documentation when they were tagged, so documentation for them will not be recreated after the fact.

What "latest" means

"Latest" points to the newest documentation set that may be public and has passed review. Once a stable release exists, the default points to the newest stable release; previews must be chosen explicitly from the version menu and never take the default place.

A link to a fixed version always stays on that version; it will not jump to the latest documentation because you visited it before.

Reading version numbers

Version numbers follow semantic versioning: major.minor.patch, with suffixes such as -alpha.N for previews. See the software changelog for what changed in each version and the development log for finished work that has not shipped yet. A machine-readable list is published as docs-manifest.json at the site root.