Changelog

Release history for this documentation site, and how versions and build commits are assigned.

This build

This copy of the docs was taken from workspaces-build-v2-docs at commit 23312e9.

How versions are assigned

Two identifiers, answering different questions.

	Source	Changes	Answers
Version	`package.json`	On a release, deliberately	What changed, as a set
Commit	Git, at build time	Every commit	Exactly which revision built this page

The header shows both. The version links here; the commit links to the GitLab revision. Quoting the pair identifies a build exactly, which is what a docs bug report needs.

Semantic versioning, applied to documentation:

Bump	When
Major	A restructure that breaks existing URLs, or a documented platform decision reversed
Minor	A new section, a new page, or a documented behaviour change
Patch	Corrections, clarifications, diagram and styling fixes, dependency bumps

Versions track the docs, not the platform

This number versions the documentation site. The API it describes is versioned separately and independently — see API design principles for the /v1 path segment and the dated WB-Version header.

Release history

The authoritative record is CHANGELOG.md in the repository, kept in Keep a Changelog format.

Unreleased

Nothing yet.

0.2.0 — 6 October 2026

Added

Version management: release version and build commit in the site header, linking to this page and to the GitLab revision.
scripts/check-links.mjs plus check:links and verify scripts, auditing internal links and heading fragments across the built site.
AGENTS.md — working conventions for AI coding agents, including the versioning and GitFlow policy and staging server access.

0.1.0 — 6 October 2026

Added

Initial documentation site: Astro 7 with Starlight 0.42, API reference generated from openapi/workspaces-build.yaml.
57 authored pages across ten sections.
The v1 API contract, and the generated reference rendered from it.
51 SVG diagrams built from 13 theme-aware components.
Decision log with eleven architecture decision records.

How versions are assigned

Two identifiers, answering different questions.

	Source	Changes	Answers
Version	`package.json`	On a release, deliberately	What changed, as a set
Commit	Git, at build time	Every commit	Exactly which revision built this page

The header shows both. The version links here; the commit links to the GitLab revision. Quoting the pair identifies a build exactly, which is what a docs bug report needs.

Semantic versioning, applied to documentation:

Bump	When
Major	A restructure that breaks existing URLs, or a documented platform decision reversed
Minor	A new section, a new page, or a documented behaviour change
Patch	Corrections, clarifications, diagram and styling fixes, dependency bumps

Versions track the docs, not the platform

This number versions the documentation site. The API it describes is versioned separately and independently — see API design principles for the /v1 path segment and the dated WB-Version header.

Release history

The authoritative record is CHANGELOG.md in the repository, kept in Keep a Changelog format.

Unreleased

Nothing yet.

0.2.0 — 6 October 2026

Added

Version management: release version and build commit in the site header, linking to this page and to the GitLab revision.

scripts/check-links.mjs plus check:links and verify scripts, auditing internal links and heading fragments across the built site.

AGENTS.md — working conventions for AI coding agents, including the versioning and GitFlow policy and staging server access.

0.1.0 — 6 October 2026

Added

Initial documentation site: Astro 7 with Starlight 0.42, API reference generated from openapi/workspaces-build.yaml.

57 authored pages across ten sections.

The v1 API contract, and the generated reference rendered from it.

51 SVG diagrams built from 13 theme-aware components.

Decision log with eleven architecture decision records.