e04d9523a6
* test(core): add integration tests add integration tests for interaction hooks * chore(test): remove legacy test remove legacy test * feat(console, phrases): update the supported webhook events update the supported webhook events * refactor(console): rename webhook and webhook log keys rename webhook and webhook log keys * fix(test): fix integration test fix integration test * feat(console): add devFeature guard add devFeature guard * chore: add changeset add changeset * chore(console): remove the lint rule disable comment remove the lint rule disable comment * fix(test): fix the integartion tests fix the integration tests * fix(console): refine the code refine the code * chore(console): refine comments refine comments |
||
|---|---|---|
| .. | ||
| config.json | ||
| curvy-boxes-hide.md | ||
| 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.