.. | ||
clever-panthers-lay.md | ||
config.json | ||
fifty-balloons-taste.md | ||
green-geese-train.md | ||
grumpy-clocks-refuse.md | ||
lovely-rivers-sniff.md | ||
neat-snakes-smash.md | ||
pre.json | ||
quick-turtles-joke.md | ||
README.md | ||
silly-rules-laugh.md | ||
thin-oranges-act.md | ||
tricky-mirrors-act.md | ||
unlucky-lizards-agree.md |
Changesets
Hello and welcome! This folder has been automatically generated by @changesets/cli
, a build tool that works
with multi-package repos, or single-package repos to help you version and publish your code. You can
find the full documentation for it in our repository
We have a quick list of common questions to get you started engaging with this project in our documentation
Logto publish flow
For now, Changesets only supports tagging packages separately, instead of tagging a "release group". There is an open issue 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.