Canonical log
GitHub Releases
Ember's stable public release history lives on the repository releases page.
Changelog
Track real Ember releases without a fragile mirror.
Instead of duplicating or guessing release history inside the marketing site, this page points to the canonical GitHub Releases log and explains how Ember versions, installers, and update checks are delivered.
Stable strategy
One canonical release log, zero invented history.
GitHub Releases is the safest public place to read version notes and grab tagged installers.
Ember's latest-download flow resolves platform assets and SHA256 metadata from that same release source.
The result is a changelog page that stays accurate without a brittle runtime feed in the website itself.
Installer assets
Windows + macOS
Latest release delivery is mapped to a Windows setup executable and a macOS disk image.
Update checks
Background notifications
Installed builds check for updates in the background and notify users when a new version is available.
Integrity
SHA256 verification
Release metadata resolves a SHA256 digest before the latest installer is served.
Release source
Where Ember releases actually live.
The marketing site stays honest by linking to the public release ledger instead of recreating a version table that can drift.
Use the release source of truth
This page stays intentionally stable: for version-by-version notes, installer assets, and tags, GitHub Releases is the canonical public surface.
Platform-specific assets stay explicit
Backend download handling expects `Ember.dmg` for macOS and a versioned `Ember-Setup-<version>.exe` asset for Windows.
Installed apps can watch for new builds
Ember checks for updates in the background, then surfaces a newer version when one is available.
Open the log
Fast paths to the public release record.
Use these links when you want tagged builds, release notes, or repository context without depending on a website-side mirror.
Release trust
How delivery stays grounded and verifiable.
Release handling in the backend and app is explicit about asset names, digest checks, and version metadata.
Digest-first delivery
Latest-download metadata prefers GitHub asset digests and falls back to the historical `SHA256:` release-note format when needed.
License-aware access
The latest-download and update-check routes require a valid license key, while update checks themselves do not consume credits.
Version labels are build-injected
Packaged Ember builds use build-time release metadata, while development checkouts fall back to a `-dev` version suffix.
What users can expect
The app can notify users in the background when a newer version is available.
Installer delivery stays platform-aware with `.exe` builds for Windows and `.dmg` builds for macOS.
For the full version trail, tagged notes, and asset list, GitHub Releases remains the canonical destination.