docs(ci): annotate base runner labels on all four workflows #27

Merged
Claude-Run merged 1 commit from docs/UMBRA-16-annotate-base-runner-labels into main 2026-08-08 00:56:15 +02:00
Member

Every runs-on in this repo requested RUNS_ON_OPENSUSE_BASE_LATEST with no rationale at the label, which makes a deliberate base label indistinguishable from an unaudited one. A fleet sweep read check.yml as a defect for exactly that reason: its rationale lived in the file header, 19 lines above runs-on.

Add a one-line # base label: comment directly above each of the four runs-on lines, in the style the sibling repos use. check.yml names the rust-builder-glibc job container as the source of the C toolchain, libudev and the eframe X11/Wayland/OpenGL/fontconfig libraries; the two build-binary workflows name docker buildx and their Dockerfiles; create-release.yml states that it compiles nothing. No runner label, container image tag, or build step changes.

#UMBRA-16

Every `runs-on` in this repo requested `RUNS_ON_OPENSUSE_BASE_LATEST` with no rationale at the label, which makes a deliberate base label indistinguishable from an unaudited one. A fleet sweep read `check.yml` as a defect for exactly that reason: its rationale lived in the file header, 19 lines above `runs-on`. Add a one-line `# base label:` comment directly above each of the four `runs-on` lines, in the style the sibling repos use. `check.yml` names the rust-builder-glibc job container as the source of the C toolchain, libudev and the eframe X11/Wayland/OpenGL/fontconfig libraries; the two build-binary workflows name `docker buildx` and their Dockerfiles; `create-release.yml` states that it compiles nothing. No runner label, container image tag, or build step changes. #UMBRA-16
docs(ci): annotate base runner labels on all four workflows
All checks were successful
Check / fmt + clippy + build + tests (pull_request) Successful in 49s
Create release / Create release from merged PR (pull_request) Has been skipped
de5d4ed9b4
Every `runs-on` in this repo requested `RUNS_ON_OPENSUSE_BASE_LATEST` with no rationale at the label, which makes a deliberate base label indistinguishable from an unaudited one. A fleet sweep read `check.yml` as a defect for exactly that reason: its rationale lived in the file header, 19 lines above `runs-on`.

Add a one-line `# base label:` comment directly above each of the four `runs-on` lines, in the style the sibling repos use. `check.yml` names the rust-builder-glibc job container as the source of the C toolchain, libudev and the eframe X11/Wayland/OpenGL/fontconfig libraries; the two build-binary workflows name `docker buildx` and their Dockerfiles; `create-release.yml` states that it compiles nothing. No runner label, container image tag, or build step changes.

#UMBRA-16
Claude-Run deleted branch docs/UMBRA-16-annotate-base-runner-labels 2026-08-08 00:56:15 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
pandoras-box/umbra!27
No description provided.