Releases
What changed in each Roastwarden release. A release follows each round of work; the newest is first. Follow them with the feed.
-
Roastwarden 0.30.0
roastwarden.com now speaks to roasters: "Understand every roast. Build on every batch.", docs that open with what a roaster needs (the design notes stay in the repository), and an AI agent set up in three commands, roast login, roast skill install and roast status. On a phone the Roast page's chart is about three quarters wider.
-
Roastwarden 0.29.0
Roastwarden has a public site, roastwarden.com: a home page, the documentation with search, and every release with a feed, made from the repository's own docs at each release.
-
Roastwarden 0.28.0
Roastwarden has a mark of its own: Warden, a shield keeping the amber flame, on the top bar, the favicon, the installed app's icon, the reports and the share pages.
-
Roastwarden 0.27.2
On Beans, every button at the top now opens its form where you can see it.
-
Roastwarden 0.27.1
Two report pages get back the room they lost, and the README and user guide show the app: Roasters, Label Studio, a share page and Reports, from a copy of the owner's own data.
-
Roastwarden 0.27.0
The server's public address can be set in Settings → Roasting, so share pages, label QR codes and approval links point where others can open them. After the rename, the last backup names its file again, and a share link that is no longer active says so plainly. Checked live: a server outside the LAN imported a shared profile from production over the internet.
-
Roastwarden 0.26.0
Profiles can be shared: a public link shows a profile's curve, targets and events and offers it as a file, and another Roastwarden imports it from the link. The names from before the rename are gone from the wire (firmware must watch roastwarden/server/status, as the reference ESP32 firmware does from 3.7.0), and the owner's production moved to its new address.
-
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.
-
Roastwarden 0.24.0
Two things for people beyond the owner's own setup. Each roaster can now show up in Home Assistant as a device, read only: temperatures, RoR, heater, fan, the roast's phase and time, and the RoR warning, through the server's own broker or Home Assistant's, checked against Home Assistant itself. And a support bundle makes one file for a bug report, with every secret removed and no green coffee or receipts in it.
-
Roastwarden 0.23.0
The live prediction now warns before the RoR goes wrong late in a roast: a crash, a flick after first crack, or BT stalling short of DROP, from what this roaster's own model expects in the next two minutes and what the RoR shows now, each with its reason. Alarms can fire on them, and each roast's score says whether the warnings were right. Replayed on the owner's roasts it gave no false crash or stall, and foresaw the RoR's rise after first crack a minute ahead.
-
Roastwarden 0.22.0
rustRoast now installs as one container: the server can run its own MQTT broker, with the same locked-down rules as the Mosquitto it shipped with, so a Raspberry Pi needs nothing but Docker, and a new install guide walks a new owner through it. Tested on arm64. The install test also found two problems now fixed: a data folder the server cannot write stops it with the fix in the message instead of running on a database in memory, and the broker restarts cleanly.
-
Roastwarden 0.21.0
Orders now come into rustRoast from their receipts: an agent reads the supplier's confirmation email, the server checks that it adds up to the cent, is not there already and which of your beans each line is, and keeps the email with the order, privately. The coffee is on order until the box comes, and only then stock, priced with its share of shipping and tax. The shopping list turns into one cart link per supplier that opens its cart with your bags already in it; you check out there.
-
Roastwarden 0.20.1
Add from a link now says which bags a Shopify supplier has sold out (it never could: the page it read had no stock), and keeps each bag's shop id for the cart links to come. With it, the research on letting an agent shop for green coffee: cart links and orders from receipts are worth building, an agent-run store cart is not yet.
-
Roastwarden 0.20.0
Phidgets, the thermocouple boards most gas roasters log with in Artisan, now work in rustRoast: through Phidgets' own network server, with no Phidgets software in rustRoast itself. Artisan's 13 Phidgets machines (Diedrich, Mill City and others) set up the way Artisan has them, so 189 of its 264 machines now come across.
-
Roastwarden 0.19.0
For anyone coming from Artisan: keep Artisan as the screen while rustRoast runs the roaster. The server's Modbus slave serves the roaster to Artisan, and the server writes the Artisan setup file that reads it, checked against Artisan 4.2.0 itself. The slave is now read-only unless writes are switched on, and its writes go through the roaster's control gate and the audit log.
-
Roastwarden 0.18.0
For anyone who builds their own roaster: one guide to what rustRoast expects of a roaster and how to pick a transport, with four small working example roasters (an ESP32 on MQTT, a Modbus TCP register layout, the TC4 serial lines, a WebSocket server), each tested end to end. Adding a roaster that was already streaming now works from the command line, and a register of your own can have a scale.
-
Roastwarden 0.17.0
The Roasters section reworked for three users at once: a home roaster, a small shop and a builder of custom roasters. Add roaster is four steps (the roaster and its kind, how it connects, a live check, then control), one connection form serves the wizard and a roaster's page, and the roaster cards say at a glance which roasters are reading and ready.
-
Roastwarden 0.16.0
More of Artisan's machines are set up from its catalogue: 176 of 264 now (145 before). Fuji PID roasters, Arduino TC4 machines (Hottop, Kaleido), Probat and Prisma over Artisan's WebSocket, ROEST over MQTT, the Loring Smart Roast (BCD values) and Delta DTA/DTK lines (Modbus ASCII) come with their connection, mapping, commands, outputs and channels, starting at control off.
-
Roastwarden 0.15.1
A fix for the command that lists Artisan's machines.
-
Roastwarden 0.15.0
A roaster Artisan knows is now set up the way Artisan has it. rustRoast carries Artisan's own machine catalogue: name your machine (or give your .aset file) and its Modbus connection, BT and ET, burner, air and drum outputs and extra curves are filled in, starting at control off. A Modbus roaster may have several controllers on one RS-485 bus.
-
Roastwarden 0.9.0
Lean home, deep roastery (phase 3). A home install can hide what it doesn't use: six optional modules (reports, cupping, tuning, agents, costs, labels) behind three presets, and a new install asks once what kind of roasting it is for. Weights show in grams or ounces per browser. A roastery can record packed bags, whole bean or ground, straight from a label print, and trace any bag back to its green lot. Drum roasters get two seed profiles, an agent may ask to switch a roaster's control on (the owner approves), each roast keeps its own channels, and Matrix rooms of the newest room version are accepted. The owner's install looks as before: every module stays on.
-
Roastwarden 0.8.0
Other roasters, step three, which finishes "Any roaster" phase 2. A device can now keep its own field names, units (°F), MQTT topics and command syntax: the connection maps them, so nothing needs reflashing. A drum roaster's drum speed and damper are outputs like the heater and fan. Extra probes the owner declares (an exhaust, a third thermocouple, gas pressure) are kept with each roast, drawn, usable in alarms and exported to Artisan. An agent can add, map and check a new roaster (roast roaster add | map | check) without ever switching its control on. A simulated gas drum shows all of it working. The ESP32 works as before.
-
Roastwarden 0.7.0
Other roasters, step two: a roaster now declares its outputs (heater or burner, fan or air) with ranges and a fan floor, and its kind brings sensible defaults, so a drum no longer gets the fluid bed's CHARGE sequence or 45 % fan floor. Modbus RTU reaches PID controllers and commercial drums over RS-485, the TC4 reads stock aArtisan boards, and connections apply at once. The ESP32 works as before.
-
Roastwarden 0.6.0
The first step toward other roasters: each roaster now says what rustRoast may send it. A roaster added from now on only records until the owner switches its control on; the ESP32 and the virtual roaster keep full control and work as before.
-
Roastwarden 0.5.2
The overview docs catch up and stay caught up: README, CLAUDE.md, the dashboard's structure doc and the user guide describe rustRoast as it is now, and a check in CI fails when code gains a module, page, crate, setting or doc they do not mention.
-
Roastwarden 0.5.1
One fix: Settings → About names the release on a release's own build.
-
Roastwarden 0.5.0
Everything since v0.4.0 (2026-10-26): roasting itself, then the paperwork again. Autotune 2 (the server's relay test and PI designs) and the device contract with the gains held by the server; deploys that wait for the roaster and a drive that resumes after a restart; roast analysis in the server (roast review, roast compare); auto DROP by time, BT or development; the roaster's own thermal model and its live prediction; roasted coffee with its rest window; a new bean's first roast; the hardening of the release review. Then labels and reports polished from a review: label notes, quicker labels after a roast, a report comparing two roasts, smarter plan and profile reports, a layout check on every report.
-
Roastwarden 0.14.0
rustRoast now has a licence: the GNU AGPL, version 3 or later, the same as Artisan. Settings → About links it, the source code of the running version and the notices of every library and font inside. Release images also run on arm64 (a Raspberry Pi), and each release carries a compose bundle to install it with.
-
Roastwarden 0.13.0
After an emergency stop, the top bar's STOP turns into a Fan off button once the roaster has cooled, so quieting the fan is one tap instead of a trip to the Roast page's slider.
-
Roastwarden 0.12.0
A cleaner top bar: the red STOP button shows only while there is something to stop (a roast open, the heater on, the fan or drum running, hot beans) and stays out of the way on a cold, idle roaster.
-
Roastwarden 0.11.0
Safe to share, continued (phase 1). The dashboard signs in instead of keeping the owner key: each browser trades the key (or a token) once for a sign-in cookie it cannot read, and the owner sees and ends signed-in browsers. Reads need a sign-in unless an install opens them (the owner's does, behind Pocket ID), and the audit log is the owner's and admin tokens' only. The shipped MQTT broker no longer takes anonymous clients: the server and each roaster sign in, and a roaster may use only its own topics (the owner's ESP32 is on firmware 3.6.0, which does). The owner's homelab files moved to contrib/homelab/.
-
Roastwarden 0.10.0
Safe to share, first steps (phase 1). A fresh install no longer runs open: with no key set it makes its own owner key at first start, keeps it beside the database and logs it once, and wrong keys or tokens are rate limited. Writes that read first wait for the database instead of failing under load, the supplier pages in the tests are synthetic, and the deploy guide now says what secrets a backup holds. The owner's install, which sets its key, works as before.
-
Roastwarden 0.4.0
Everything since v0.3.0 (2026-10-25): the paperwork around a roast. An agent can do everything the app does (roast covers every API operation, checked by a test); bag labels with a label studio (saved Typst designs with versions, assets, brands, a layout check, printing over IPP and share links); cupping after the classic SCA form; nine PDF reports made with Typst (roast, cupping sheet, green inventory, shopping list, coffee, profile, period, purchases, roast-day plan).
-
Roastwarden 0.3.0
Everything since v0.2.0 (2026-10-23): rustRoast for daily use. Roast guidance reads each roast against its profile and references; green coffee with purchases, costs, supplier links and a shopping list; the roast sequence; nightly backups with a checked restore; tokens, approvals and an audit log; notifications to a phone; the roast command line and an agent skill; an OpenAPI document from the code; a user guide. Releases now carry roast for Linux x86_64 and aarch64.
-
Roastwarden 0.2.0
Everything since v0.1.0 (2026-03-02). rustRoast became a server-centric Artisan replacement: the server runs the roast (replay, alarms, fan assist, auto events) and any browser is a view.
-
Roastwarden 0.1.0
First tagged version: server, MQTT, dashboard with sessions, profiles, designer, transposer, cupping, comparison and exports.