clawdbot-feishu npm 发布流程指南：自动化版本管理与GitHub发布

release by m1heng/clawdbot-feishu

88 周安装量

4,300 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/m1heng/clawdbot-feishu --skill release

Node.js 自动化开发运维

🇨🇳中文介绍

发布流程

将 @m1heng-clawd/feishu 的新版本发布到 npm 并创建 GitHub 发布。

前提条件

工作树是干净的（所有更改都已提交到 main 分支）
npm login 会话处于活动状态，并且对 @m1heng-clawd 作用域具有发布权限
gh CLI 已通过身份验证

步骤

1. 确定版本更新类型

检查自上次发布以来的更改：

# 查找最新的发布标签
gh release list --limit 1

# 查看提交记录和差异统计
git log <last-tag>..HEAD --oneline
git diff <last-tag>..HEAD --stat

选择更新类型：patch（错误修复）、（新功能）或（破坏性变更）。

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

3. 起草发布说明

查看完整的差异以编写发布说明：

git diff <last-tag>..HEAD

首先创建 GitHub 发布草稿：

gh release create v<new-version> --draft --title "v<new-version>" --target main --notes "<release notes markdown>"

4. 更新 package.json 中的版本号

编辑 package.json，将 "version" 字段更新为 <new-version>。

5. 提交、打标签并推送

git add package.json
git commit -m "chore: bump version to <new-version>"
git tag v<new-version>
git push && git push --tags

如果身份验证失败，请要求用户先运行 npm login，然后重试。

7. 发布 GitHub 版本

gh release edit v<new-version> --draft=false

遵循既定格式（请参考之前的发布）：

## 新功能

- **功能标题** — 描述。(#PR)

## 错误修复

- **修复标题** — 描述。(#PR)

## 内部变更

- 内部变更描述。

npm publish 404 / 身份验证错误

npm login          # 重新进行身份验证
npm whoami         # 验证是否已登录
npm publish        # 重试

如果标签已创建但发布失败，请在修复问题后删除并重新创建：

git tag -d v<version>
git push origin :refs/tags/v<version>
# 修复问题，然后重新打标签并推送

🇺🇸English

Release Workflow

Publish a new version of @m1heng-clawd/feishu to npm and create a GitHub release.

Prerequisites

Working tree is clean (all changes committed to main)
npm login session is active with publish access to @m1heng-clawd scope
gh CLI is authenticated

Steps

1. Determine version bump

Check what changed since the last release:

# Find latest release tag
gh release list --limit 1

# Review commits and diff stat
git log <last-tag>..HEAD --oneline
git diff <last-tag>..HEAD --stat

Choose bump type: patch (bug fixes), minor (new features), or major (breaking changes).

2. Type check

npx tsc --noEmit

Do NOT proceed if type check fails.

3. Draft release notes

Review the full diff to write release notes:

git diff <last-tag>..HEAD

Create a GitHub release draft first:

gh release create v<new-version> --draft --title "v<new-version>" --target main --notes "<release notes markdown>"

4. Bump version in package.json

Edit package.json to update the "version" field to <new-version>.

5. Commit, tag, and push

git add package.json
git commit -m "chore: bump version to <new-version>"
git tag v<new-version>
git push && git push --tags

6. Publish to npm

npm publish

If auth fails, ask the user to run npm login first, then retry.

7. Publish GitHub release

gh release edit v<new-version> --draft=false

Release Notes Format

Follow the established format (see previous releases for reference):

## Features

- **Feature title** — Description. (#PR)

## Bug Fixes

- **Fix title** — Description. (#PR)

## Internal

- Internal change description.

Troubleshooting

npm publish 404 / auth error

npm login          # re-authenticate
npm whoami         # verify logged in
npm publish        # retry

Tag already exists

If the tag was created but publish failed, delete and recreate after fixing:

git tag -d v<version>
git push origin :refs/tags/v<version>
# fix issue, then re-tag and push

Weekly Installs

Repository

m1heng/clawdbot-feishu

GitHub Stars

4.3K

First Seen

Feb 11, 2026

Security Audits

Gen Agent Trust HubFail SocketPass SnykPass

Installed on

opencode78

gemini-cli75

github-copilot75

codex75

cursor75

amp74