Skip to content

👾 Open Computer Use – Open-Source Alternative to Codex Computer Use

Use macos-26 for npm release workflow

Leo9da222312811
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index efe7196..4add4d0 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -24,7 +24,7 @@ permissions:
jobs:
package-npm:
- runs-on: macos-14
+ runs-on: macos-26
steps:
- name: Check out repository
diff --git a/docs/histories/2026-04/20260417-2214-enable-tag-release-and-bump-to-0.1.5.md b/docs/histories/2026-04/20260417-2214-enable-tag-release-and-bump-to-0.1.5.md
index 40858bc..2a6587b 100644
--- a/docs/histories/2026-04/20260417-2214-enable-tag-release-and-bump-to-0.1.5.md
+++ b/docs/histories/2026-04/20260417-2214-enable-tag-release-and-bump-to-0.1.5.md
@@ -16,6 +16,7 @@
- **保留 Trusted Publishing**:发布步骤继续走 GitHub Actions OIDC,不依赖长期 npm token。
- **版本 bump**:将插件 manifest、MCP server、自测和 CLI 文档中的版本统一更新到 `0.1.5`。
- **同步文档**:把 README 和 CI/CD 文档明确改成“打 git tag 自动发 npm”的用法。
+- **修正 GitHub runner**:把 release workflow 从 `macos-14` 调整到 `macos-26`,避免 GitHub Hosted Runner 默认 Xcode 15.4 / Swift 5.10 无法构建 `swift-tools-version: 6.2` 包。
### 🧠 Design Intent (Why)
既然 npm 侧已经配置了 Trusted Publishing,最自然的 release 路径就是“commit -> tag -> GitHub Actions 自动发”。这样发布动作能绑定到一个明确的 Git tag,也更符合 npm 包版本和 Git 版本一一对应的维护习惯。