v0.14.5 — Open & committed.

What shipped

The v0.14.5 cycle, closed end-to-end on 2026-08-02 with the four PRs below. The cycle name "Open & Committed" matched the public commitment set when the cycle was opened.

• PR #222 — docs(v0.14.5): cycle plan + ROADMAP header + CHANGELOG entry (Tier A). The new docs/v0.14.5_plan.md (287 LOC) + the v0.14.5 cycle block in ROADMAP.md + the ## [0.14.5] — 2026-08-02 section in CHANGELOG.md. Docs-only.
• PR #223 — feat(v0.14.5): n52 + n54 — swap local:10 oil for obd:5C + add 3 fuel-rate / runtime PIDs (Tier A). Mirrors the v0.14.2 N62 slice 1 (PR #175) + v0.14.3 N62 slice 2 (PR #186). N52: 10 → 13 params. N54: 12 → 15 params. Each new entry carries the [needs verification, N5x/E9x bench] marker.
• PR #224 — docs(v0.14.5): n5x-real-car.md harness doc — E9x N52 / N54 family (Tier A). 450-line harness doc mirroring the v0.14.2 N62 harness (docs/validation/n62-real-car.md). The N52 BSD oil-condition sensor note is the load-bearing difference from N62.
• PR #225 — release(v0.14.5): version surface bump + CHANGELOG date + cycle plan refresh (Tier C). Version bumps 0.14.4 → 0.14.5 in package.json + Cargo.toml + tauri.conf.json + Cargo.lock; README release badge v0.14.4 → v0.14.5; CHANGELOG date stamps. Merged 2026-08-02T07:37:08Z on origin/main @ 5743348. Tag v0.14.5 at 9249b934.

Open questions

The [needs verification, N5x/E9x bench] markers on the four new OBD-II PIDs (0x5C / 0x5E / 0x5F / 0x62) are retired only when a real-car report lands via docs/validation/n5x-real-car.md. The harness doc is the report-back loop.

For the maintainer:

1. When does v0.14.6 start?

   When the v0.14.5 release cut landed on 2026-08-02. v0.14.6 ("Forward Roadmap Audit") is the doc-rotation close-of-cycle, opening with the docs/v0.14.6_plan.md PR.

2. What happens to the v0.14.5 N5x harness reports?

   The [needs verification, N5x/E9x bench] markers stay on the four new PIDs until an E9x owner runs the harness doc and files a [verified YYYY-MM-DD on chassis XYZ] PR. The next-cycle v0.14.6 audit doesn't retire the markers — only a real-car report does.

Install v0.14.5

The v0.14.5 release ships both Windows installers. Pick the one that matches your workflow:

• NSIS installer (recommended for most users) — BeeEmUu_0.14.5_x64-setup.exe (3.5 MB)
• MSI installer — BeeEmUu_0.14.5_x64_en-US.msi (5.0 MB)

Both attach to the v0.14.5 release page. Verify the SHA-256 of either installer against the hashes published on the release page before installing (per the verification how-to).

 • Modifying vehicle electronics carries inherent risks. Always use a battery maintainer before flashing or deep coding.

Contribute

If you have a slice in mind, open a PR against main on the Beemuu repo. The maintainers will either merge it directly (Tier A) or roll it into the next cycle's plan doc.

FAQ