Pacenote v0.5.3

The upgrade quits the running app first and reopens it, once. Config and run history are untouched.

After you upgrade

• With the built-in sandbox set up by 0.5.2, Settings > Sandbox says "Update needed" and the status bar shows a check issue, as 0.5.2's images do not say which recipe built them. Pace keeps answering with them meanwhile. Run "Set up built-in sandbox" once: the kernel is already there, so it only builds the images again, in a few minutes. The reasoner image then has codex 0.162.1.

Images that need an update

• Each image keeps the hash of the recipe it was built from: its script, the files of sandbox/vm it installs, the versions it pins and its settings. When a newer Pacenote changes a recipe, Settings > Sandbox says "Update needed", the image's line says it was built for another version, and the status bar's check issue names the images.
• Those images still run until the setup builds them again, and the setup builds only those: an image that is current is left as it is.
• The diagram renderer's image counts only with diagrams on, and the broker's only with ops tools on. Settings shows the broker's image beside the others.

The Linux kernel

• The first setup downloads the kernel, about 14 MB, from ghcr.io/ashon/pacenote-kernel by its pinned hash. It used to download Kata's release archive, about 290 MB, to keep 14 MB of it.
• When ghcr.io cannot give it, the setup takes it from that archive as before, checked against the archive's hash and then the kernel's.

Also

• pacenote-vm build --label KEY=VALUE keeps labels with an image, and pacenote-vm status reports them.