chore(release): 项目版本升至 1.0.0,确立发版规范

[ddpie]

中文

项目进入 1.0.0：公共契约(MCP 工具面 lark_*、部署脚本 flag、OAuth 流程)已稳定,后续破坏它才升 2.0.0。发版 tag 为 v1.0.0+larkcli.1.0.66。

版本号收敛

此前 git tag、serverInfo、两个 package.json 四处版本号各不相同。现统一以 git tag 为准:

• serverInfo.version 2.0.0 → 1.0.0,并新增 larkCliVersion 字段,运行时从 generated-tools.json 的 _larkCliVersion 读取(不硬编码),供下游客户端发现内置的 lark-cli 版本。
• docker/package.json / infra/package.json(及各自 lock 顶层 version)0.2.0 → 1.0.0。

发版规范(新增文档)

docs/releasing_{en,zh}.md,并挂到 AGENTS.md 与 README:

• 版本号格式 v<主>.<次>.<修订>+larkcli.<lark-cli 版本>。主号是项目自身版本,与 lark-cli 解耦;lark-cli 升级(哪怕带新工具/skill)不破坏契约,计入次号/修订号。
• +larkcli.<版本> 是 SemVer build metadata,仅标注内置 lark-cli 版本,不参与版本比较。

验证

npm test 563 通过、lint 干净、invariants 一致;重建镜像确认 initialize 返回 {"version":"1.0.0","larkCliVersion":"1.0.66"}。

---

English

The project reaches 1.0.0: the public contract (the lark_* MCP tool surface, deploy-script flags, OAuth flow) is stable; breaking it from here bumps 2.0.0. Release tag: v1.0.0+larkcli.1.0.66.

Version reconciliation

The git tag, serverInfo, and the two package.json files had drifted apart. They now all track the git tag:

• serverInfo.version 2.0.0 → 1.0.0, plus a new larkCliVersion field read at runtime from generated-tools.json's _larkCliVersion (not hardcoded), so clients can discover the bundled lark-cli version.
• docker/package.json / infra/package.json (and each lock's top-level version) 0.2.0 → 1.0.0.

Release policy (new doc)

docs/releasing_{en,zh}.md, linked from AGENTS.md and the README:

• Version format v<MAJOR>.<MINOR>.<PATCH>+larkcli.<lark-cli version>. MAJOR is the project's own version, decoupled from lark-cli; a lark-cli upgrade (even with new tools/skills) doesn't break the contract and lands as MINOR/PATCH.
• +larkcli.<version> is SemVer build metadata — it records the bundled lark-cli version and doesn't affect precedence.

Verification

npm test 563 pass, lint clean, invariants consistent; a rebuilt image confirms initialize returns {"version":"1.0.0","larkCliVersion":"1.0.66"}.

[coderabbitai]

Warning

Review limit reached

@ddpie, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 17 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 219d91e9-d84c-4ed0-965e-f26dd7420ce4

📥 Commits

Reviewing files that changed from the base of the PR and between ce43b79 and a9b41cc.

⛔ Files ignored due to path filters (2)

• docker/package-lock.json is excluded by !**/package-lock.json
• infra/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (7)

• AGENTS.md
• README.md
• docker/package.json
• docker/server.js
• docs/releasing_en.md
• docs/releasing_zh.md
• infra/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/release-1.0.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}