👾 Open Computer Use – Open-Source Alternative to Codex Computer Use
Swift accessibilityai-agentai-agentsclaude-codecodexcodex-computer-usecomputer-usecomputer-use-agentcross-platformcuadesktop-automationgemini-cligui-automationmacosmcpmodel-context-protocolopen-computer-useopen-computer-use-mcpopenai-codexopencode
ci(release): 强制使用审核版英文发布说明
tisfeng2069f9e149fc
diff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex 4c8f97e..2b7ed72 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -23,7 +23,26 @@ permissions:id-token: writejobs:+ release-metadata:+ runs-on: ubuntu-24.04++ steps:+ - name: Check out repository+ uses: actions/checkout@93cb6efe18208431cddfb8368fd83d5badbf9bfd++ - name: Set up Node.js+ uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e+ with:+ node-version: "24"++ - name: Validate reviewed GitHub Release notes+ if: ${{ github.event_name == 'push' }}+ env:+ RELEASE_TAG: ${{ github.ref_name }}+ run: node ./scripts/validate-github-release-notes.mjs --tag "${RELEASE_TAG}"+package-npm:+ needs: release-metadataruns-on: macos-26steps:@@ -127,6 +146,7 @@ jobs:--tag "${NPM_DIST_TAG}"release-cursor-motion-dmg:+ needs: release-metadataif: ${{ github.event_name == 'push' }}runs-on: macos-26@@ -230,11 +250,15 @@ jobs:run: |version="${RELEASE_TAG#v}"dmg_path="dist/release/cursor-motion/CursorMotion-${version}.dmg"+ notes_path="docs/releases/github/${RELEASE_TAG}.md"if gh release view "${RELEASE_TAG}" >/dev/null 2>&1; thengh release upload "${RELEASE_TAG}" "${dmg_path}" --clobber+ gh release edit "${RELEASE_TAG}" \+ --title "${RELEASE_TAG}" \+ --notes-file "${notes_path}"elsegh release create "${RELEASE_TAG}" "${dmg_path}" \--title "${RELEASE_TAG}" \- --generate-notes+ --notes-file "${notes_path}"fidiff --git a/docs/histories/2026-07/20260730-1637-enforce-english-github-release-notes.md b/docs/histories/2026-07/20260730-1637-enforce-english-github-release-notes.mdnew file mode 100644index 0000000..c02a143--- /dev/null+++ b/docs/histories/2026-07/20260730-1637-enforce-english-github-release-notes.md@@ -0,0 +1,35 @@+## [2026-07-30 16:37] | Task: Enforce reviewed English GitHub Release notes++### Execution Context+* **Agent ID**: `Codex`+* **Base Model**: `GPT-5`+* **Runtime**: `Codex desktop`++### User Query+> 将近期 GitHub Release 更新日志统一为英文,并让后续 workflow 从审核过的英文 notes 文件发布。++### Changes Overview+**Scope:** GitHub Release metadata, validation, workflow gating, and release documentation.++**Key Actions:**+- Added reviewed English GitHub Release notes for `v0.2.0`, `v0.2.1`, `v0.3.0`, and `v0.3.1`, plus a reusable template.+- Added a fail-closed Node validator for tag/version consistency, one to three user-visible changes, CJK exclusion, and the required Full Changelog link.+- Added a `release-metadata` workflow job that must pass before npm packaging or Cursor Motion DMG publication starts.+- Replaced generated notes with `--notes-file` for both release creation and idempotent release updates.++### Design Intent+GitHub generated notes copy merged pull request titles without translation, so Chinese PR titles produced mixed-language public release history. Checked-in English notes make release text reviewable and reproducible, while the pre-publication gate prevents npm or DMG publication from starting when release metadata is missing or inconsistent.++### Files Modified+- `.github/workflows/release.yml`+- `package.json`+- `scripts/validate-github-release-notes.mjs`+- `scripts/check-docs.sh`+- `docs/releases/README.md`+- `docs/releases/RELEASE_GUIDE.md`+- `docs/releases/github/TEMPLATE.md`+- `docs/releases/github/v0.2.0.md`+- `docs/releases/github/v0.2.1.md`+- `docs/releases/github/v0.3.0.md`+- `docs/releases/github/v0.3.1.md`+- `docs/histories/2026-07/20260730-1637-enforce-english-github-release-notes.md`diff --git a/docs/releases/README.md b/docs/releases/README.mdindex 7794755..b23a196 100644--- a/docs/releases/README.md+++ b/docs/releases/README.md@@ -2,6 +2,8 @@`feature-release-notes.md` 用来记录对用户可感知的新功能、体验优化和重要修复。+`github/vX.Y.Z.md` 是 GitHub Release 的审核版英文正文。每次公开发版必须从 `github/TEMPLATE.md` 新建目标 tag 对应文件,并在打 tag 前运行 release notes 校验。+如果任务是“准备发版 / bump 版本 / 打 tag / 查 release 失败”,先读 `RELEASE_GUIDE.md`。## 规则@@ -10,6 +12,7 @@- 同一个月份里,最新内容插在最上面- 先写用户价值,再写变更摘要- 不要把纯内部重构和实现噪音塞进来+- GitHub Release 正文默认使用审核过的英文,不直接使用 PR 标题自动生成## 建议的列diff --git a/docs/releases/RELEASE_GUIDE.md b/docs/releases/RELEASE_GUIDE.mdindex 3c562b7..b16ec45 100644--- a/docs/releases/RELEASE_GUIDE.md+++ b/docs/releases/RELEASE_GUIDE.md@@ -25,13 +25,15 @@- 本地 publish:`node ./scripts/npm/publish-packages.mjs`- CI workflow:`.github/workflows/release.yml`- 用户可见发布记录:`docs/releases/feature-release-notes.md`-- GitHub Release 页面:workflow 在 release 不存在时用 `gh release create --generate-notes` 创建,并交给 GitHub 自动生成 `What's Changed` / `New Contributors` / `Full Changelog`。+- GitHub Release 正文:`docs/releases/github/vX.Y.Z.md`+- GitHub Release 页面:workflow 使用审核过的英文 notes 文件创建或更新,不直接引用 PR 标题自动生成正文。## 当前版本源-这个仓库当前有两类 release 版本源:+这个仓库当前有三类 release 版本源:- npm staging 包版本:以 `plugins/open-computer-use/.codex-plugin/plugin.json` 里的 `version` 为准。+- GitHub Release 正文:以 `docs/releases/github/<tag>.md` 为准,文件名必须与实际 tag 完全一致。- `CursorMotion-<version>.dmg` 文件名与 GitHub Release asset 版本:以 release tag 为准;workflow 会把 `vX.Y.Z` 规范化成 `X.Y.Z` 写进 DMG 文件名,也可以在本地显式传 `--version`。也就是说:@@ -39,6 +41,7 @@- 只改 git tag,不改这个 manifest,不会得到新 npm 版本。- `scripts/npm/build-packages.mjs` 会从这个 manifest 读取版本,再生成三个 root/alias staging 包;每个包内置 macOS、Linux 和 Windows runtime artifacts。- 所以 release 前必须先把这份 manifest bump 到目标版本。+- 如果缺少目标 tag 对应的英文 notes,或者 notes 与 manifest/tag 不一致,`release-metadata` job 会在 npm 与 DMG job 启动前失败。- 如果要让 `CursorMotion` 的 DMG 文件名和 release 页面资产名正确落到目标版本,也必须使用目标 tag 推送,或本地显式传入同样的 `--version`。## Release Checklist@@ -56,15 +59,34 @@- `scripts/computer-use-cli/main.go`- `scripts/computer-use-cli/README.md`- `docs/releases/feature-release-notes.md`+- `docs/releases/github/vX.Y.Z.md`- `docs/histories/` 中本轮 release 对应的 history如果这轮 release 还改了其他对外暴露版本字符串,也要一起对齐,不要只改一半。-### 2. 本地验证版本源已经生效+### 2. 准备并验证 GitHub Release notes-至少跑这三步:+从 `docs/releases/github/TEMPLATE.md` 创建目标 tag 对应文件,并运行:```bash+node ./scripts/validate-github-release-notes.mjs --tag v0.1.14+```++校验要求:++- tag 必须是 `vX.Y.Z` 或 `X.Y.Z`,并与 plugin manifest 版本一致。+- 正文以 `## What's Changed` 开头,包含 1-3 条用户可感知的英文变化。+- 正文不能包含 CJK 字符。+- 正文必须且只能包含一个指向当前 tag 的 `Full Changelog` 链接。++任何一项不满足都不要打 tag。tag push 后,`release-metadata` job 会再次执行相同校验,并在失败时阻止 npm 与 DMG job 启动。++### 3. 本地验证版本源已经生效++至少跑这四步:++```bash+node ./scripts/validate-github-release-notes.mjs --tag v0.1.14swift testnode ./scripts/npm/build-packages.mjs --out-dir dist/release/npm-staging-check./scripts/build-cursor-motion-dmg.sh --configuration release --arch universal --version 0.1.14@@ -86,12 +108,12 @@ ls dist/release/cursor-motion/CursorMotion-0.1.14.dmg如果当前 checkout 里已经有和目标版本一致的 `dist/Open Computer Use.app`,也可以临时加 `--skip-build` 跳过重复构建;但在干净 checkout 里不要默认加这个参数,否则 staging 脚本会因为缺少 `dist/Open Computer Use.app` 而失败。-### 3. 提交版本 bump+### 4. 提交版本 bump- 用单独 commit 提交 release version bump。- commit message 要能直接看出这是 release 收口,而不是普通功能提交。-### 4. 打 tag 并推送+### 5. 打 tag 并推送当前约定用 `vX.Y.Z`:@@ -106,7 +128,7 @@ tag push 后,`.github/workflows/release.yml` 会自动做两件事:- 发布 npm 包。- 构建 `CursorMotion-0.1.14.dmg`,并创建或更新同名 tag 的 GitHub Release asset。-### 5. 检查 GitHub Release notes+### 6. 检查 GitHub Release notes每次 tag push 后都要检查 GitHub Release 页面,不要只确认 workflow 绿了:@@ -114,14 +136,13 @@ tag push 后,`.github/workflows/release.yml` 会自动做两件事:gh release view v0.1.14 --json body,url```-当前 workflow 已经在新建 release 时使用 `--generate-notes`,所以如果两次 tag 之间有 merged PR,GitHub 会自动生成 `What's Changed` 和 `New Contributors`。如果这段区间只有 direct commits,自动 notes 可能只剩 `Full Changelog`,这时 release agent 必须根据 `docs/releases/feature-release-notes.md`、`git log <previous-tag>..vX.Y.Z --oneline` 和本轮 history 手动补一段简短的 `What's Changed`,再用 `gh release edit` 更新正文。+workflow 会使用 `docs/releases/github/<tag>.md` 创建新 Release;如果 Release 已经存在,则在覆盖上传 DMG 后用同一文件更新正文。GitHub 自动生成 notes 不再是正文来源,因此 PR 标题使用中文也不会改变公开 Release 的语言。最低要求:-- release body 不能只有 `Full Changelog`。-- `What's Changed` 至少列出本次用户可感知的 1-3 个变化。+- release body 必须与仓库里的目标 notes 文件一致。+- `What's Changed` 必须列出本次用户可感知的 1-3 个英文变化。- 保留 `Full Changelog` 链接。-- 如果 GitHub 自动生成了 `New Contributors`,保留它;不要为了统一格式删掉。## Release 失败时怎么查@@ -134,6 +155,9 @@ gh run view -R iFurySt/open-codex-computer-use <run-id> --log-failed### 2. 重点看哪一类错误+- `release-metadata` 失败+ - 先本地运行 `node ./scripts/validate-github-release-notes.mjs --tag <tag>`。+ - 检查 `docs/releases/github/<tag>.md` 是否存在、manifest 版本是否匹配、正文是否包含 CJK,以及 Full Changelog 是否指向当前 tag。- `npm error 403 ... You cannot publish over the previously published versions`- 通常不是 token 权限问题,而是 staging 包版本仍然是旧版本。- 先回头检查 `plugin.json` 的 `version`,再检查 staging 包实际产出的 `package.json`。@@ -180,6 +204,7 @@ git push origin :refs/tags/v0.1.14每次 release 都至少同步这三类文档:- `docs/releases/feature-release-notes.md`+- `docs/releases/github/vX.Y.Z.md`- `docs/histories/` 对应 release history- 如果 release 流程本身有变化,这份 `docs/releases/RELEASE_GUIDE.md`diff --git a/docs/releases/github/TEMPLATE.md b/docs/releases/github/TEMPLATE.mdnew file mode 100644index 0000000..a7308fd--- /dev/null+++ b/docs/releases/github/TEMPLATE.md@@ -0,0 +1,5 @@+## What's Changed++* Describe one user-visible change in reviewed English. Link the related pull request when one exists.++**Full Changelog**: https://github.com/iFurySt/open-codex-computer-use/compare/vPREVIOUS...vNEXTdiff --git a/docs/releases/github/v0.2.0.md b/docs/releases/github/v0.2.0.mdnew file mode 100644index 0000000..d9b0957--- /dev/null+++ b/docs/releases/github/v0.2.0.md@@ -0,0 +1,5 @@+## What's Changed++* Add configurable snapshot output controls with `text_limit`, `max_tree_nodes`, and `max_tree_depth`, including shared validation and defaults across the supported runtimes. ([#41](https://github.com/iFurySt/open-codex-computer-use/pull/41)) by [@tisfeng](https://github.com/tisfeng)++**Full Changelog**: https://github.com/iFurySt/open-codex-computer-use/compare/v0.1.54...v0.2.0diff --git a/docs/releases/github/v0.2.1.md b/docs/releases/github/v0.2.1.mdnew file mode 100644index 0000000..1c9871f--- /dev/null+++ b/docs/releases/github/v0.2.1.md@@ -0,0 +1,6 @@+## What's Changed++* Document macOS 14.0 as the minimum supported version and separate system compatibility failures from Accessibility and Screen Recording permission troubleshooting. ([#44](https://github.com/iFurySt/open-codex-computer-use/pull/44)) by [@tisfeng](https://github.com/tisfeng)+* Preserve unnamed compact web action targets as buttons so icon-only controls retain usable `element_index` values. ([#45](https://github.com/iFurySt/open-codex-computer-use/pull/45)) by [@tisfeng](https://github.com/tisfeng)++**Full Changelog**: https://github.com/iFurySt/open-codex-computer-use/compare/v0.2.0...v0.2.1diff --git a/docs/releases/github/v0.3.0.md b/docs/releases/github/v0.3.0.mdnew file mode 100644index 0000000..21e5592--- /dev/null+++ b/docs/releases/github/v0.3.0.md@@ -0,0 +1,6 @@+## What's Changed++* Add explicit `click_method` selection across macOS, Linux, and Windows while keeping the default automatic route unchanged and making explicit modes fail closed. ([#47](https://github.com/iFurySt/open-codex-computer-use/pull/47)) by [@tisfeng](https://github.com/tisfeng)+* Add macOS `sky_click` background delivery for supported windows without moving the real pointer or changing the foreground app or window order. ([#48](https://github.com/iFurySt/open-codex-computer-use/pull/48)) by [@tisfeng](https://github.com/tisfeng)++**Full Changelog**: https://github.com/iFurySt/open-codex-computer-use/compare/v0.2.1...v0.3.0diff --git a/docs/releases/github/v0.3.1.md b/docs/releases/github/v0.3.1.mdnew file mode 100644index 0000000..2b47f5f--- /dev/null+++ b/docs/releases/github/v0.3.1.md@@ -0,0 +1,5 @@+## What's Changed++* Preserve clickable boundaries in Chrome accessibility text summaries so compact generic action nodes retain independent `element_index` targets. This fixes internal colleague, forward to others, and email forwarding options being merged into one container. ([#50](https://github.com/iFurySt/open-codex-computer-use/pull/50)) by [@tisfeng](https://github.com/tisfeng)++**Full Changelog**: https://github.com/iFurySt/open-codex-computer-use/compare/v0.3.0...v0.3.1diff --git a/package.json b/package.jsonindex 5867b9f..c863364 100644--- a/package.json+++ b/package.json@@ -6,6 +6,7 @@"npm:build": "node ./scripts/npm/build-packages.mjs","npm:pack": "./scripts/release-package.sh","npm:publish": "node ./scripts/npm/publish-packages.mjs",- "package:skill": "./scripts/package-skill.sh"+ "package:skill": "./scripts/package-skill.sh",+ "release:notes:validate": "node ./scripts/validate-github-release-notes.mjs"}}diff --git a/scripts/check-docs.sh b/scripts/check-docs.shindex d0073ee..973c781 100755--- a/scripts/check-docs.sh+++ b/scripts/check-docs.sh@@ -28,6 +28,7 @@ required_files=("docs/exec-plans/tech-debt-tracker.md""docs/histories/template.md""docs/releases/feature-release-notes.md"+ "docs/releases/github/TEMPLATE.md")missing=0diff --git a/scripts/validate-github-release-notes.mjs b/scripts/validate-github-release-notes.mjsnew file mode 100644index 0000000..e9e2949--- /dev/null+++ b/scripts/validate-github-release-notes.mjs@@ -0,0 +1,126 @@+#!/usr/bin/env node++import { existsSync, readFileSync } from "node:fs";+import path from "node:path";+import { fileURLToPath } from "node:url";++const repoRoot = path.resolve(path.dirname(fileURLToPath(import.meta.url)), "..");+const repositoryURL = "https://github.com/iFurySt/open-codex-computer-use";+const tagPattern = /^v?(\d+\.\d+\.\d+(?:-[0-9A-Za-z.-]+)?)$/;+const cjkPattern = /[\u3400-\u4DBF\u4E00-\u9FFF\uF900-\uFAFF]/u;++function fail(message) {+ throw new Error(message);+}++function parseArgs(argv) {+ const options = {+ notesOnly: false,+ notesPath: undefined,+ tag: undefined,+ };++ for (let index = 0; index < argv.length; index += 1) {+ const arg = argv[index];++ switch (arg) {+ case "--notes-only":+ options.notesOnly = true;+ break;+ case "--notes-path":+ options.notesPath = argv[index + 1];+ index += 1;+ break;+ case "--tag":+ options.tag = argv[index + 1];+ index += 1;+ break;+ default:+ fail(`Unknown argument: ${arg}`);+ }+ }++ if (!options.tag) {+ fail("Usage: validate-github-release-notes.mjs --tag <vX.Y.Z> [--notes-only] [--notes-path <path>]");+ }++ return options;+}++function validateNotes({ notesPath, tag }) {+ if (!existsSync(notesPath)) {+ fail(`Missing reviewed GitHub Release notes: ${path.relative(repoRoot, notesPath)}`);+ }++ const body = readFileSync(notesPath, "utf8").replaceAll("\r\n", "\n");+ if (!body.endsWith("\n")) {+ fail("Release notes must end with a newline");+ }+ if (cjkPattern.test(body)) {+ fail("Release notes must use reviewed English and cannot contain CJK characters");+ }++ const lines = body.trimEnd().split("\n");+ if (lines[0] !== "## What's Changed") {+ fail("Release notes must start with exactly: ## What's Changed");+ }++ const nextHeadingIndex = lines.findIndex((line, index) => index > 0 && line.startsWith("## "));+ const whatsChangedLines = nextHeadingIndex === -1 ? lines.slice(1) : lines.slice(1, nextHeadingIndex);+ const changeItems = whatsChangedLines.filter((line) => line.startsWith("* "));+ if (changeItems.length < 1 || changeItems.length > 3) {+ fail("What's Changed must contain 1 to 3 user-visible bullet items");+ }++ const changelogPrefix = `**Full Changelog**: ${repositoryURL}/compare/`;+ const changelogLines = lines.filter((line) => line.startsWith("**Full Changelog**:"));+ if (changelogLines.length !== 1) {+ fail("Release notes must contain exactly one Full Changelog line");+ }++ const changelogLine = changelogLines[0];+ if (!changelogLine.startsWith(changelogPrefix) || !changelogLine.endsWith(`...${tag}`)) {+ fail(`Full Changelog must use ${repositoryURL}/compare/<previous-tag>...${tag}`);+ }++ const previousTag = changelogLine.slice(changelogPrefix.length, -(`...${tag}`.length));+ if (!tagPattern.test(previousTag) || previousTag === tag) {+ fail("Full Changelog must reference a different semantic previous tag");+ }++ return changeItems.length;+}++function main() {+ const options = parseArgs(process.argv.slice(2));+ const tagMatch = options.tag.match(tagPattern);+ if (!tagMatch) {+ fail(`Release tag must match vX.Y.Z or X.Y.Z: ${options.tag}`);+ }++ const version = tagMatch[1];+ const notesPath = path.resolve(+ repoRoot,+ options.notesPath ?? path.join("docs", "releases", "github", `${options.tag}.md`)+ );++ if (!options.notesOnly) {+ const manifestPath = path.join(repoRoot, "plugins", "open-computer-use", ".codex-plugin", "plugin.json");+ const manifest = JSON.parse(readFileSync(manifestPath, "utf8"));+ if (manifest.version !== version) {+ fail(`Tag ${options.tag} does not match plugin manifest version ${manifest.version}`);+ }+ }++ const changeCount = validateNotes({ notesPath, tag: options.tag });+ console.log(+ `Validated ${path.relative(repoRoot, notesPath)} for ${options.tag}: ${changeCount} user-visible change item(s)`+ );+}++try {+ main();+} catch (error) {+ console.error(`Release notes validation failed: ${error.message}`);+ process.exit(1);+}