From ce05db76c4ad3dfc8631c8ec2d779039043e123a Mon Sep 17 00:00:00 2001 From: AstroHan Date: Wed, 2 Sep 2026 01:05:01 +0800 Subject: [PATCH] ci: pin the model metadata upkeep runner #4460 added this lane and #4483 banned `ubuntu-latest`, 35 minutes apart. Both were green when they ran; main is red now that they sit together, which blocks every merge because `test` is the only required context. One-line fix, and exactly the drift the rule exists to catch: `ubuntu-latest` is what every tutorial writes, so it comes back one new workflow at a time. The rule caught it on the first one. Refs #4480 --- .github/workflows/model-metadata-upkeep.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/model-metadata-upkeep.yml b/.github/workflows/model-metadata-upkeep.yml index 07016276d0..804ae06203 100644 --- a/.github/workflows/model-metadata-upkeep.yml +++ b/.github/workflows/model-metadata-upkeep.yml @@ -38,7 +38,7 @@ jobs: # A fork inherits the schedule but owns neither the branch this pushes nor # the pull request it opens. if: github.repository == 'apache/maka' - runs-on: ubuntu-latest + runs-on: ubuntu-24.04 timeout-minutes: 30 permissions: contents: write