Skip to content

Change Log

The change log is where platform updates land: new capabilities, new documentation, and changes to the paved path. Each update is its own dated page, newest first, so you can skim what has changed since you last looked or link a team to a specific announcement.

Entries are announcements, not reference material — each one links to the docs that carry the durable detail.

Cross-team alignment decisions are part of the feed too: when teams agree on a commitment, a contract, or a boundary, the agreement ships as an entry badged Decision, carrying a status, a DRI, and the stakeholders who were present — a system of record for what was agreed, by whom. The full decision log collects them in one place.

Posting an update? From doc-site/, run hugo new content changelog/YYYY-MM-DD-your-slug.md to scaffold an entry from the announcement template (or copy the frontmatter of any recent entry) — it carries the title, description, author attribution, tags, and the optional decision block, ready to fill in.

Database migrations have a paved path: migrator DeploymentDatabase
Theseus services now define schema migrations as a forward/backward SQL contract and run them from a migrator hook before each release starts, with validation, a rollback path, and one pass/fail signal. Agreed with Data Engineering; ready to adopt in every new service.
September 28, 2026 Read more →
Decision: GATE does not need platform multi-port for the multi-tenant deployment of iam-auth todayDecision DecisionDeployment
The Auth team has agreed GATE's HTTP/gRPC split is served by two single-listener charts today: no outstanding Theseus work is necessary to facilitate GATE's iam-auth deployment to gitlab.com. The one-chart, two-listener shape remains the direction to converge on, without a deadline attached.
September 16, 2026 Read more →
Fairway services can now expose more than one port DeploymentConfiguration
A service that speaks gRPC to the cluster and HTTP to the world could not be expressed in a Fairway manifest. spec.listeners replaces spec.containerPort, and existing manifests keep working untouched.
September 11, 2026 Read more →
Decision: database migrations ship as a forward/backward contract, run by an init containerDecision DecisionDeployment
Milestone 1 of Theseus database migrations is agreed: modular features supply paired forward and backward migrations as an API contract, an init container applies them, and Fairway deploys it automatically when a Postgres service opts in.
September 10, 2026 Read more →
Decision: cross-team alignment decisions are recorded on the change logDecision DecisionDocs
Alignment decisions between teams now ship as change log entries with a status, a DRI, and the stakeholders who were present — a system of record for what was agreed. This entry demonstrates the format with placeholder stakeholders.
September 9, 2026 Read more →
Prev 1/3 Next 3/3