Infrastructure/logto
0
Fork 0
mirror of https://github.com/logto-io/logto.git synced 2024-12-16 20:26:19 -05:00
Code Issues Activity
logto/.changeset
History
Xiao Yijun 5553425fcd
feat(console): suspend user (#3696)
2023-04-14 16:44:37 +08:00
..
config.json refactor(core): add single-page apps as dependencies 2023-04-02 17:40:07 +08:00
curly-laws-hammer.md fix(console): log event filter (#3678) 2023-04-06 11:32:46 +08:00
fifty-dolls-divide.md chore: add changeset 2023-04-02 14:14:23 +08:00
fluffy-masks-tap.md chore: add changeset 2023-04-01 01:55:39 +08:00
hungry-bears-complain.md feat(phrases): add pl-PL translation 2023-04-01 02:00:04 +08:00
new-windows-rescue.md feat(core): add management API to verify user password (#3680) 2023-04-09 22:01:35 +08:00
popular-wasps-begin.md feat(core): provide management API to detect if user has password (#3698) 2023-04-14 12:22:33 +08:00
README.md refactor: update pubilsh flow 2023-04-02 17:05:18 +08:00
seven-dolphins-hammer.md chore: add changeset 2023-03-31 23:22:46 +08:00
shiny-crabs-wink.md fix(cli): fix changeset syntax (#3689) 2023-04-11 06:05:17 +00:00
spicy-pears-serve.md chore: add comments and refactor 2023-04-07 14:36:25 +08:00
sweet-dots-ring.md feat(console): suspend user (#3696) 2023-04-14 16:44:37 +08:00
tasty-tables-glow.md chore: add changeset 2023-04-07 01:08:27 +08:00
wise-dingos-compete.md refactor(cli): use current directory as instance path if no path input for cli 2023-04-08 17:24:15 +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 service and its schemas and cli, which consists of the following packages:

  • @logto/core (main)
  • @logto/schemas
  • @logto/cli
  • @logto/create

Their versions will be always in sync, and forms our main release.

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.