Use this skill when preparing or executing a Pake release. Shared facts live in AGENTS.md and are not repeated here: the four version files and tag format (Version Management), CI jobs, Trusted Publishing, surface separation, and the contributors bot (Release Workflow), and issue closeout (Issue Closeout After a Fix).
Pre-Release
- Before changing files or running any formatter/build, freeze the full baseline with
git status --short --branch -uall,git diff, andgit diff --cached. If the checkout contains unrelated or ambiguously owned changes, prepare the release in an isolated worktree. - Confirm the new version (
jq .version package.json; previous tag per AGENTS.md Version Management) and thatnpm view pake-cli@X.Y.Z versionreturns 404. - Update all four version files.
-
pnpm run format, thenpnpm test. Ifpnpm testfails at the suite'spnpm install pake-cli@latest(run in/tmp) against a mirror, re-run once; two consecutive failures are real. -
pnpm run cli:build, thenpnpm run release:check(version sync, format, vitest, package contents, npm dry-run). - Re-read
git status --short --branch -uall,git diff, andgit diff --cached. Restore only build-churn paths that were clean in the baseline and provably generated by this run; otherwise repeat in an isolated worktree. - Commit
chore: bump version to VX.Y.Zwith the rebuiltdist/cli.jsstaged viagit add -f dist/cli.js.
Tag And Verify
git tag -a VX.Y.Z -m "Release VX.Y.Z"
git push origin VX.Y.Z
If the bump push is rejected, rebase onto the contributors bot commit as AGENTS.md describes, push, then tag the last real commit. Never force-push.
-
gh run list --workflow=release.yml, then pollgh run view <run-id> --json status,conclusion. -
gh release view VX.Y.Z --json tagName,url,assets, then fill the title and body per GitHub Release Notes below; CI leaves a bare placeholder. -
gh run list --workflow=npm-publish.yml, thennpm view pake-cli@X.Y.Z version gitHead dist.tarball --jsonandnpm view pake-cli versionforlatest. - Record
gh run list --workflow=quality-and-test.yml --limit 3separately. - Add the six positive reactions (
+1,laugh,heart,hooray,rocket,eyes) torepos/tw93/Pake/releases/<id>/reactionsviagh apiand read them back. Never-1orconfused.
npm-Only Hotfix (no tag)
For CLI or Rust-template fixes that must reach npm without an app release. The version number is still consumed, so the next V* tag skips over it.
- Bump all four version files,
pnpm run cli:build, stage the version files andgit add -f dist/cli.js. -
pnpm run release:check(already includes vitest). For a Rust-template fix, also run the narrow current-platform Rust check. - Commit
chore: bump version to VX.Y.Z, pushmain, record<publish-sha>withgit rev-parse HEAD. - Wait for
gh run list --workflow=quality-and-test.yml --commit <publish-sha> --limit 3 --json databaseId,headSha,status,conclusionto becompleted/success; for Rust-template changes alsoFull Tauri Build (windows-latest). -
gh workflow run npm-publish.yml --ref main -f expected_sha=<publish-sha> -f quality_run_id=<quality-run-id>. Ifmainmoved, wait for the new head's own Quality run. - Poll
gh run view <run-id> --json headSha,status,conclusion;headShaand the npmgitHeadmust both equal<publish-sha>. - Issue closeout per AGENTS.md; for a Rust-template fix, tell users to rebuild their app after upgrading.
Skip for a hotfix: no V* tag, no GitHub Release or notes, no reactions, no Docker.
A successful publish followed by a verification timeout does not authorize republishing: npm scans new packages for 5 to 15+ minutes. Re-read the registry until the version appears. Local fallback, only when the trusted path is blocked: npm exec --yes --package=pnpm@10.26.2 -- npm publish --registry=https://registry.npmjs.org.
GitHub Release Notes
Before writing notes, gh release view <previous release> and treat its structure as the hard template, codename included. Title: V<X.Y.Z> <Codename>, one English codename word, optionally one emoji (V3.11.8 Polish, V3.11.0 Evolve 👻); patch releases get a codename too. Source items from git log VPREV..VX.Y.Z, user-facing only.
<div align="center">
<img src="https://gw.alipayobjects.com/zos/k/fa/logo-modified.png" alt="Pake Logo" width="120" height="120" style="border-radius:50%" />
<h1 style="margin: 12px 0 6px;">Pake VX.Y.Z</h1>
<p><em>Turn any webpage into a desktop app with one command.</em></p>
</div>
### Changelog
1. ...
### 更新日志
1. ...
Special thanks to @user for the reports and PRs behind this release. If Pake helps you, please consider giving it a star and recommending it to your friends.
> https://github.com/tw93/Pake
Apply with gh release edit VX.Y.Z --title "VX.Y.Z Codename" --notes-file notes.md.