release
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseRelease
发布
Steps
步骤
bash
undefinedbash
undefined1. Commit all changes first
1. 先提交所有更改
2. Bump version (patch / minor / major)
2. 升级版本(补丁版 / 次版本 / 主版本)
npm version <patch|minor|major> -m "chore: bump version to %s"
npm version <patch|minor|major> -m "chore: bump version to %s"
3. Push commit and tag
3. 提交代码并推送标签
git push && git push --tags
CI will automatically run tests, publish to npm, and create a GitHub Release.git push && git push --tags
CI 会自动运行测试、发布至 npm 并创建 GitHub Release。Rules
规则
- Always pass to
-m "chore: bump version to %s"npm version - Tag format: (e.g.
v*), this is npm's defaultv0.2.0 - Do NOT manually edit in
version— always usepackage.jsonnpm version - Do NOT manually create tags — creates them
npm version - Ensure all changes are committed before running
npm version - CI requires the GitHub repo to be public (for )
--provenance - npm trusted publishing via OIDC — no secret needed, configured on npmjs.com
NPM_TOKEN
- 执行 时必须添加
npm version参数-m "chore: bump version to %s" - 标签格式:(例如
v*),这是 npm 的默认格式v0.2.0 - 请勿手动修改 中的
package.json字段 —— 请始终使用version命令npm version - 请勿手动创建标签 —— 会自动创建标签
npm version - 执行 前请确保所有更改已提交
npm version - CI 要求 GitHub 仓库为公开状态(以支持 参数)
--provenance - 通过 OIDC 实现 npm 可信发布 —— 无需 密钥,需在 npmjs.com 上完成配置
NPM_TOKEN