Releases and changes
The changelog lives outside the documentation, and why there is only one of it. Also how a product version relates to a documentation version.
The changelog is at Releases, not here.
There is deliberately one of it. A documentation page describing "what changed" beside a changelog doing the same thing becomes two records that drift apart, and the one people end up reading is the one nobody updated.
What each release entry carries
| Field | What it says |
|---|---|
| Version | Calendar versioning, YYYY-MM. It names the month the content closed — not an installation date and not the date you received it |
| Channel | Feature, security or maintenance. A security release carries its own badge in the list, so "must I install this" is answerable at a glance |
| Highlights | The two or three lines a reader takes away without opening anything |
| Areas | The parts of the product that changed |
Following it without visiting the site
There is an Atom and an RSS feed per language, at /en/atom.xml and /en/rss.xml. They carry articles, guides and releases — not the glossary, because a definition is not news.
A documentation version is not a product version
A documentation URL carries the documentation version inside it: /docs/v1/…. The marker in the sidebar says which product versions this documentation describes.
There is no latest address, and that is a decision: an unversioned alias is exactly what makes a bookmark rot quietly — the page keeps loading and starts describing a different product with no warning. A new documentation version gets its own path segment, and the existing addresses go on describing what they always described.
Updated
This page is the file content/docs/en/v1/reference/changelog.mdx