0
Fork 0
mirror of https://github.com/logto-io/logto.git synced 2024-12-16 20:26:19 -05:00
logto/.changeset
2024-07-31 14:22:21 +08:00
..
bright-carpets-relax.md feat(connector): added postmark connector 2024-07-31 14:22:21 +08:00
clever-lemons-yawn.md feat(schemas): add custom data to application (#6309) 2024-07-25 09:55:57 +00:00
config.json chore: update changesets config (#3703) 2023-04-17 16:22:39 +08:00
cool-otters-unite.md fix(console): fix Google connector scope field can not be unset bug (#6254) 2024-07-17 15:17:37 +08:00
dull-goats-help.md feat: organization logo 2024-07-07 21:40:26 +08:00
fast-rats-talk.md fix(core): fix some webhook api body status 404 bug (#6311) 2024-07-25 17:34:59 +08:00
lazy-geese-bow.md feat: organization logo 2024-07-07 21:40:26 +08:00
polite-plums-tease.md chore: add changesets (#6239) 2024-07-14 17:42:55 +08:00
README.md refactor: update pubilsh flow 2023-04-02 17:05:18 +08:00
seven-comics-tan.md chore: add changeset for impersonation (#6251) 2024-07-19 18:23:18 +08:00
shy-baboons-occur.md refactor: experience ssr (#6229) 2024-07-12 19:00:36 +08:00
slow-boxes-greet.md feat(connector): enable custom headers for SMTP connector (#6256) 2024-07-17 15:16:54 +08:00
sour-windows-wave.md refactor(experience): use vite 2024-07-24 17:47:37 +08:00
stale-planets-sneeze.md chore: launch multiple app secrets 2024-07-28 08:40:01 +08:00
swift-stingrays-tap.md chore: add changesets (#6239) 2024-07-14 17:42:55 +08:00
violet-phones-occur.md refactor(connector): use tsup for building 2024-07-28 13:15:09 +08:00

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.