Versioning
How versions, changelogs, and releases are managed with Changesets.
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 changesetThis asks you:
- Which packages changed
- Whether it's a major, minor, or patch change
- A summary of what changed (write this for humans, not machines)
Commit the generated file (in .changeset/) with your pull request.
How releases happen
- Contributors merge PRs with changeset files
- A GitHub Action automatically opens or updates a "chore: version packages" PR
- That PR updates the package changelogs (
packages/ui/CHANGELOG.md,packages/common/CHANGELOG.md) and bumps both package versions - When merged, the workflow runs
changeset publish, which creates a git tag per package (@repo/ui@x.y.z,@repo/common@x.y.z) and a GitHub Release for each tag with its changelog entry. Nothing is published to npm; the packages are private andprivatePackagesin.changeset/config.jsonenables versioning and tagging them.
Tags in the @repo/<package>@<version> form start with the first release after Changesets 3 was adopted; the older v1.0 and v1.1 tags use a different scheme and are not continued.
Viewing the changelog
See packages/ui/CHANGELOG.md for releases from 1.4.0 on, and the root CHANGELOG.md for 1.0.0 to 1.3.0.
Current version
The template's version is the version of @repo/ui and @repo/common, which Changesets bumps together. Releases from 1.4.0 onward are listed in packages/ui/CHANGELOG.md; 1.0.0 to 1.3.0 are in the root CHANGELOG.md. The root package.json has no version field; the template's version is the version of those two packages.