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.

Fairway services can now expose more than one portLatest 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 →
Caproni is now the strategic development platform StrategyDevelopment
Going forward, Caproni will replace the GitLab Development Kit everywhere across GitLab. Action is required by teams that still use GDK, especially to develop GitLab services.
September 3, 2026 Read more →
The feature-flags service is ready for production use Feature-FlagsDeployment
Feature flags for services outside the monolith are now available to all of GitLab engineering — define a flag in git, evaluate it with the LabKit client, and de-risk your next rollout.
September 1, 2026 Read more →
Next 2/2