Skip to content

fix(release): gate the release runner behind OAC_USE_GITHUB_RUNNERS - #14

Merged
sunyalou merged 1 commit into
mainfrom
fix/oac14-release-runner
Oct 3, 2026
Merged

sunyalou merged 1 commit into
mainfrom
fix/oac14-release-runner

Conversation

@sunyalou

@sunyalou sunyalou commented Oct 3, 2026

Copy link
Copy Markdown
Owner

目标

fork 上 core-release 无法运行:.github/workflows/release.yml 的 build job runs-on 硬编码为 blacksmith-4vcpu-ubuntu-2204,而 fork 没有 Blacksmith runner,release 会在排队阶段失败。全仓其余 workflow 都已用 vars.OAC_USE_GITHUB_RUNNERS 门控,release.yml 是唯一例外。

改动

.github/workflows/release.yml 的 build job:

-    runs-on: blacksmith-4vcpu-ubuntu-2204
+    runs-on: ${{ vars.OAC_USE_GITHUB_RUNNERS == 'true' && 'ubuntu-22.04' || 'blacksmith-4vcpu-ubuntu-2204' }}

与 check.yml / website.yml / native.yml 的写法一致:上游保留 Blacksmith,fork(OAC_USE_GITHUB_RUNNERS=true)落到 GitHub-hosted ubuntu-22.04(公开仓库 4 vCPU,对应原 4vcpu Blacksmith)。

验证

  • actionlint 1.7.12(与 CI actionlint.yml 同版本):全部 workflow 通过,exit 0。
  • make check-ci:46 tests OK。
  • make check-names:通过。

已知限制

release.yml was the only workflow with a hardcoded Blacksmith runner
(blacksmith-4vcpu-ubuntu-2204), so a fork without Blacksmith would queue
and fail. Gate it the same way as the other workflows so a fork with
OAC_USE_GITHUB_RUNNERS=true builds the release on GitHub-hosted
ubuntu-22.04, while upstream keeps Blacksmith.

Co-authored-by: multica-agent <github@multica.ai>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@sunyalou
sunyalou merged commit 5423a68 into main Oct 3, 2026
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant