We use Changesets to manage versioning and changelogs for various packages in this monorepo.
Pull request titles that start with chore: can be merged without changesets.
These must contain changes with no tangible effect on the product. Otherwise, changeset is always required.
Example: chore: fix typo in code comment.
- Commit some changes to a local branch.
- Run
pnpm changeset. - Select packages to update with
<SPACE>. - The changeset file will be auto-committed.
- Open a pull request.
You can include multiple changesets in a single pull request if each affected package contains distinct changes.
Use capital letters and proper grammar in your changelogs. Omit the qualifier prefix.
---
dashboard: patch
---
fix: prevents double submit on upgrade button
---
dashboard: patch
---
Prevent double submit on upgrade button <feel free to elaborate if it is warranted. you have room to breath here.>
Over time, several PRs will be merged and changesets will build up on main.
There will also be a "release" pull request that is automatically created by the
changeset action. Merging this PR to main constitutes
cutting a release which currently adds git tags and pushes them to remote
repository.