mirror of https://github.com/logto-io/logto.git synced 2024-12-16 20:26:19 -05:00

History

Gao Sun 3585a77de9 feat(cli): trim keys		2022-11-07 19:26:56 +08:00
..
config.json	chore: add German language changeset (#2324 )	2022-11-04 22:23:26 +08:00
fifty-balloons-taste.md	chore: add German language changeset (#2324 )	2022-11-04 22:23:26 +08:00
pre.json	chore: add German language changeset (#2324 )	2022-11-04 22:23:26 +08:00
README.md	ci: update changeset (#2236 )	2022-10-24 04:03:00 +00:00
unlucky-lizards-agree.md	feat(cli): trim keys	2022-11-07 19:26:56 +08:00

README.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.