mirror of https://github.com/logto-io/logto.git synced 2025-02-17 22:04:19 -05:00

History

aiden 39cef8ea47 feat(core): support custom endpoint and addressing style for S3 (#6924 ) Add support for configurable S3 endpoint and addressing style (path-style/virtual-hosted) to improve compatibility with S3-compatible storage services. - Add forcePathStyle option to control URL addressing style - Fix custom endpoint support implementation - Improve URL generation logic for different configurations Resolves: [#6920] Signed-off-by: aiden_lu <allaher@icloud.com>		2025-01-08 08:46:54 +08:00
..
afraid-otters-crash.md	feat(core): support custom endpoint and addressing style for S3 (#6924 )	2025-01-08 08:46:54 +08: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

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.