Files
computer-playbook/scripts/meta/resolve
kevinveenbirkenbachandClaude Opus 5.5 d412b23409 fix(ci): stop the release backfill below the oldest buildable tag
The release backfill dispatches the highest version tag whose images are
missing. Every tag from v15.0.0 down to v9.0.2 has its images now, so since
2026-10-05 it picks v9.0.1 every day, and each of the nine runs failed in
"Build missing CI images / Image" at
`entry.sh: line 19: infinito: command not found`. The v9.0.1 tree cannot
build its own image; c680be12ea fixed that build in v9.0.2, and a tag cannot
take the fix.

highest_release_tag.sh now stops at v9.0.2: no tag below it is picked, so the
backfill reports nothing missing instead of retrying v9.0.1. v9.0.0 has the
same Dockerfile, Makefile and scripts/docker as v9.0.1.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-14 01:32:05 +02:00
..
…

Resolve Scripts

This directory contains scripts that resolve metadata and derived values used by the project.

  • 🧩 Derive runtime values from repository and workflow context
  • 🔍 Resolve identifiers, references, and computed inputs
  • 🗂️ Keep lookup and resolution logic grouped in one place

Examples in this folder and its subfolders:

  • baseline_remote.sh resolves the remote whose main CI diffs against
  • repository/name.sh resolves the concrete repository name once for callers
  • repository/owner.sh resolves the concrete repository owner once for callers
  • See pr/README.md for the Pull Request-specific resolvers.

The scope of this folder is value resolution. Build, release, and wait-oriented behavior should stay in their dedicated script directories.