Release Workflow

Changesets + npm publishing. CI uses OIDC; local requires npm login + OTP.

Workflow

1. Commit code changes

Use conventional commits: fix(pkg), feat(pkg), chore:

2. Create changeset

Write .changeset/<name>.md:

---
"@kasoa/package-name": patch
---

Brief description

Semver (pre-1.0): Always use patch unless explicitly told otherwise.

3. Commit changeset

git add .changeset/<name>.md && git commit -m "chore: add changeset"

4. Publish

Via CI (recommended):

git pull --rebase && git push origin main

Wait for CI, then merge the Version PR:

gh pr merge <number> --rebase

Via local:

Requires: npm whoami (must be logged in)

pnpm changeset version   # versions + auto-commits
pnpm release             # builds + publishes (enter OTP when prompted)
git push origin main --follow-tags

5. Verify

npm view <package-name> version

Edge Cases

Multiple packages: List all in one changeset file.

Push rejected: git pull --rebase && git push origin main

CI fails: gh run view <run-id> --log-failed