Cycle releases
A fresh tree at the newest upstream stable tag, every 42 days. The mainline you probably want.
Download Cryolite
Plain versioned artifacts, straight from the promotion gate. Every bundle below was built from a pinned upstream stable tag, passed its gates, and landed in the dist tree unchanged.
—
42-day cadence from last promotion · security respins land any time they're needed
Release 140.9.1-gnu1 cycle release
Built from the pinned gnuzilla tag 140.9.1-gnu1 (Firefox ESR 140.9.1 with the GNU freedom layer): official release configuration, current patch layer applied, promoted after passing the smoke gate.
| File | What it is |
|---|---|
| SHA256SUMS | Checksums for everything in this directory - fetch this first |
| cryolite-140.9.1-gnu1.tar.xz.00.part | Bundle part 1 of 3 (24M chunks) |
| cryolite-140.9.1-gnu1.tar.xz.01.part | Bundle part 2 of 3 (24M chunks) |
| cryolite-140.9.1-gnu1.tar.xz.02.part | Bundle part 3 of 3 (24M chunks) |
All parts: .00.part .01.part .02.part … - grab every one, then rejoin with a single command (see verify section) | |
Inside the bundle: bin/, the application directory exactly as the build produced it — no installer, nothing written outside your chosen profile directory.
Verify & unpack
Download every part for your version into one directory, then:
$ sha256sum -c SHA256SUMS $ cat cryolite-140.9.1-gnu1.tar.xz.*.part > cryolite-140.9.1-gnu1.tar.xz $ mkdir -p ~/apps/cryolite $ tar xf cryolite-140.9.1-gnu1.tar.xz -C ~/apps/cryolite
A checksum you didn't check is decoration, not verification.
Release channels
Security respins
Unscheduled rebuilds when the weekly watcher catches an ESR fix newer than the pinned base. Same version family, patched base.
Both channel types land here under their exact upstream tag. Announcements go out on the main site's status page.
First run
Keep your profile far away from the extracted tree:
$ mkdir -p ~/.local/share/cryolite-profile
$ ~/apps/cryolite/bin/cryolite \
--profile=$HOME/.local/share/cryolite-profile
Full walkthrough, including upgrades and desktop launchers, lives in the install guide.
Older versions
Promoted artifacts are kept per version at /releases/<tag>/. The directory name is always exactly the upstream tag it was built from - no decoding required.