Release Process

Static UI uses Changesets for automated versioning and publishing.

Release Flow

1. Create a changeset: pnpm changeset
2. Version packages: pnpm changeset version
3. Publish to npm: pnpm changeset publish

Creating a Changeset

pnpm changeset

Follow the prompts to describe your changes and select affected packages.

Versioning

We follow semantic versioning (SemVer):

• Major (1.x): Breaking API changes
• Minor (0.x): New features, backward compatible
• Patch (0.0.x): Bug fixes and minor improvements

Published Packages

• @static-ui/cli — CLI tool
• @static-ui/core — Core schemas and generators
• @static-ui/ui — UI components
• @static-ui/themes — Theme definitions
• @static-ui/registry — Component registry

Release Pipeline

The full release pipeline runs automatically via GitHub Actions:

pnpm release  # Runs: typecheck → lint → test → validate → size → build → publish

Changelogs

Changelogs are auto-generated from conventional commit messages. Each package has its own CHANGELOG.md file.