Changelog

Each release gets an entry here, newest first, with what it adds, what it changes and what an existing project must do to upgrade. From 0.1, the release workflow writes each entry from the release’s merged pull requests, so it will match the GitHub release and what mb upgrade shows. Metrics Book follows semantic versioning: a change an existing project would fail is a major version, with an mb upgrade migration.

Unreleased: 0.1

The first release. Until it ships, nothing is on PyPI, no image is published, and the commands in the quickstart show how it will work. The stack is built in phases, in the order the design sets. Last updated 27 October 2026.

Phase	What it builds	Status
0	A probe of anfra on sample data	Built, in review
1	The monorepo, standards, security baseline, mb init, mb fmt and mb check	Built, in review
2	The data path: the job runner, the DuckDB and Postgres warehouses, dlt and dbt, publish and rollback, schedules	Built, in review
3	The semantic layer and the e-commerce template: 115 metrics, terms, reports, mb templates	Nearly done
4	Access: sign-in, service accounts, Cerbos policies, the proxy to anfra, the audit log	In progress
5	The catalog and the connector: lineage, search, the MCP tools and /api/v1	In progress
6	The CLI’s remote commands	Not started
7	Operating and monitoring: ops commands, budgets, the monitoring containers	Not started
8	The web app’s screens	Not started
9	Docs, deploy guides and agent evaluations	Not started
10	Release: signed images, the PyPI package, versioned docs, mb upgrade	Not started
11	Source adapters for the e-commerce template	Not started

“Built, in review” means the phase passes its checks, including the end-to-end test on DuckDB and Postgres, and waits for review before it merges.

The design describes every phase in full, with the reasons behind each decision.