Skip to content

v0.1.46

Choose a tag to compare

@github-actions github-actions released this 13 Nov 13:06
· 51 commits to main since this release
Immutable release. Only release title and notes can be modified.
v0.1.46
c61a20b

Adding a self-signed server now asks about its certificate only once, and the Overview shows dashes instead of zeros when it has no data. The 0.1.46 beta confirmed this on a real phone: the trust question appears once, the Overview shows dashes while offline, Uptime is a duration and disk rows have no dangling separator.

Fixed

  • The Overview shows a dash instead of zeros when it has no data — after the
    connection to your server dropped, the Array card read "0,0 / 0 TB used" with a
    half-filled bar, and CPU and Memory read "0,0%" and "0,0 GB". Values the app does
    not know now show a dash with an empty bar, like the Network and Temperature
    cards, and the graphs no longer draw zeros for them. A value your server really
    reports as zero is still shown as zero. For a few seconds after the connection
    drops the last values stay on screen on purpose: the app waits for a few failed
    polls before it calls the server offline (#303).
  • Uptime on the Overview shows how long the server has been running — the
    System card showed a raw timestamp such as "2026-11-12T13:56:22.425Z", which is
    when the server started. It now shows the time since then, for example
    "22h 4m" or "3d 4h", and a dash when the server sends nothing readable (#304).
  • Disk rows on the Array tab no longer end in a lonely "·" — a row showed
    "sdb ·" when the server sends no model for the disk. The second line now
    lists only what is known ("sdb") and is left out when nothing is (#305).
  • A new self-signed server asks you to trust its certificate only once —
    when you added a server with "Trust self-signed certificate", confirmed the
    certificate during Test and then saved, the same "Trust this certificate?"
    dialog appeared a second time on the main screen. The certificate you accept
    is now stored together with the server, so it is already trusted when the
    server first connects. A certificate that later changes still asks (#292).

What's Changed

  • fix: ask to trust the certificate of a new server only once by @nofuturekid in #298
  • ci: harden the build gate (dispatch check name, merge-base diff, lint and release checks) by @nofuturekid in #297
  • fix: placeholders when offline, readable uptime, no dangling separator in disk rows by @nofuturekid in #308
  • ci: release only pull-request-green commits, changelog section required, publish draft-first by @nofuturekid in #309
  • release: v0.1.46-beta1 — certificate trust asked once, Overview placeholders offline by @nofuturekid in #310
  • release: 0.1.46 — certificate trust asked once, Overview placeholders offline (Stable) by @nofuturekid in #311

Full Changelog: v0.1.45...v0.1.46