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 binary roastwarden-server, the image roastwarden, the repository, the environment variables (ROASTWARDEN_*), the Agent Skill (roastwarden), the database file roastwarden.db and its backups roastwarden-<time>.db, the label helpers roastwarden.typ, the report data schemas roastwarden.report.*, the metrics roastwarden_*, the server's MQTT user, the server's presence topic roastwarden/server/status, the mDNS service _roastwarden._tcp and Home Assistant's ids and bridge topic. The roast CLI 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 renames rustroast.db (and its -wal, -shm) and every rustroast-<time>.db backup at its first start; migration 057 points saved label designs at roastwarden.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 on rustroast/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.