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 50c35a2143
feat(experience): google one tap
2024-06-16 14:50:00 +08:00
..
breezy-bags-help.md feat(connector): google one tap 2024-06-16 13:55:36 +08:00
cold-masks-film.md feat(connector): google one tap 2024-06-16 13:55:36 +08:00
config.json chore: update changesets config (#3703) 2023-04-17 16:22:39 +08:00
cool-cows-relax.md chore: remove dev flags and add changeset for m2m guide feature (#5983) 2024-06-04 14:03:50 +08:00
cyan-garlics-tan.md feat(core): google one tap 2024-06-16 14:31:33 +08:00
fuzzy-eyes-add.md refactor(core,schemas): add user detail payload to User.Deleted webhook event (#5986) 2024-06-04 11:09:27 +00:00
mean-dogs-pump.md feat: automatic social account linking (#5881) 2024-06-08 20:23:57 +08:00
nine-carrots-roll.md feat(experience): google one tap 2024-06-16 14:50:00 +08:00
README.md refactor: update pubilsh flow 2023-04-02 17:05:18 +08:00
smart-laws-compare.md chore(console,core): launch organization jit 2024-06-08 10:22:38 +08:00
stale-shrimps-compare.md chore: add tests and changeset 2024-06-08 10:19:13 +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.