Skip to content

kuma v45.0.1

Choose a tag to compare

@github-actions github-actions released this 07 Nov 15:30
· 85 commits to main since this release
  • kuma upgrade no longer refuses a moved declaration — the delta lane always has a path. The diff baseline was the release's baked example, so any machine whose declaration ever named a custom hostname, keymap, or [user] account diverged forever and was refused at every crossing (#65). The baseline is now the booted image's baked declaration — what the machine's last build actually honored — so a stable declaration diffs clean and compiles as the small delta it is. And when the diff carries fields a delta cannot take (a keymap moved since the last build, a changed account), the verb no longer dead-ends: it compiles the FULL declaration FROM the release digest it already pulled — the whole compiler, so hostname, the initramfs half of the keymap, and the account all ride — while the release's own binaries, version label, and branding stand. A 44.x binary can build this fallback (no compose env involved), which is the road a 44.15.2 point release gives every existing machine.
  • kuma upgrade --check tells a delta machine the truth. The delta lane's check compared the booted digest against the release tag's — and a delta machine boots its own build, whose digest can never equal the release's, so every machine that ever upgraded through the delta lane was reported a step behind the release it was current with (#67). The comparison reads the lock's release story now (what the last upgrade compiled against); a machine with no record gets an honest "cannot tell" and keeps the action, and the fetch lane keeps the booted compare — it boots the release itself.
  • A no-op upgrade is a success. A rebuild that reproduces the image the machine already runs — same declaration, same release, podman's layer cache — stages nothing, and the verb ended that in Error: nothing staged with exit 1: an error for the system being correct (#68). The no-op is confirmed against the digest bootc itself compares, read out of root's store (the user's store answers a different manifest digest for the same image — the save/load sync re-serializes the manifest), reported as already-current, exit 0. The unexplainable refusal stays an error.
  • The machine runs what it runs. update --check and update read the Fedora release from the running system's os-release, not the lock's base image — a delta upgrade boots the release's Fedora while the lock's base half keeps the last full build's story, so a machine booting 45 was told it runs 44 and an update announced a release move that already happened (#69). The full compile inside kuma upgrade also re-bases the lock's base story onto the release image it actually FROM'd, so the next git diff kuma.lock and the next update both read the build story straight.
  • The smoke's upgrade failures dump the store that failed. The delta and fallback builds run in the guest; the runner-side dump read a store that never saw a layer of the build. The failure branches ask the guest's root store now (images, disk, df) while the machine is still up (#66), and the delta lap proves the new contracts where they live: the post-upgrade check says current, the repeat upgrade stages the pure delta path, the no-op upgrade exits zero, and the fallback's full compile re-bases the lock.

Static x86_64 binary, no runtime dependencies.

$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.0.1/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.0.1/kuma-nostrd-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.0.1/kuma-nostr-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.0.1/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.0.1/cosign.pub
$ cosign verify --key cosign.pub ghcr.io/letdown2491/kuma:niri-45.0.1

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 a1ec13a492e879f48d2d6b9c77092e5ff5c80af7.

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