From 943337fc94583fa1edfbe21f01324c3e0817b307 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tar=C4=B1k=20=C4=B0smet=20ALKAN?=
 <267584739+tialkan@users.noreply.github.com>
Date: Sat, 26 Sep 2026 19:50:12 +0300
Subject: [PATCH] ci: use ubuntu-latest for meta jobs instead of org-scoped
 Warp runner label

The runners/record-frozen-commit jobs ran on runs-on: ubuntu-slim, a
custom Warp runner image scoped to the upstream bitcoin/bitcoin org.
This fork has no access to that runner group, so GitHub failed the
whole workflow before scheduling any job (0 jobs, conclusion failure,
"workflow file issue" - e.g. run 33050282126 on dogmode/tx-weight-3900k).

Both jobs only run shell steps, so a standard GitHub-hosted
ubuntu-latest works regardless of provider.
---
 .github/workflows/ci.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 4d3a1b02bf3e..b0093d17161d 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -30,7 +30,7 @@ defaults:
 jobs:
   runners:
     name: '[meta] determine runners'
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-latest
     outputs:
       provider: ${{ steps.runners.outputs.provider }}
     steps:
@@ -318,7 +318,7 @@ jobs:
     # Record frozen commit, so that the native tests on cross-builds can run on
     # the exact same commit id of the build.
     name: '[meta] record frozen commit'
-    runs-on: ubuntu-slim
+    runs-on: ubuntu-latest
     outputs:
       commit: ${{ steps.record-commit.outputs.commit }}
     steps: