8739805f99
Some checks failed
Auto-update PR branches / Update open PR branches (push) Has been cancelled
CI / Frontend Static Quality Checks (push) Has been cancelled
CI / Frontend Tests & Coverage (push) Has been cancelled
CI / Rust Tests & Quality Checks (push) Has been cancelled
CI / Linux build verification (push) Has been cancelled
Release (Alpha) / Compute alpha version (push) Has been cancelled
Release (Alpha) / Build release artifacts (push) Has been cancelled
Release (Alpha) / GitHub Release (alpha) (push) Has been cancelled
Release (Alpha) / Update docs and release pages (push) Has been cancelled
Deploy docs / Build VitePress site (push) Has been cancelled
Deploy docs / Deploy to GitHub Pages (push) Has been cancelled
803 B
803 B
Release Channels
Tolaria publishes Stable and Alpha release metadata to GitHub Pages.
Stable
Stable follows manually promoted releases. This is the right channel for normal use.
The stable updater metadata lives at:
/stable/latest.json
The public download page points at the latest stable release.
Alpha
Alpha follows pushes to main. It receives fixes and features earlier, but it can be rougher than Stable.
The alpha updater metadata lives at:
/alpha/latest.json
Compatibility endpoints also point to the alpha metadata:
/latest.json
/latest-canary.json
Before Switching
Commit or push important vault changes before changing release channel or installing an update. Your notes are local files, but a clean Git state makes recovery simpler.