9b41d51231
Some checks are pending
Auto-update PR branches / Update open PR branches (push) Waiting to run
CI / Frontend Static Quality Checks (push) Waiting to run
CI / Frontend Tests & Coverage (push) Waiting to run
CI / Rust Tests & Quality Checks (push) Waiting to run
CI / Linux build verification (push) Waiting to run
Deploy docs / Build VitePress site (push) Waiting to run
Deploy docs / Deploy to GitHub Pages (push) Blocked by required conditions
Release (Alpha) / Compute alpha version (push) Waiting to run
Release (Alpha) / Build release artifacts (push) Blocked by required conditions
Release (Alpha) / GitHub Release (alpha) (push) Blocked by required conditions
Release (Alpha) / Update docs and release pages (push) Blocked by required conditions
Source snapshot: 514ab1975951d94342ea38e64101d5a0f1c51c77
37 lines
803 B
Markdown
37 lines
803 B
Markdown
# 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:
|
|
|
|
```txt
|
|
/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:
|
|
|
|
```txt
|
|
/alpha/latest.json
|
|
```
|
|
|
|
Compatibility endpoints also point to the alpha metadata:
|
|
|
|
```txt
|
|
/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.
|