/
/
/
There are no releases here, so hand-maintained version numbers only drifted from what was actually built - the table packages said 0.1.0 while Harbor held 0.3.0. CI now tags by commit SHA plus latest, and deploys follow latest. One dnd_image_tag drives every component, so setting it to the parent repository's SHA reverts the whole system together: that repository's pin workflow re-tags each component's already-built image with a single tag. dnd-runner is renamed dnd-tabletop-server. The old name collided with both the Forgejo runners and the runner host itself, and said nothing about what the image does. Images move to the public 'docker' Harbor project, since the source repos are going public and images referenced from a public README have to be pullable. Also registers QEMU binfmt handlers on the host for arm64 cross-builds. The Forgejo runners mount the host docker socket rather than running their own daemon, so this is host state - putting it in the runner image would register handlers in a namespace no build uses. A systemd unit re-runs it at boot, because binfmt is kernel state and a reboot would otherwise leave arm64 builds silently producing amd64 images.