For now, Changesets only supports tagging packages separately, instead of tagging a "release group". There is an [open issue](https://github.com/changesets/changesets/issues/683) that is still hanging in the air.
So, we are using our own "grouping" release strategy in this monorepo:
### Core
The release group that includes the Logto core products, which consists of the following packages:
-@logto/console
-@logto/core (main)
-@logto/integration-tests
-@logto/ui
Their version will be in sync, and forms our main release.
### CLI
The release group that includes Logto CLI and its aliases:
-@logto/cli (main)
-@logto/create
### Others
For simplicity, we will tag other **public** packages separately and publish them to NPM. But in most cases, no GitHub release will present for these packages.