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
Gao Sun 76fd33b7ed
feat: default user role (#5872) 
* feat: default user role

* chore: add tests and changeset

* refactor: show warning for deprecated env

* chore: fix tests
2024-05-17 16:02:05 +08:00
..
config.json chore: update changesets config (#3703) 2023-04-17 16:22:39 +08:00
curvy-boxes-hide.md feat(console, phrases): update the supported webhook events (#5856) 2024-05-15 06:26:52 +00:00
README.md refactor: update pubilsh flow 2023-04-02 17:05:18 +08:00
sixty-scissors-tell.md fix(console): improve audit log error handling if the related user has been removed (#5874) 2024-05-16 04:51:55 +00:00
spicy-drinks-camp.md feat: default user role (#5872) 2024-05-17 16:02:05 +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.