openclaw-lark-multi-agent 0.1.0 → 0.1.2

package/README.md

@@ -269,6 +269,27 @@ npm run dev -- config.json
 
 TypeScript output goes to `dist/`.
 
+
+## npm release automation
+
+This repository includes `.github/workflows/publish.yml`. To enable automated npm publishing:
+
+1. Create an npm automation/granular token with package publish permission.
+2. Add it to GitHub repository secrets as `NPM_TOKEN`.
+3. Bump `package.json` version.
+4. Commit and push.
+5. Create a matching tag, for example:
+
+```bash
+npm version patch --no-git-tag-version
+git add package.json package-lock.json
+git commit -m "chore: release v0.1.1"
+git tag v0.1.1
+git push origin main --tags
+```
+
+The publish workflow checks that the git tag matches the package version before running `npm publish`.
+
 ## Repository hygiene
 
 The repository intentionally excludes:

package/README.zh-CN.md

@@ -269,6 +269,27 @@ npm run dev -- config.json
 
 TypeScript 输出目录是 `dist/`。
 
+
+## npm 自动发布
+
+仓库里已经包含 `.github/workflows/publish.yml`。启用自动发布需要：
+
+1. 在 npm 创建 automation/granular token，并授予 package publish 权限。
+2. 在 GitHub 仓库 Settings → Secrets and variables → Actions 中添加 `NPM_TOKEN`。
+3. 修改 `package.json` version。
+4. 提交并推送。
+5. 创建匹配的 tag，例如：
+
+```bash
+npm version patch --no-git-tag-version
+git add package.json package-lock.json
+git commit -m "chore: release v0.1.1"
+git tag v0.1.1
+git push origin main --tags
+```
+
+发布 workflow 会检查 git tag 是否和 package version 一致，然后再执行 `npm publish`。
+
 ## 仓库卫生
 
 仓库会忽略：

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openclaw-lark-multi-agent",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Multi-bot Lark/Feishu bridge for OpenClaw, with per-bot model routing and isolated sessions",
   "type": "module",
   "scripts": {