From 2fa9b8a3e7891e95c56ea5d74227222739de579c Mon Sep 17 00:00:00 2001 From: Ralf Anton Beier Date: Sun, 3 May 2026 21:02:08 +0200 Subject: [PATCH] ci: canary - migrate verify-rules to smithy now that Bazel is host-installed Smithy main commit c5d4794 added bazelisk + buildifier + OpenJDK 21 to the host. This is the validation canary for that change: pick the smallest Bazel-using job in any pulseengine repo and flip its runs-on to smithy. verify-rules is just two bazel query calls. No compile, no Lean toolchain download. bazelbuild/setup-bazelisk@v3 stays in the workflow; it is a no-op when bazel is already on PATH. If this lands green, it unblocks ~30 hosted jobs across rules_*, wasm-component-examples, moonbit_checksum_updater, and loom's rocq-proofs. Phase C of the Bazel rollout. --- .github/workflows/ci.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 108aa78..f36408c 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -9,7 +9,7 @@ on: jobs: verify-rules: name: Verify rules load - runs-on: ubuntu-latest + runs-on: [self-hosted, linux, x64, light] steps: - uses: actions/checkout@v4 - uses: bazelbuild/setup-bazelisk@v3