Release notes
What changed, and whether you care.
One sentence per release, written for somebody who runs a shop rather than somebody who reads changelogs. If a release does not affect you, it says so.
[DATE]
[VERSION] — [WHAT CHANGED, IN ONE PHRASE]
[One sentence a customer would care about.]
Checksums: macOS [CHECKSUM] · Windows [CHECKSUM]
[DATE]
[VERSION] — [WHAT CHANGED, IN ONE PHRASE]
[One sentence a customer would care about.]
Checksums: macOS [CHECKSUM] · Windows [CHECKSUM]
[DATE]
[VERSION] — [WHAT CHANGED, IN ONE PHRASE]
[One sentence a customer would care about.]
Checksums: macOS [CHECKSUM] · Windows [CHECKSUM]
[RELEASE ENTRIES] Date, version, one phrase, one sentence. Never “various fixes and improvements” — if there is nothing worth a sentence, there is nothing worth a release note, and the entry can say “maintenance only, nothing you need to do”.
How the app finds out
This is how it will work, and it does not work yet. The desktop app will check a static file on this site about once a week and tell you when there is something newer than the version your licence entitles you to. It will never install anything on its own, and it will never ask the network for permission to run — the check is a courtesy, not a gate. Until it ships, this page is the way to find out, and the app will not mention it at all.
[updates.json] Not shipped yet, on purpose. Publishing a live feed of invented versions at the URL a future client will poll is a worse failure than having no feed. It lands with CLOUD K11.4, against the schema already documented.