Version 0.1.0

Added a page of its own for every version, at /updates/<version>.

Every version's every line used to be open on one page, which made the log hard to scan and impossible to link to. The list now shows three lines per version, and the version itself opens a page holding the full entry grouped by category — so a support answer can point at the exact release that fixed something.

Added the instant each version went live — UTC to the second, with your device's local time beside it.

The log carried a date, not a time, so three versions that shipped on 5 August could not be told apart — and that date was typed by whoever wrote the entry rather than taken from the deploy. The deploy script now writes the instant into the entry as it ships it. The four releases up to 0.0.4 predate the mechanism and carry the time of the commit that set the version, which is under a minute from the real deploy.

Added marks for what kind of release it was: initial release, hotfix, or alpha.

A hotfix is a release that went to everyone without being an alpha first. The alpha channel is not built yet, so every release so far carries the mark — that is the accurate answer, not a placeholder, and it will stop being universal on its own once previews exist. The mark is worked out from the list of releases rather than set by hand, so it cannot go stale.

Rewrote every entry in one voice, under the five categories a changelog conventionally uses.

0.0.1 listed features, while 0.0.3 and 0.0.4 narrated them, so the log read as though several people wrote it. Every line now states what was done and is filed under added, changed, fixed, removed or security — the categories nearly every published changelog uses. The word rules that keep it that way are checked by the build.

Changed the rule to one version number per deploy, with the number decided by what changed.

Until now a number went up when it felt like enough had accumulated, which is why three versions carry the same date. A release that adds, removes or changes behaviour moves the middle number (0.1.0); one that only puts right what was already meant to work moves the last (0.0.5). The build reads the categories in the entry and fails if the number moved the wrong way.