chore(ci): run the compiling jobs on the dev runner label #480

Merged

Claude-Run merged 1 commit from chore/PMS-719-ci-dev-runner-label into main

2026-08-02 01:55:29 +02:00

Claude-Run commented

2026-08-02 01:46:22 +02:00

Member

check.yml and integration.yml compile Rust natively on the runner but requested RUNS_ON_OPENSUSE_BASE_LATEST, whose image ships no C toolchain, and worked around it with sudo zypper install gcc libopenssl-devel on every run. That is the workaround CLAUDE-203 rejected, and it followed two CI-failure issues in this repo (PMS-705, PMS-706). Both jobs now request RUNS_ON_OPENSUSE_DEV_LATEST and the install steps are gone: verified against ghcr.io/niceguyit/opensuse-dev (tags v1.7.0-leap-16.0 and latest-leap-16.0) that the image carries /usr/bin/cc, gcc and ld, glibc-devel, and libopenssl-devel with pkg-config reporting openssl 3.5.0, so nothing the removed packages provided is missing.

Every other runs-on is classified in a comment at the site: build-oci-image.yml and both create-release.yml jobs stay on base (docker buildx / nu / git, no native compile), and e2e.yml keeps the dev label deliberately for the pre-baked bun, node24 and Playwright browsers.

scripts/check-runner-labels.nu makes the rule mechanical: it fails when a workflow that runs cargo natively requests the base label, when any workflow installs a C toolchain at run time, or when a runs-on: carries no comment justifying its label. Wired into just check and check.yml.

#PMS-719

check.yml and integration.yml compile Rust natively on the runner but requested `RUNS_ON_OPENSUSE_BASE_LATEST`, whose image ships no C toolchain, and worked around it with `sudo zypper install gcc libopenssl-devel` on every run. That is the workaround CLAUDE-203 rejected, and it followed two CI-failure issues in this repo (PMS-705, PMS-706). Both jobs now request `RUNS_ON_OPENSUSE_DEV_LATEST` and the install steps are gone: verified against ghcr.io/niceguyit/opensuse-dev (tags v1.7.0-leap-16.0 and latest-leap-16.0) that the image carries /usr/bin/cc, gcc and ld, glibc-devel, and libopenssl-devel with pkg-config reporting openssl 3.5.0, so nothing the removed packages provided is missing. Every other `runs-on` is classified in a comment at the site: build-oci-image.yml and both create-release.yml jobs stay on base (docker buildx / nu / git, no native compile), and e2e.yml keeps the dev label deliberately for the pre-baked bun, node24 and Playwright browsers. scripts/check-runner-labels.nu makes the rule mechanical: it fails when a workflow that runs cargo natively requests the base label, when any workflow installs a C toolchain at run time, or when a `runs-on:` carries no comment justifying its label. Wired into `just check` and check.yml. #PMS-719

Claude-Run added 1 commit

2026-08-02 01:46:22 +02:00

chore(ci): run the compiling jobs on the dev runner label

E2E / Playwright against staging (pull_request) Successful in 3m25s

Details

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

Details

Integration / integration tests (pull_request) Successful in 8m29s

Details

Create release / Gate (release-branch merges only) (pull_request) Successful in 0s

Details

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

Details

b098f8254c

check.yml and integration.yml compile Rust natively on the runner but requested `RUNS_ON_OPENSUSE_BASE_LATEST`, whose image ships no C toolchain, and worked around it with `sudo zypper install gcc libopenssl-devel` on every run. That is the workaround CLAUDE-203 rejected, and it followed two CI-failure issues in this repo (PMS-705, PMS-706). Both jobs now request `RUNS_ON_OPENSUSE_DEV_LATEST` and the install steps are gone: verified against ghcr.io/niceguyit/opensuse-dev (tags v1.7.0-leap-16.0 and latest-leap-16.0) that the image carries /usr/bin/cc, gcc and ld, glibc-devel, and libopenssl-devel with pkg-config reporting openssl 3.5.0, so nothing the removed packages provided is missing.

Every other `runs-on` is classified in a comment at the site: build-oci-image.yml and both create-release.yml jobs stay on base (docker buildx / nu / git, no native compile), and e2e.yml keeps the dev label deliberately for the pre-baked bun, node24 and Playwright browsers.

scripts/check-runner-labels.nu makes the rule mechanical: it fails when a workflow that runs cargo natively requests the base label, when any workflow installs a C toolchain at run time, or when a `runs-on:` carries no comment justifying its label. Wired into `just check` and check.yml.

#PMS-719