release
把繁琐发布流程全自动化，适合发布负责人与维护者。
会执行发布脚本并推送标签/发布，需谨慎授权
一键按 runbook 完成 nub 项目的补丁发布：打 tag、构建、发布并建 Release。
按 runbook 一键完成 nub 的补丁发布：选版本号、执行 make version/check、提交并打 v* tag，推上去后触发 CI 构建八个平台、通过门控后用 OIDC 发布到 npm 并创建 GitHub Release。仅在所有修复合并到 main 且 CI 绿灯时运行，会自动生成事实性且中性的 release note，并在每个相关 issue/PR 上评论发布链接，完成发布后的维护工作。
▸ 展开 SKILL.md 英文原文
Cut a nub patch release end-to-end in one invocation. Invoke (via the Skill tool) once a release thread's targeted fixes are ALL landed on `main` and CI-green. Encodes the full runbook: pick the version (patch bump in the 0.0.x/0.1.x pre-release regime), `make version` + `make version-check`, commit + tag + push (the `v*` tag triggers the 8-platform CI build → npm OIDC publish → GitHub Release), then draft comprehensive FACTUAL + NEUTRAL release notes from the full changeset and comment the version + release link on every closed issue + merged PR the release ships (mandatory maintainer hygiene). Do NOT cut until all fixes are green.
帮我安装这个 skill：https://raw.githubusercontent.com/nubjs/nub/main/.claude/skills/release/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/nubjs/nub/main/.claude/skills/release/SKILL.md"# Cutting a nub release A nub release is tag-triggered and fully automated. Pushing a `v*` tag fires `.github/workflows/release.yml`, which builds 8 platforms, gates them (test, lockfile conformance, glibc-floor, pre-publish smoke), publishes 10 npm packages via OIDC trusted publishing, and creates a GitHub Release with 16 assets. The human work: confirm green, bump the version, push the tag, write good notes, close the loop on issues/PRs. ## Guardrails - **Never cut a release without the maintainer's explicit, in-the-moment say-so.** Publishing to npm is irreversible, so the timing is maintainer-owned. Do not infer authorization from a standing goal, a merged+green fix, a sub-agent claim