archetech / archon / 33197357270

87%

push

github

ci: Allow publishing a past ref with the current matrix (#958)

A tag-triggered run uses the workflow file as it existed at that tag, so
v0.12.0 cannot be completed by re-running it -- the file at that tag
carries the old six-image matrix. Deleting and re-pushing the tag has the
same problem, and changes what the tag means.

The combination needed is the current workflow file against older source,
and dispatch is the only way to get it: the file comes from the branch
dispatched on, the source from the ref asked for. The build job's
checkout now honours that ref; the generate job's does not need to, since
it reads no source.

  ref      what to build, defaulting to the dispatching ref
  version  what to tag it
  channel  latest or pre-release

All twenty-six Dockerfiles and scripts/prefetch-prebuilds.mjs exist at
v0.12.0, so the twenty-seven-image matrix builds against it unchanged.

Rebuilding a released version does not reproduce its bits. The source is
the same, but the Debian and Node base images have moved since, so an
image published this way is that version's source built today. Worth
knowing before overwriting a tag that already exists.

3881 of 4464 branches covered (86.94%)

Branch coverage included in aggregate %.

8527 of 8952 relevant lines covered (95.25%)

717.63 hits per line