Skip to content

kuma v45.4.0

Latest

Choose a tag to compare

@github-actions github-actions released this 14 Nov 05:45
· 1 commit to main since this release
  • The shell rides with its battery notifier. The kumaui pin moves to v0.9.0, the release that grows threshold battery notifications into kuma-shell itself: low at 15%, critical at 5%, warned once per band through the shell's own notification road, re-armed by any non-Discharging status.

  • The image's battery-watch script retires. The shell's notifier is the superset of what /usr/libexec/kuma-battery-watch did, so the script, its niri spawn line, and its 300-second monitor leave the image: one battery state announced by two programs in two styles was the shape the blueman retirement exists to undo. Every login stops respawning a second watcher that says what the shell already says. (#80)

  • The image's git speaks nostr://. The nostr git transport rides in every image now: ngit and its git-remote-nostr launcher, baked from the pinned upstream release (v3.0.5, verbatim musl archive — the emoji-font precedent), verified by hash at build and gated on their own --version before the layer can claim it shipped. git clone nostr://… works on a fresh machine. The doctor reads the pair's versions back rather than trusting the layer's presence: an image that predates the transport grades a warn whose fix is kuma update, instead of git dying later in its own bare transport error. (#79)

  • Doctor grades the wire under the signer. The 45.2.1 lesson's read side, closed: the vault line now grades the conjunction — an open vault answering over no connected relay is a warn that names the dead wire, not an Ok that vouches for it; the local relay's unit gets a liveness check when the declaration arms it (a relay that cannot stay up was silent while every other grade read green); and a unit stuck activating is called a crash loop, with the journal as the fix, instead of being told to start. The dev road stopped swallowing its own failures in the same breath: a bounce that fails is noted loudly at both call sites (the install print says the daemon is pointed at the staged binary — what a swallowed restart actually achieved), an adopt that finds a session bus missing bails instead of staging silently, and the dev override is audited — its ExecStart arguments drift when the image's unit moves, and the audit's fix is re-running kuma dev install. (#77)

  • The fallback lap's ceiling fits its work. The upgrade-fallback job's in-guest fallback compile measured 117–120 minutes against a 150-minute job ceiling that one runner shutdown and one unfinished lap proved was runner-weather roulette: the ceiling is 180 now. (#81)

  • Battery-watch stopped polling. The low/critical notifier woke the machine every 60 seconds — 1,440 wakeups a day on every machine, battery or none — to read two sysfs files. It now watches udev's power_supply events, with a five-minute safety read behind them: the first real battery announced the plug and stayed silent through a whole band of draining, so the monitor's own five-minute lifespan is the floor the threshold can never slip past. A desktop's watch now costs ~288 cheap reads a day instead of 1,440 timer wakeups; a laptop's notice is never more than one cadence behind. The first read on start means a boot at 12% on battery warns immediately. The old poll survives as the fallback for a machine without udevadm. The real-battery proof (discharge past both thresholds, replug, re-warn) is #80's remaining half — nothing in a VM ever discharges.

Static x86_64 binary, no runtime dependencies.

$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.4.0/kuma-x86_64-unknown-linux-musl
$ chmod +x kuma-x86_64-unknown-linux-musl && sudo mv kuma-x86_64-unknown-linux-musl /usr/local/bin/kuma

The image build stages the layer's three binaries from beside
the running kuma on every compose, nostr or not, so they
install to the same place:

$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.4.0/kuma-nostrd-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.4.0/kuma-nostr-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.4.0/nip46-relay-x86_64-unknown-linux-musl
$ chmod +x kuma-nostrd-x86_64-unknown-linux-musl kuma-nostr-x86_64-unknown-linux-musl nip46-relay-x86_64-unknown-linux-musl
$ sudo mv kuma-nostrd-x86_64-unknown-linux-musl /usr/local/bin/kuma-nostrd
$ sudo mv kuma-nostr-x86_64-unknown-linux-musl /usr/local/bin/kuma-nostr
$ sudo mv nip46-relay-x86_64-unknown-linux-musl /usr/local/bin/nip46-relay

Verify it came from this workflow:

$ cosign verify-blob \
    --bundle kuma-x86_64-unknown-linux-musl.bundle \
    --certificate-identity-regexp '^https://github.com/Letdown2491/kumaOS/.+@refs/tags/' \
    --certificate-oidc-issuer https://token.actions.githubusercontent.com \
    kuma-x86_64-unknown-linux-musl

The image this release publishes verifies with the committed
public key — the same key every kuma machine's own policy
enforces on update:

$ curl -sSLO https://github.com/Letdown2491/kumaOS/raw/v45.4.0/cosign.pub
$ cosign verify --key cosign.pub ghcr.io/letdown2491/kuma:niri-45.4.0

The moving tag is the convenience and the digest is the proof;
the verify response prints the digest it checked, and the same
command against that digest pins the bytes:

$ cosign verify --key cosign.pub ghcr.io/letdown2491/kuma@sha256:<digest the verify above printed>

Built from 3a1c09454a74f976763bca53e25f9eff2e9328d5.

The installer media on this page verifies the same way:

$ cosign verify-blob \
    --bundle kuma-x86_64.iso.bundle \
    --certificate-identity-regexp '^https://github.com/Letdown2491/kumaOS/.+@refs/tags/' \
    --certificate-oidc-issuer https://token.actions.githubusercontent.com \
    kuma-x86_64.iso