Release history
| Version | Date | What shipped |
|---|---|---|
| v0.14.4 | 2026-07-31 | 52 unit tests for story.rs and anonymize.rs; CLAUDE.md hardware-and-timing invariants refresh; ROADMAP v0.3.0 historical audit; CI workflow fix for missing Tauri Linux deps. |
| v0.14.3 | 2026-07-30 | Decoder catalog expansion + community data (testplans, opinions, freeze schemas); protocol helpers and a new Tauri command. |
| v0.14.2 | 2026-07-29 | Live Data on the Bench: replay logged data against the simulator for development and regression testing; CI workflow fix. |
| v0.14.1 | 2026-07-27 | Tauri 2 webview flakiness fix (#161). Improves connection stability on repeated connect/disconnect cycles. |
| v0.14.0 | 2026-07-25 | The big 0.14.x cycle: redesigned diagnostic-story generator with anonymisation, snapshot export; landing site reach expansion (DTC index, per-engine profiles, service resets). |
| v0.13.0 | 2026-07-22 | Per-target KWP2000 response deadlines (1 s default, 3 s slow) that scale with the FTDI VCP latency timer; Tester-Present keep-alive implemented. |
| v0.12.0 | 2026-07-21 | Diagnostic-story generator v2; DTC history record; community TOML knowledge base initial seeds. |
| v0.11.0 | 2026-07-20 | Walkthrough bundle: structured diagnostic walkthroughs exportable as JSON for sharing. |
| v0.10.0 | 2026-07-19 | Charge-pipe profile (N55); data-export improvements. |
| v0.9.0 | 2026-07-18 | Testplan loader; community testplans/ seeded with 11 entries. |
| v0.6.0 | 2026-07-16 | OBD-II PID scan; log-diff functionality; fuel-trim N55; knock-severity polish. |
| v0.5.0 | 2026-07-15 | First fuel-trim implementation on the N55. |
| v0.4.0 | 2026-07-15 | CBS reset multi-module; histograms; first community TOML knowledge base. |
| v0.3.0 | 2026-07-11 | Community intelligence: hunt the bytes, surface patterns, tell the story. DTC history harness initial. |
| v0.2.0 | 2026-07-06 | The big community-data release: ~150 DTC fault texts (was 7). Covers misfire, fuel, VANOS, DPF, EGR. Public DTC API initial. |
Release cadence
Beemuu ships roughly every 1–2 weeks. The cadence is set by the maintainers’ available time, not by an external schedule. Every release is a short cycle (3–5 PRs) with a clear plan doc.
Versions follow semver: breaking changes bump the minor (0.X.0), bug fixes bump the patch (0.14.X). The v0.14.x line has been the most active; the next minor bump (0.15.0) is gated on a real-car validation report landing in docs/validation/.
Patterns over time
Three themes run through the Beemuu release history:
- Community knowledge accumulation.
From v0.2.0 (150 DTC fault texts) through v0.9.0 (11 testplans), v0.14.0 (engine profiles + service resets), and v0.14.4 (the opinion/testplan/freeze/oracle catalog), the community contribution pipeline has been the headline work of every cycle.
- Protocol and transport hardening.
v0.7.0 (ENET discovery), v0.13.0 (KWP deadlines), v0.14.3 (UDS helpers and the new Tauri command) — the protocol layer gets attention every cycle, even when the public-visible work is elsewhere.
- Diagnostic story & anonymisation.
v0.8.0 (async commands), v0.12.0 (story generator v2), v0.14.0 (anonymisation), v0.14.4 (52 tests for both) — the project’s story generator is the user-facing surface for sharing diagnostic data; the test coverage in v0.14.4 made it production-ready.