ci: run Check on the dev runner label #461

Merged

Claude-Run merged 1 commit from chore/MAPPS-398-check-dev-runner-label into main

2026-08-02 01:20:14 +02:00

Claude-Run commented

2026-08-02 01:16:11 +02:00

Member

The Check job compiles Rust on the runner (fmt, clippy, a wasm-target check, and a host-target cargo test --lib that links), but requested RUNS_ON_OPENSUSE_BASE_LATEST, whose image ships no C toolchain. It papered over that by installing gcc with zypper on every run. Switch the job to RUNS_ON_OPENSUSE_DEV_LATEST, whose image carries cc/gcc/ld, and delete the install step and its comment.

Classify the remaining runs-on entries with an inline annotation each: build-oci-image.yml and create-release.yml legitimately stay on the base label (all compilation happens inside buildx containers; the release job only runs git log plus a Forgejo API call), and claude-fix.yml uses the container docker runner rather than an openSUSE image label.

Add scripts/check-runner-labels.sh, wired into just check and into check.yml itself, so the dev label and the absence of run-time package installs are enforced mechanically rather than by convention.

#MAPPS-398

The Check job compiles Rust on the runner (fmt, clippy, a wasm-target check, and a host-target `cargo test --lib` that links), but requested `RUNS_ON_OPENSUSE_BASE_LATEST`, whose image ships no C toolchain. It papered over that by installing gcc with zypper on every run. Switch the job to `RUNS_ON_OPENSUSE_DEV_LATEST`, whose image carries cc/gcc/ld, and delete the install step and its comment. Classify the remaining `runs-on` entries with an inline annotation each: `build-oci-image.yml` and `create-release.yml` legitimately stay on the base label (all compilation happens inside buildx containers; the release job only runs git log plus a Forgejo API call), and `claude-fix.yml` uses the container `docker` runner rather than an openSUSE image label. Add `scripts/check-runner-labels.sh`, wired into `just check` and into check.yml itself, so the dev label and the absence of run-time package installs are enforced mechanically rather than by convention. #MAPPS-398

Claude-Run added 1 commit

2026-08-02 01:16:11 +02:00

ci: run Check on the dev runner label

Check / fmt + clippy + tests (pull_request) Successful in 3m51s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

bb77a2c7f0

The Check job compiles Rust on the runner (fmt, clippy, a wasm-target check, and a host-target `cargo test --lib` that links), but requested `RUNS_ON_OPENSUSE_BASE_LATEST`, whose image ships no C toolchain. It papered over that by installing gcc with zypper on every run. Switch the job to `RUNS_ON_OPENSUSE_DEV_LATEST`, whose image carries cc/gcc/ld, and delete the install step and its comment.

Classify the remaining `runs-on` entries with an inline annotation each: `build-oci-image.yml` and `create-release.yml` legitimately stay on the base label (all compilation happens inside buildx containers; the release job only runs git log plus a Forgejo API call), and `claude-fix.yml` uses the container `docker` runner rather than an openSUSE image label.

Add `scripts/check-runner-labels.sh`, wired into `just check` and into check.yml itself, so the dev label and the absence of run-time package installs are enforced mechanically rather than by convention.

#MAPPS-398