release

name	release
description	Prepare, validate, and publish a Pake release. Not for version bumps without release intent.
version	1.1.0
allowed-tools	["Bash","Read","Grep","Glob"]
disable-model-invocation	true

Release Skill

Use this skill when preparing or executing a Pake release.

Version Files

Four files must be updated in sync — never update one without the others:

• package.json → "version"
• src-tauri/Cargo.toml → version under [package]
• src-tauri/Cargo.lock → version for package pake
• src-tauri/tauri.conf.json → "version"

Release Checklist

Pre-Release

1. Confirm the new version number (check current: cat package.json | jq .version)
2. Update all four version files above
3. Run pnpm run format — must pass cleanly
4. Run pnpm test — must pass cleanly. If the release workflow step fails with pnpm install ... exit code 1 against the CN mirror, re-run once; a single transient flake is acceptable, two consecutive failures is not.
5. Run pnpm run cli:build — Rollup + TS must pass (catches type errors that format misses).
6. Run pnpm run release:check — verifies version sync, package contents, and npm dry-run
7. No uncommitted changes: git status
8. Commit version bump with message: chore: bump version to VX.X.X

Tagging (triggers CI)

git tag -a VX.X.X -m "Release VX.X.X"
git push origin VX.X.X

Tag format: uppercase V prefix (e.g. V3.11.0), not v3.11.0.

Post-Tag Verification

1. Confirm CI triggered: gh run list --workflow=release.yml
2. Watch CI status: gh run watch
3. Verify GitHub Release was created: gh release view VX.X.X
4. Confirm npm workflow exists and is active: gh workflow list --all | grep "Publish npm Package"
5. Confirm npm Trusted Publishing triggered: gh run list --workflow=npm-publish.yml
6. Verify npm published the package: npm view @bghitcode/bghitapp version and npm view @bghitcode/bghitapp@X.Y.Z dist.tarball

npm publishes through Trusted Publishing from .github/workflows/npm-publish.yml. Configure npm package settings with GitHub Actions, BghitCode/BghitApp, workflow file npm-publish.yml, and no environment. Local npm publish is only a fallback if CI or registry state blocks the trusted path.

Trusted Publishing Notes

• The first real Trusted Publishing test must use a new version and a new V* tag; do not retry an already-published version.
• npm package settings should use the strict publishing option: require two-factor authentication and disallow tokens. Trusted Publishing still works with this setting.
• If local fallback is unavoidable, prefer npm exec --yes --package=pnpm@10.26.2 -- npm publish --registry=https://registry.npmjs.org so prepublishOnly can find the pinned pnpm version.
• Do not reply to GitHub issues or close them as released until npm view @bghitcode/bghitapp@X.Y.Z version returns the expected version.

Build Commands (local only)

# Current platform
pnpm build

# macOS universal binary
pnpm build:mac

Cross-platform builds (Windows/Linux) are handled by CI, not locally.

Safety Rules

1. NEVER auto-commit or auto-push without explicit user request
2. NEVER tag before all checks pass
3. ALWAYS verify the four version files are in sync before tagging