HotLoop Cascade 0.1.2 release notes

What this is

0.1.2 is a build fix and nothing else. The code is the same as 0.1.1, and so is everything you run: the chart, the Quadlet units, the settings, the database.

I run a Podman Quadlet house, and the workflows that test and publish Cascade still reached for a Docker engine to start the test services, to log in to the registry and to load the image into k3s. They run on Podman the whole way through now, and the test scripts no longer offer Docker as a switch. The image was already built with Podman. It still is, one platform at a time now, and the release reads the manifest list back and refuses to push unless it holds exactly amd64 and arm64.

Upgrading from 0.1.1

Nothing to do. helm upgrade to 0.1.2, or let :stable roll the Quadlet units. No migrations, no new settings, and the key and your workflows stay where they were.

What isn’t proven

The workflows on a real GitHub runner. I ran the workflow’s own steps under Podman 4.9.3, the version the runner ships, on a box cut down to two CPUs, 7 GB of RAM and a runner-sized disk, with k3s fighting a pack of busy loops for the same two cores. The registry in that run was a local one with a login. The tag run is the first time ghcr.io sees any of it.