Reference pages are information-oriented: the facts, laid out for looking
up. One page per component, mirroring templates/<name>.yml 1:1. If you
want a guided lesson instead, see Tutorials; for a
task-oriented recipe, see How-To Guides; for the why
behind a design, see Explanation.
Which pipelines each component runs on:
the trigger matrix for all 40 components (merge request, branch, default
branch, tag, schedule), which triggers you can override, and why a
component that appears to have been ignored usually produced no job at
all.
Limitations: what these components deliberately
do not do: unsupported platforms and clouds, combinations that do not
work, and the things you have to supply yourself.
On a tag pipeline, decides whether the release can retag the image the default branch already built, and triggers the child pipeline named for the answer.
Scans a built image with trivy, OS packages as a hard gate and tool binaries as advisory, and keeps one dashboard issue per image current with the findings.
Runs a project's own documentation check on every merge request. Deliberately always-on: a docs gate filtered on docs paths skips the merge requests that break the docs.
The composable preset library: a base plus ecosystem and role leaves you combine to describe a project. Change policy in one file and it applies fleet-wide.
Derives the estate's first-party dependency order from its go.mod files and plans (or walks) the release cascade in it, the sequencing Renovate structurally cannot do.
The release orchestrator this estate owns: proposes a release MR, confirms what actually landed, and tags that commit. The estate moved to it from releaser-pleaser under spec 0078.
On a schedule, checks that every release binary on the estate's object store is still there and still matches its published digest, and files an issue where it is not.