Journey log
Journey log is the project logbook for Sendspin Bluetooth Bridge.
This section captures the narrative behind CHANGELOG.md entries:
- stable / RC / beta rollout notes
- release-engineering changes such as GitHub Releases, add-on packaging, and channel publishing
- architecture and deployment pivots
- important fixes discovered in real Home Assistant, Docker, and LXC installs
- short summaries of what changed, why it mattered, and how it rolled out
If you want the latest status first, start with the newest entry below.
Entries
Section titled “Entries”- 2026-04-06 — Idle mode, Docker diet, and unified branding (v2.55.0)
- 2026-04-04 — v2.54.0 stable, mute desync, and Raspberry Pi
- 2026-04-02 — The idle standby saga and SinkMonitor
- 2026-03-31 — Stats dashboard, Russian landing, and v3 roadmap
- 2026-03-30 — Landing page, auto-translation, and v2.52.0
- 2026-03-29 — Bug report proxy, Docker Compose fix, and v2.51.0 stable
- 2026-03-28 — Mobile UI overhaul, diagnostics redesign, and v2.51.0
- 2026-03-26 — NumPy CPU crash, documentation audit, and v2.50.0
- 2026-03-25 — Native transport and null-sink standby
- 2026-03-24 — Security audit and IPC hardening
- 2026-03-23 — Room metadata and HA area integration
- 2026-03-22 — Scan modal redesign and guidance refinements
- 2026-03-20 — Orchestrator extraction and onboarding guidance
- 2026-03-19 — 2.40.6 release wave, UI polish, and roadmap realignment
- 2026-03-18 — Stable 2.40.5: manual ports, prerelease channels, and HA fixes
- 2026-03-17 — CI convergence and release completion
- 2026-03-16 — MA playback parity and runtime hardening
- 2026-03-14 — UI system consolidation
- 2026-03-12 — Observability, UX polish, and security hardening
- 2026-03-07 — Reliability, multi-bridge, and HA OAuth
- 2026-03-02 — Architectural overhaul and v2 foundation
- January – March 1 — Origins and v1 feature explosion
What belongs here
Section titled “What belongs here”Use the Journey log when a release changes how the project ships, is operated, or is explained.
Keep evergreen setup/config/API/architecture reference material in the main docs, and keep concise user-facing release bullets in CHANGELOG.md.