release-workflow

Release workflow (react-zmage)

Why this skill exists

A react-zmage release has to land in three places that drift independently:

Surface	What it shows	Failure mode if missed
npm registry	latest tarball + version	"1.5.0 was published but npm shows 1.4.1"
Git tag	reproducible commit anchor	bisects skip the release; CI tooling looking for tags breaks
GitHub Release page	human-facing changelog (bilingual)	repo browsers see no changelog; migration guidance invisible

The npm side requires an interactive OTP that only the human user can supply — which means the agent cannot drive the whole flow end-to-end. The skill exists to enforce a clean stop/resume around that human checkpoint, plus to bake in the lesser-known repo conventions (no v prefix on tags, bilingual notes structure, sandbox .tgz paths bumped in lockstep with core).

When to invoke

Strong triggers (just do it):

• "发版" / "我要发版" / "准备发版" / "release" / "publish to npm" / "ship X.Y.Z"
• "bump version and push"
• "tag a release"
• "提交推送 我要发版"

Weak triggers (consider, then judge):

• User says "commit and push" right after material changes to packages/core/src/** — they may want a release but didn't say so. Ask once: "ship a release with this, or commit-only?"
• Conversation has been around polishing public API (props, defaults, docs) — release may be the implicit next step. Don't auto-trigger; surface the option.

Skip:

• Pure internal refactor / test additions with no public-API change — release is overkill.
• User explicitly says "don't publish, just commit" or "preview only".

Pre-flight (Step 0 — before bumping anything)

Run these all and confirm they pass:

# Core unit + integration tests
pnpm --filter react-zmage test

# Public-docs contract (asserts llms.txt, README, AGENTS, types stay aligned)
pnpm --filter llms-eval run test

# i18n key parity across 7 languages — must all be equal
for lang in en de es fr ja ko zh-CN; do
  count=$(grep -cE "^[[:space:]]+'[^']+':" "packages/home/src/i18n/$lang.ts")
  echo "$lang: $count keys"
done

# Build core to verify dist artifacts produce
pnpm --filter react-zmage run build

# (Optional but strong) full sandbox check — catches dist regressions
pnpm -w run check