The changelog is no longer one long list. Every release has a permanent page you can link to, share and keep.
Why a list was not enough
A changelog you can only read in place is a changelog you cannot send to anyone. Every entry now has its own address — a permanent link that keeps working when the next release lands underneath it. That link is shareable: it carries its own title, its own description, its own canonical URL and its own social card, so it looks right when it is pasted into a chat, a community post or a commit message.
What a release page carries
The publication date, the categories, a summary, the highlights, the full notes and the links that go with the release. The notes have their own table of contents, so a long entry can be read in pieces or linked to by section. Each page has a copy button for its own address.
Only what has shipped
A release becomes public when it is published, and until then it does not exist as far as the outside world is concerned. Drafts and unreleased entries are answered with a 404 rather than a forbidden sign — the public API cannot be asked whether a draft exists. They stay out of the sitemap, out of the social preview, and out of anything a search engine indexes. The releases that predate this change were given pages too, so every entry in the list can be linked directly.