moru CLAUDE.md

Moru SDKs

This repository contains all Moru SDKs (JS, Python, CLI) managed as a pnpm workspace.

Version Management with Changesets

We use Changesets for automated version management and releases.

Core Principle: Flexible

You just need changesets before releasing. Commit freely during development, and add changesets when you're ready to release.

When Changesets Are Needed

The following changes require changesets when included in a release:

• ✅ Features: New functionality
• ✅ Bug Fixes: Bug corrections
• ✅ Breaking Changes: Changes that break API compatibility
• ✅ Performance: Performance improvements
• ✅ Dependencies: Dependency updates affecting users

When Changesets Are NOT Needed

Skip changesets for:

• ❌ Documentation-only changes (README, comments)
• ❌ Test-only changes
• ❌ CI/CD configuration changes
• ❌ Internal tooling changes

Workflow (Flexible Approach)

Approach 1: Add as you develop (Recommended - won't forget)

# 1. Make code changes
git add <files>
git commit -m "feat: add new feature X"

# 2. Add changeset
pnpm changeset
# - Which packages? (select with spacebar)
# - Version type? (patch/minor/major)
# - Summary? (description for CHANGELOG)

git add .changeset/
git commit -m "chore: add changeset"
git push

Approach 2: Add later (More flexible)

# 1. Commit multiple changes freely
git commit -m "feat: add feature A"
git commit -m "fix: bug B"
git commit -m "feat: add feature C"
git push

# 2. Add changeset before release
git log --oneline -10  # Review recent changes

pnpm changeset  # "Add features A and C, fix bug B"
git add .changeset/
git commit -m "chore: add changeset for v0.3.3"
git push

Either approach works. Choose what fits your team/personal preference.

Choosing the Right Version Type

Follow Semantic Versioning:

patch (0.3.1 → 0.3.2)

• Bug fixes with no API changes
• Performance improvements
• Internal refactoring
• Documentation updates affecting functionality
• Dependency patches