## Changelog

Use this page for reader-facing release notes across GitBook content, public docs structure, tools, auth flows, and externally visible platform changes that matter to readers.

{% figure src="/docs-images/gitbook-changelog.png" alt="GitBook changelog page" caption="The changelog page gives readers one stable public record for docs, auth, tools, and cross-app release notes." /%}

## What to publish

Keep entries focused on what changed, who it affects, and where a reader should go next for more detail. Link to the deeper product, auth, API, legal, or tool doc when a short note would otherwise force readers to guess at the impact.

## Entry shape

Each changelog entry should include a clear date, a one-line summary, and a brief explanation of the user-facing effect. If a change is docs-only, say so. If a change affects live behavior, call out whether the change is already available or still rolling out.

## Cross-app rule

Use GitBook changelog entries for shared public-facing updates. Do not scatter the same release note across website, seller, facility, or markets help surfaces when the change is best explained once in docs.