Repository navigation
kuma v45.0.0
- The base moves to Fedora 45.
DEFAULT_BASEisquay.io/fedora/fedora-bootc:45and the ISO build container isfedora:45— the next composed image is F45 root to toe (kernel 7.2, systemd 262, dnf5 5.4.6, podman 6), everything layered on top baked fresh as always. The seed rides the GA digest (sha256:8076cf4f…, the 2026-10-31 release compose; the tag is frozen until base-images grows its 45 renovate lane), and the compose env's rpm-ostree 2026.3 knows F45's relocated repo configs (/usr/share/dnf5/repos.d). The greeter PAM stacks moved from/etc/pam.dto/usr/lib/pam.dand the keyring assert follows (8906e62); the oo7 secrets change is met by staying on gnome-keyring for now — the adopt lane and its preconditions are the research notes' subject, not this release's. The one F45 name change in the package set (mesa-va-driversfolded intomesa-dri-drivers) is handled by the mesa block's own version guard, which only ever installs the freeworld side. Research trail:notes/45.0.0-*.md.
Static x86_64 binary, no runtime dependencies.
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.0.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/kumaThe 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.0.0/kuma-nostrd-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.0.0/kuma-nostr-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.0.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-relayVerify 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-muslThe 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.0.0/cosign.pub
$ cosign verify --key cosign.pub ghcr.io/letdown2491/kuma:niri-45.0.0The 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 505fc5d896c309213037ae0c21047e609143793c.
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