Files
computer-playbook/scripts/meta/resolve
kevinveenbirkenbachandClaude Opus 5 ac28c0b378 fix(ci): keep the backfill floor on the path the architecture gate takes
The main merge joined two correct rules into one broken script. The
architecture gate republishes the highest version when :latest misses an
architecture, because the published install instructions pull the image
untagged and only a release of that version rewrites latest. The backfill
floor refuses any tag below v9.0.2, which cannot build from its own tree.

The gate returned before the floor was ever consulted, so an incomplete
:latest would have asked the backfill for a tag it cannot build. Both
paths now ask below_floor, which also replaces the comparison the loop
carried inline.

The picker's own test could not have caught it: its docker stub answers
tags without emitting a manifest, and architectures.sh reads an empty
manifest as every architecture missing, so the gate fired on every case
and printed the newest tag. The stub now serves the whole pool, which is
the state the floor cases assume anyway.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-10-14 14:33:45 +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.