Add Chinese release publishing flow and Automation package - #72
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6db74f6dd4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ### 自动化接口（v0.4 实验性） | ||
|
|
||
| v0.4 Windows Release 构建同时包含 `CodexProviderSync.Automation.exe` 和 `automation-protocol-v0.4.schema.json`。这个一次性进程接口与 Windows GUI 共用同一套 Application 用例；每次调用只在 stdout 输出一份协议 `0.4` JSON，诊断信息写入 stderr。 | ||
| Release 提供独立的 Windows 自动化接口包，内含 `CodexProviderSync.Automation.exe`、`automation-protocol-v0.4.schema.json` 和中文快速说明；Windows 完整包也包含这些文件。这个一次性进程接口与 Windows GUI 共用同一套 Application 用例；每次调用只在 stdout 输出一份协议 `0.4` JSON，诊断信息写入 stderr。普通桌面用户不需要下载自动化接口包。 |
There was a problem hiding this comment.
Once this release is tagged, the README and packaged assets advertise CodexProviderSync.Automation.exe, but the repository's mandatory operator guide still states that no Automation executable is shipped. AGENTS-aware tools will therefore treat the newly published interface as unavailable; either update the operator contract as part of this change or do not publish the executable.
AGENTS.md reference: AGENTS.md:L22-L24
Useful? React with 👍 / 👎.
| if (/\b(?:TODO|TBD)\b/.test(body)) { | ||
| throw new Error(`${relativeBodyPath} still contains a TODO or TBD placeholder.`); | ||
| } |
There was a problem hiding this comment.
When a maintainer copies TEMPLATE-zh.md, updates the title and required safety marker words, but misses any of its <...> fields, this check still passes because it recognizes only TODO and TBD. The release workflow can consequently publish placeholder prose and broken v<版本> download links; validate and reject the template's angle-bracket placeholders as well.
Useful? React with 👍 / 👎.
|
|
||
| 接口支持 `describe`、`status`、`plan`、`sync`、`switch`、`restore` 和 `prune`。所有写命令默认只生成计划，不会修改数据；真正执行时必须同时提供 `--apply`、匹配的计划文件及其 SHA-256 摘要。计划有有效期、绑定目标状态，并且只能使用一次。 | ||
|
|
||
| 该接口不会替代现有 Node CLI。协议 `0.4` 仍处于 1.0 之前的实验阶段，未来可能发生不兼容变更。完整命令示例见 [README](https://github.com/Dailin521/codex-provider-sync/blob/v0.4.0/README.md#business-automation-apiv04-实验性)，自动化接口包内也附带中文快速说明。 |
There was a problem hiding this comment.
For v0.4.0 readers following the “complete command examples” link, the fragment still targets the old business-automation-api... heading, while this commit renames that README section to 自动化接口（v0.4 实验性）. GitHub therefore cannot navigate to the intended section; update the fragment to match the new heading.
Useful? React with 👍 / 👎.
1 participant
What changed
CodexProviderSync.exeupdater asset contractWhy
The v0.4.0 release is a reliability architecture upgrade, but the previous presentation read like a developer changelog. The repository also needed to match the live release's separate Automation package and Chinese-first user guidance so future releases cannot drift from the checked-in process.
Impact
Normal Windows users continue to download
CodexProviderSync.exeand retain built-in updates. Scripts, CI, and AI agents can use the separate Automation package. Future tags fail early when the Chinese announcement, safety notes, version metadata, or package contract is incomplete.Validation
npm test: 192 passed, 0 failed.github/workflows/publish.ymlparsed successfully as YAMLnpm pack --dry-run --jsonincluded the new changelog and documentation