flintstackbuild-cache daemon · a hosted project
Project status: activeLicense: Apache-2.0Latest: 0.11.3 (2026-09-28)releases feed

Flintstack › Changelog

Changelog

Thirteen releases from May 2024 to September 2026, newest first - one store-format break and no others.

Dates are release dates. Each version links to its own notes. «Store format» lines matter for rollback: the format has changed exactly once, at 0.7.0, and the upgrade notes say what that means. The same history is available as data - releases.json - and as an Atom feed.

0.11.3 fix 2026-09-28
Three fixes, no new surface. The one worth noting is the clock-offset report in doctor. 3 changes →
0.11.0 2026-06-02
The peer backend lands: a second daemon as a cache tier, with optional mutual TLS. 3 changes →
0.10.4 fix 2026-03-17
Credential hygiene is now enforced at startup rather than trusted. 2 changes →
0.10.0 2026-01-21
Configurable compression and a far faster index rebuild. The 0.6 reader is gone. 3 changes →
0.9.1 fix 2025-10-08
A FreeBSD target joins the matrix and the 0.9.0 tail-latency regression is closed. 2 changes →
0.8.0 2025-07-15
Hash the compiler itself, and attribute hits to parts of a build. 2 changes →
0.7.0 breaking 2025-04-24
The one store-format break in the project's history. The index database is gone. 3 changes →
0.6.2 fix 2025-02-19
The last release that still carried the index database. 1 change →
0.5.0 2024-12-11
The first remote tier: object storage over signed HTTPS. 2 changes →
0.4.0 2024-10-09
Eviction gets hysteresis after a report of it running for a full day. 2 changes →
0.3.1 2024-08-21
The daemon arrives and the single-process lock contention goes away. 2 changes →
0.2.0 2024-07-02
An environment allowlist and path normalization make entries reusable under CI. 2 changes →
0.1.0 2024-05-16
First tag, four weeks after the work started. 1 change →

Thirteen releases over 2026–2024 is slow on purpose: a cache that changes its key or its store format churns everyone's disk, so both move rarely and loudly. The next planned work is a read-through cap for the objs tier, and it will not touch the store format.

Last updated: 2026-09-28