mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 04:06:42 +00:00
kevinveenbirkenbachandClaude Opus 5
964f3255f5
Every check asked `docker manifest inspect` whether a tag resolved. A tag serving only amd64 answers yes, so the arm64 half of the pool could be absent from `latest` while the release, the CI-image wait and the cron picker all reported the images present. `architectures.sh` answers the narrower question instead: given a reference, which architectures must it serve that it does not. It subtracts the manifest index's platforms from `resolve_architectures()`, so the pool stays declared in one place and an absent tag and a single-architecture tag give the same answer to every caller. `highest_release_tag.sh` checks `latest` before it walks the version tags. The published install instructions name the image without a tag, so a reader pulls `latest`, and only a release of the highest version republishes it: an architecture missing from `latest` is therefore reported as that version missing. Older tags stay an existence check, because their source predates the architecture and no rebuild for it is available. The CI-image wait is handed the run's own architecture list, the same expression the build matrix and the manifest step already read, so it cannot demand more than the run produced. The two release workflows pass no list and therefore require the whole pool, which is what drives the rebuild. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Script Collection
This directory contains automation scripts used across the project.
-
system/ contains host and system-facing helpers.
-
container/ contains helpers that run inside the local container.
-
github/ contains GitHub workflow helper scripts.
-
For the canonical Make target index, see make.md.
-
🛠️ Organize operational helpers for development, CI, release, and maintenance
-
🧭 Separate responsibilities into focused subdirectories with clear scope
-
📚 Keep script-based workflows discoverable and easier to navigate
The scope of this folder is script organization at the repository level. Detailed responsibilities belong in the README files of the respective subdirectories.