Skip to content

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

docs(release): record verified v1.1.2 publication (#110)

Leoeb501f4b1fb1
diff --git a/docs/exec-plans/active/20261017-release-v1.1.2.md b/docs/exec-plans/completed/20261017-release-v1.1.2.md
similarity index 55%
rename from docs/exec-plans/active/20261017-release-v1.1.2.md
rename to docs/exec-plans/completed/20261017-release-v1.1.2.md
index 5bbdf3f..2c7ab6a 100644
--- a/docs/exec-plans/active/20261017-release-v1.1.2.md
+++ b/docs/exec-plans/completed/20261017-release-v1.1.2.md
@@ -17,11 +17,19 @@ A successful tag push does not prove publication. Check all release jobs, actual
- [x] Read the release SOP, synchronize main and confirm installed/latest version 1.1.1.
- [x] Align current version sources and prepare reviewed English release notes.
- [x] Run local release tests, signed universal packaging and archive checks.
-- [ ] Commit the release bump, synchronize, merge and push tag v1.1.2.
-- [ ] Confirm workflow, all npm packages and public GitHub assets.
-- [ ] Update the global npm installation and verify version and functionality.
-- [ ] Record final results and archive this plan.
+- [x] Commit the release bump, synchronize, merge and push tag v1.1.2.
+- [x] Confirm workflow, all npm packages and public GitHub assets.
+- [x] Update the global npm installation and verify version and functionality.
+- [x] Record final results and archive this plan.
## Decisions
- 2026-10-17: Use patch version 1.1.2 for the merged cursor, Linux read-back and repository migration fixes. The user explicitly authorized public release and a global npm update.
+
+## Publication
+
+PR #109 merged as `531c9d4d6e2e842f93368283ebd1d757625b73b1`; tag `v1.1.2` points to that commit. Release workflow `39012969782` completed successfully in all four jobs. All three npm packages report version/latest 1.1.2, canonical repository metadata and SLSA provenance. Ten downloaded public assets passed reviewed-notes, source, version, digest and checksum checks; the universal App, four Locked Use components, notarization/stapling, Gatekeeper and workflow-bound SLSA attestation verified.
+
+The authorized global npm update completed. All four CLI aliases and the actual running MCP Agent report 1.1.2. Permission diagnostics are fully granted; native MCP list_apps and JavaScript cua.listApps succeeded. The installed native executable matches the verified public release. No privileged component installation or system authorization changes were needed.
+
+Completed on 2026-10-17. See the release history for validation counts, registry propagation and local verifier compatibility details.
diff --git a/docs/histories/2026-10/20261017-1510-release-v1.1.2.md b/docs/histories/2026-10/20261017-1510-release-v1.1.2.md
index 19df449..0397e72 100644
--- a/docs/histories/2026-10/20261017-1510-release-v1.1.2.md
+++ b/docs/histories/2026-10/20261017-1510-release-v1.1.2.md
@@ -17,4 +17,20 @@
- Developer ID universal App 与四个 Locked Use 组件签名 / 架构检查通过,remote 插件 ABI 与 kernel verifier 正负例通过。
- 三个 npm staging 包及 tgz 均为 1.1.2,包含六个 runtime target、四个 alias,无 optionalDependencies;主 App、Guardian 与插件版本均为 1.1.2。
- CursorMotion-1.1.2.dmg 的 universal 架构、签名与磁盘镜像校验通过;直接下载归档与 SHA256SUMS 全部匹配。
-- 公开发布与本机更新验证进行中。
+
+## 公开发布
+
+- PR #109 合并为 `531c9d4d6e2e842f93368283ebd1d757625b73b1`,tag `v1.1.2` 指向该提交;Release workflow `39012969782` 四个 job 全部成功。
+- 三个 npm 包均通过新仓库的 GitHub Actions OIDC 发布 1.1.2,并生成 transparency log provenance;主 App 与 Cursor Motion 公证均为 Accepted、staple 成功。
+- 从公开 Release 下载十个资产,正文与审核文件一致,manifest 版本 / 仓库 / 源码提交及全部资产大小、digest 和 SHA256SUMS 匹配。
+- 公开 universal App 的四组件架构 / 签名通过,App 和 DMG 的 stapler validate 通过,Gatekeeper accepted / Notarized Developer ID。
+- 新版官方 `gh 2.102.0` 验证 App zip 的 SLSA attestation,限定当前仓库与 release.yml;原有 `gh 2.49.0` 不支持新 Sigstore root 的密钥类型,已将复验方式补入发布指南。本机全局 gh 未修改。
+- 待 registry 传播后,三个包的普通 npm 查询与实时 dist-tags 均确认 version/latest=1.1.2,repository.url 指向新仓库并带 SLSA provenance。传播期间出现兼容包 tarball 已可下载、目标版本元数据仍 404 的窗口;没有重复发布。
+
+## 本机更新
+
+- 按用户要求执行 `npm i -g open-computer-use`,全局包从 1.1.1 更新至 1.1.2;四个 CLI alias 都返回 1.1.2。
+- `ocu capabilities --json` 确认 native MCP / JS / REPL 均可用;`ocu doctor --json` 的辅助功能、录屏与 allGranted 均为 true,无缺失权限。
+- 实际 MCP Agent 的 initialize 返回 1.1.2,列出 10 个工具并成功调用只读 list_apps;`ocu js` 通过 cua.listApps 成功访问 native runtime。
+- 已安装 universal App 与四个 Locked Use 组件签名 / 架构检查通过,主 executable 与下载验证过的公开 Release 完全一致。
+- npm 11.17 默认跳过的 postinstall 仅打印安装提示,未影响上述运行验证;没有放宽全局 allow-scripts 配置或修改已安装的 Locked Use 系统组件。
diff --git a/docs/releases/RELEASE_GUIDE.md b/docs/releases/RELEASE_GUIDE.md
index ca356a8..2eec7c9 100644
--- a/docs/releases/RELEASE_GUIDE.md
+++ b/docs/releases/RELEASE_GUIDE.md
@@ -25,7 +25,7 @@ npm staging 的 `repository.url` 必须与发布所在的 GitHub 仓库一致,
publisher 即使已绑定仓库不可变身份、页面仍显示 Valid,也不能据此推断改名后的认证可用:本次迁移的旧名称连接在真实 token exchange 中返回 HTTP 404。应以新仓库名新增连接,沿用原有权限,并验证真实认证。创建连接需要账号所有者逐包完成 npm 的安全密钥二步验证。旧名连接保留为迁移记录,下次正式发版成功后可按需清理;它们不能作为新仓库认证的 fallback。参考 [npm 官方 Trusted Publishing 文档](https://docs.npmjs.com/trusted-publishers/)与 [npm Registry API](https://api-docs.npmjs.com/)。
-2026-10-17 的迁移已通过 [真实认证复验](https://github.com/iFurySt/open-computer-use/actions/runs/39012120822):三个包的 token exchange 均返回 HTTP 201,新连接随后从 Pending validation 变为 Valid。此次没有发布新版本或保存返回的 token;npm 现有版本仍为 1.1.1,新仓库元信息会随下一次正常发版进入 registry。
+2026-10-17 的迁移已通过 [真实认证复验](https://github.com/iFurySt/open-computer-use/actions/runs/39012120822):三个包的 token exchange 均返回 HTTP 201,新连接随后从 Pending validation 变为 Valid。该认证复验没有发布新版本或保存返回的 token,当时 npm 版本仍为 1.1.1。后续 [v1.1.2 正式发布](https://github.com/iFurySt/open-computer-use/actions/runs/39012969782) 已验证四个 job 成功、三个包通过 OIDC 发布,新仓库元信息与 provenance 已进入 registry。
- 本地 staging / 打 tgz:`./scripts/release-package.sh`
- 本地重新封装 GitHub Release assets:`./scripts/package-github-release-assets.sh --version <version>`
@@ -186,6 +186,9 @@ gh run view -R iFurySt/open-computer-use <run-id> --log-failed
- 发布成功后,`npm view` 仍显示旧版本或目标版本返回 404
- 先核对 CI 中每个包的 publish 成功日志。registry 元数据的 CDN 响应可能带有 `max-age=300`,短时间内仍返回旧内容;`--prefer-online` 也可能读到同一份边缘缓存。
- 可通过 `https://registry.npmjs.org/-/package/<package-name>/dist-tags` 核对实时 dist-tag;待缓存刷新后,再确认三个包的目标版本和 `latest` 一致,避免把传播延迟误判为发布失败。
+ - v1.1.2 曾出现 tarball 已返回 HTTP 200,但版本元数据仍返回 404 的传播窗口。可只读核对带唯一查询参数的完整 packument 辅助定位,最终仍以普通 `npm view` 与实际安装确认,不能用单个缓存响应判断需要重发。
+- `gh attestation verify` 提示 `unsupported tlog public key type: PKIX_ED25519`
+ - 先用新版官方 GitHub CLI 复验。此次本机 `gh 2.49.0` 无法读取新的 Sigstore trusted root,而临时下载并核对官方 archive digest 的 `gh 2.102.0` 验证同一制品成功;旧验证器的不兼容不能据此判定 Release 签名失效。复验应同时限制 `--repo iFurySt/open-computer-use` 与 `--signer-workflow iFurySt/open-computer-use/.github/workflows/release.yml`。
- 构建阶段失败
- 优先看 `Build npm release artifacts`、`package-github-release-assets.sh` 的架构/归档校验、`Build Cursor Motion DMG` 或 Swift 编译错误。
- GitHub Release 资产上传失败