NAME

repomatic sync-runner-images - Move runner images forward as GitHub retires and supersedes them

SYNOPSIS

repomatic sync-runner-images [OPTIONS]

DESCRIPTION

Move retiring runner images forward, and probe superseding ones.

Every label this repository runs is looked up in GitHub's available-images table. A **retirement** rewrites each literal `runs-on:` naming a deprecated image onto its successor, because those jobs carry an end date. An **upgrade** adds a strictly newer *version* to the full test matrix as a `continue-on-error` probe rather than migrating onto it: nothing is bet on it, but the suite starts exercising it at once, which surfaces a dependency breaking there while there is runway to report it upstream.

Strictly newer by version is what separates an upgrade from a flavour. A same-version variant carrying a different toolchain is not a newer image and is never proposed as one.

Merging is the decision; the CI run this triggers is the evidence for it. To decline a proposal for good, name the label in `[tool.repomatic.sync-runner-images] ignore`: closing the pull request alone brings it back on the next run.

OPTIONS

--dry-run / --live

Report the changes without writing them.

--output FILE

Write the proposal as a Markdown table to this file, for feeding a pull request body through `pr-sync --template-arg-file`.

--help / -h

Show this message and exit.

ENVIRONMENT

SYNC_RUNNER_IMAGES_DRY_RUN

Report the changes without writing them.

SYNC_RUNNER_IMAGES_OUTPUT

Write the proposal as a Markdown table to this file, for feeding a pull request body through `pr-sync --template-arg-file`.

SYNC_RUNNER_IMAGES__CLICK_DEFAULT_HELP

Show this message and exit.

EXIT STATUS

0

Success.

1

A runtime error, or an aborted prompt (Ctrl-C, a declined confirmation).

2

A usage error: unknown option, invalid value, missing operand, or an unparsable configuration file.

EXAMPLES

What would change, without touching the tree

repomatic sync\-runner\-images \-\-dry\-run

AUTHORS

Kevin Deldycke