Publish

Step 1: Determine next version

npm view seiro version
npm view create-seiro version

Both should match. Bump to next patch version (e.g., 0.1.5 → 0.1.6).

Step 2: Update CHANGELOG.md

# Edit packages/seiro/CHANGELOG.md
# - Change "[X.Y.Z] - Unreleased" to "[X.Y.Z] - YYYY-MM-DD" (today's date)
# - Add new "[X.Y.Z+1] - Unreleased" section at top for future changes

Step 3: Publish seiro

# Edit packages/seiro/package.json - set new version
# Then:
git add packages/seiro/package.json packages/seiro/CHANGELOG.md
git commit -m "Bump [email protected]"
git tag [email protected]
git push origin main --tags

Step 4: WAIT for seiro to publish

# Poll until version appears (may take 30+ seconds)
npm view seiro version

Do NOT proceed until the new version is confirmed on npm.

Step 5: Update template dependency

# Edit template/package.json - set "seiro": "^X.Y.Z"

Step 6: Sync template

rm -rf packages/create-seiro/template
cp -r template packages/create-seiro/template

Step 7: Publish create-seiro

# Edit packages/create-seiro/package.json - set same version as seiro
# Then:
git add -A
git commit -m "Bump [email protected] with seiro@^X.Y.Z dependency"
git tag [email protected]
git push origin main --tags

Step 8: WAIT for create-seiro to publish

npm view create-seiro version

Step 9: Clear cache and verify

bun pm cache rm

# Test the published package
rm -rf /tmp/test-publish
bunx [email protected] /tmp/test-publish
grep '"seiro"' /tmp/test-publish/package.json
# Should show: "seiro": "^X.Y.Z"

Critical Rules

1. NEVER publish create-seiro before seiro
2. NEVER proceed without confirming npm has the new version
3. ALWAYS use the same version number for both packages
4. ALWAYS sync template before publishing create-seiro
5. ALWAYS update the seiro dependency in template to match the new version
6. ALWAYS update CHANGELOG.md with the release date before publishing