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
simeng-li 9518658595
fix(schemas): fix the get interation/consent api bug (#5503) 
* fix(schemas): fix the get interation/consent api bug

fix the get interation/consent api bug

* chore: update changeset

update changeset

* fix: update changeset

update changeset

* refactor(schemas, console): alter the resource scopes description field to nullable (#5504)

* refactor(schemas, console): alter the resoruce scopes description field nullable

make the resourec scopes description nullable

* fix(test): fix the type issue in the integration test

fix the type issue in the integration test

* fix(console): add the field register

add the field register

* fix: update the changeset

update the changeset

* fix(console,test): update comments and rebase

update comments and rebase the master
2024-03-20 14:31:35 +08:00
..
clever-buttons-behave.md feat(core): create user with avatar and custom data (#5476) 2024-03-08 03:29:39 +00:00
config.json chore: update changesets config (#3703) 2023-04-17 16:22:39 +08:00
README.md refactor: update pubilsh flow 2023-04-02 17:05:18 +08:00
real-eels-jam.md feat(core): create user with encrypted password (#5446) 2024-03-04 15:41:36 +09:00
seven-socks-perform.md fix(schemas): fix the get interation/consent api bug (#5503) 2024-03-20 14:31:35 +08:00
silent-singers-trade.md refactor(experience): skip non-object messages in native (#5491) 2024-03-12 11:27:18 +08:00
thin-shoes-jog.md chore: add changeset for the bug fix PR (#5507) 2024-03-18 02:27:05 +00:00
witty-moose-kick.md refactor: update invitation apis 2024-03-19 10:38:36 +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.