Releases ·
Roastwarden 0.25.0
rustRoast is now Roastwarden (roastwarden.com): coffee roaster control, written in Rust. The rename goes all the way, from the dashboard and docs to the crates, the image, the variables and the names a roaster sees, so the interface standard is public with its final names. An install made as rustRoast upgrades in place: old variable names still work, the database and backups are renamed at start, label designs and browsers carry over, and older roaster firmware keeps its fail-safe for this release.
Changed
- rustRoast is now Roastwarden (Next 72, owner 2026-11-02; roastwarden.com). Every name
moves: the dashboard, the docs, the crates (
roastwarden-core,-mqtt,-autotune,-server), the server binaryroastwarden-server, the imageroastwarden, the repository, the environment variables (ROASTWARDEN_*), the Agent Skill (roastwarden), the database fileroastwarden.dband its backupsroastwarden-<time>.db, the label helpersroastwarden.typ, the report data schemasroastwarden.report.*, the metricsroastwarden_*, the server's MQTT user, the server's presence topicroastwarden/server/status, the mDNS service_roastwarden._tcpand Home Assistant's ids and bridge topic. TheroastCLI and the roasters' own topics (roaster/<id>/…) keep their names. - An install made as rustRoast upgrades in place (Running it, "Upgrading from
rustRoast"):
RUSTROAST_*variables are still read, with a warning naming them; the server renamesrustroast.db(and its-wal,-shm) and everyrustroast-<time>.dbbackup at its first start; migration 057 points saved label designs atroastwarden.typ; the dashboard moves its stored key and preferences to the new names, so nobody signs in again. For one release the server also announces itself onrustroast/server/status(with its own last will) and browses_rustroast._tcp, so firmware older than ESP32 3.7.0 keeps its fail-safe until it is flashed; both go in the next release. Home Assistant, if it was on, finds the roasters as new devices: delete the old ones.