Versioning

How versioning works

This project uses Changesets to manage version numbers and changelogs.

The version number follows semantic versioning:

• Major (2.0.0) — Breaking changes to the template structure
• Minor (1.4.0) — New features, components, or skills
• Patch (1.3.1) — Bug fixes, dependency updates

For contributors

After making changes that affect users of this template, run:

bun changeset

This asks you:

1. Which packages changed
2. Whether it's a major, minor, or patch change
3. A summary of what changed (write this for humans, not machines)

Commit the generated file (in .changeset/) with your pull request.

How releases happen

1. Contributors merge PRs with changeset files
2. A GitHub Action automatically creates a "Version Packages" PR
3. That PR updates CHANGELOG.md and bumps the version number
4. When merged, a new GitHub Release is created with a git tag

Viewing the changelog

See CHANGELOG.md for the full release history.

Current version

The template is currently at v1.3.0 (the root package.json version).