v0.5.9
Released: 2026-04-28
UX release. Continuation of #11 — when discovery returns empty, the most common silent failure mode is another tool (nRF Connect for VS Code, JLink Commander, RTT Viewer) holding the probe. The “No J-Link devices found” message gave no hint that contention was a possibility.
- Common-causes hint when no probe is found — the empty-state error card now lists the three most likely reasons (no probe connected, another tool holding the probe, driver refresh needed) instead of the previous one-line message
- Contention hint in the device picker — the QuickPick empty state now suggests closing RTT/VCOM sessions in nRF Connect, JLink Commander, or RTT Viewer
Changed
Section titled “Changed”- Error-card detail supports multi-line text —
white-space: pre-lineon.error-card-detailso\ncharacters render as actual line breaks