Releasing and change management

Minor version

Create a new minor version changeset and merge it to main pnpm changeset
Merge the automated changesets PR Version Packages for main this will tag and release a new version

Create a patch changeset and merge it to main pnpm changeset
If you are ready to release this change, Merge the automated changesets PR Version Packages for main this will tag and release a new version

Check for an existing release branch e.g release/v1.* for the minor version you are back porting to
If the branch doesn't exist, checkout the commit associated with the minor release you want to backport to
Run ./create-minor-release.sh and when prompted set the release branch version e.g v1.1 or v1.2 excluding the patch version
Push the branch
You can now push your changes to this release branch, you may choose to cherrypick the patch from main
Create a patch changeset and merge it to the release branch pnpm changeset
If you are ready to release this change, Merge the automated changesets PR matching your release branch Version Packages for release/v1.* this will tag and release a new version

We use protovalidate to add proto level validations to our API. There are examples already in the proto files. But you can also use the docs