release: version packages

[silverhand-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@logto/connector-xiaomi@1.0.0

Minor Changes

• 3fa2b79: add Xiaomi social connector

@logto/connector-yunpian-sms@1.0.0

Minor Changes

• 3004ae9: add YunPian SMS connector

@logto/phrases@1.16.0

Minor Changes

• f1b1d9e: new MFA prompt policy

  You can now cutomize the MFA prompt policy in the Console.

  First, choose if you want to enable Require MFA:

  • Enable: Users will be prompted to set up MFA during the sign-in process which cannot be skipped. If the user fails to set up MFA or deletes their MFA settings, they will be locked out of their account until they set up MFA again.
  • Disable: Users can skip the MFA setup process during sign-up flow.

  If you choose to Disable, you can choose the MFA setup prompt:

  • Do not ask users to set up MFA.
  • Ask users to set up MFA during registration (skippable, one-time prompt). The same prompt as previous policy (UserControlled)
  • Ask users to set up MFA on their sign-in after registration (skippable, one-time prompt)

Patch Changes

• 239b81e: loose redirect uri restrictions

  Logto has been following the industry best practices for OAuth2.0 and OIDC from the start. However, in the real world, there are things we cannot control, like third-party services or operation systems like Windows.

  This update relaxes restrictions on redirect URIs to allow the following:

  1. A mix of native and HTTP(S) redirect URIs. For example, a native app can now use a redirect URI like https://example.com.
  2. Native schemes without a period (.). For example, myapp://callback is now allowed.

  When such URIs are configured, Logto Console will display a prominent warning. This change is backward-compatible and will not affect existing applications.

  We hope this change will make it easier for you to integrate Logto with your applications.

@logto/schemas@1.23.0

Minor Changes

• f1b1d9e: new MFA prompt policy

  You can now cutomize the MFA prompt policy in the Console.

  First, choose if you want to enable Require MFA:

  • Enable: Users will be prompted to set up MFA during the sign-in process which cannot be skipped. If the user fails to set up MFA or deletes their MFA settings, they will be locked out of their account until they set up MFA again.
  • Disable: Users can skip the MFA setup process during sign-up flow.

  If you choose to Disable, you can choose the MFA setup prompt:

  • Do not ask users to set up MFA.
  • Ask users to set up MFA during registration (skippable, one-time prompt). The same prompt as previous policy (UserControlled)
  • Ask users to set up MFA on their sign-in after registration (skippable, one-time prompt)

Patch Changes

• Updated dependencies [f1b1d9e]
• Updated dependencies [239b81e]
  • @logto/phrases@1.16.0
  • @logto/core-kit@2.5.2

@logto/cli@1.23.0

Patch Changes

• 2178589: fix fetch official connector list CLI command error

  Due to changes in the npm registry API (https://registry.npmjs.org/-/v1/search) that our CLI add official connector depends on, the new API behavior returns irrelevant search results.

  We need to manually filter out these irrelevant results to avoid potential infinite loops, where each loop triggers an API call, eventually hitting a rate limit and resulting in a status code 429.

• Updated dependencies [f1b1d9e]

• Updated dependencies [239b81e]

  • @logto/schemas@1.23.0
  • @logto/core-kit@2.5.2

@logto/create@1.23.0

Patch Changes

• Updated dependencies [2178589]
  • @logto/cli@1.23.0

@logto/core-kit@2.5.2

Patch Changes

• 239b81e: loose redirect uri restrictions

  Logto has been following the industry best practices for OAuth2.0 and OIDC from the start. However, in the real world, there are things we cannot control, like third-party services or operation systems like Windows.

  This update relaxes restrictions on redirect URIs to allow the following:

  1. A mix of native and HTTP(S) redirect URIs. For example, a native app can now use a redirect URI like https://example.com.
  2. Native schemes without a period (.). For example, myapp://callback is now allowed.

  When such URIs are configured, Logto Console will display a prominent warning. This change is backward-compatible and will not affect existing applications.

  We hope this change will make it easier for you to integrate Logto with your applications.

@logto/tunnel@0.2.3

Patch Changes

• Updated dependencies [239b81e]
  • @logto/core-kit@2.5.2

@logto/console@1.20.0

Minor Changes

• f1b1d9e: new MFA prompt policy

  You can now cutomize the MFA prompt policy in the Console.

  First, choose if you want to enable Require MFA:

  • Enable: Users will be prompted to set up MFA during the sign-in process which cannot be skipped. If the user fails to set up MFA or deletes their MFA settings, they will be locked out of their account until they set up MFA again.
  • Disable: Users can skip the MFA setup process during sign-up flow.

  If you choose to Disable, you can choose the MFA setup prompt:

  • Do not ask users to set up MFA.
  • Ask users to set up MFA during registration (skippable, one-time prompt). The same prompt as previous policy (UserControlled)
  • Ask users to set up MFA on their sign-in after registration (skippable, one-time prompt)

Patch Changes

• 239b81e: loose redirect uri restrictions

  Logto has been following the industry best practices for OAuth2.0 and OIDC from the start. However, in the real world, there are things we cannot control, like third-party services or operation systems like Windows.

  This update relaxes restrictions on redirect URIs to allow the following:

  1. A mix of native and HTTP(S) redirect URIs. For example, a native app can now use a redirect URI like https://example.com.
  2. Native schemes without a period (.). For example, myapp://callback is now allowed.

  When such URIs are configured, Logto Console will display a prominent warning. This change is backward-compatible and will not affect existing applications.

  We hope this change will make it easier for you to integrate Logto with your applications.

@logto/core@1.23.0

Minor Changes

• f1b1d9e: new MFA prompt policy

  You can now cutomize the MFA prompt policy in the Console.

  First, choose if you want to enable Require MFA:

  • Enable: Users will be prompted to set up MFA during the sign-in process which cannot be skipped. If the user fails to set up MFA or deletes their MFA settings, they will be locked out of their account until they set up MFA again.
  • Disable: Users can skip the MFA setup process during sign-up flow.

  If you choose to Disable, you can choose the MFA setup prompt:

  • Do not ask users to set up MFA.
  • Ask users to set up MFA during registration (skippable, one-time prompt). The same prompt as previous policy (UserControlled)
  • Ask users to set up MFA on their sign-in after registration (skippable, one-time prompt)

Patch Changes

• 239b81e: loose redirect uri restrictions

  Logto has been following the industry best practices for OAuth2.0 and OIDC from the start. However, in the real world, there are things we cannot control, like third-party services or operation systems like Windows.

  This update relaxes restrictions on redirect URIs to allow the following:

  1. A mix of native and HTTP(S) redirect URIs. For example, a native app can now use a redirect URI like https://example.com.
  2. Native schemes without a period (.). For example, myapp://callback is now allowed.

  When such URIs are configured, Logto Console will display a prominent warning. This change is backward-compatible and will not affect existing applications.

  We hope this change will make it easier for you to integrate Logto with your applications.

• Updated dependencies [2178589]

• Updated dependencies [f1b1d9e]

• Updated dependencies [239b81e]

  • @logto/cli@1.23.0
  • @logto/experience-legacy@1.11.0
  • @logto/experience@1.11.0
  • @logto/console@1.20.0
  • @logto/phrases@1.16.0
  • @logto/schemas@1.23.0
  • @logto/core-kit@2.5.2

@logto/experience@1.11.0

Minor Changes

• f1b1d9e: new MFA prompt policy

  You can now cutomize the MFA prompt policy in the Console.

  First, choose if you want to enable Require MFA:

  • Enable: Users will be prompted to set up MFA during the sign-in process which cannot be skipped. If the user fails to set up MFA or deletes their MFA settings, they will be locked out of their account until they set up MFA again.
  • Disable: Users can skip the MFA setup process during sign-up flow.

  If you choose to Disable, you can choose the MFA setup prompt:

  • Do not ask users to set up MFA.
  • Ask users to set up MFA during registration (skippable, one-time prompt). The same prompt as previous policy (UserControlled)
  • Ask users to set up MFA on their sign-in after registration (skippable, one-time prompt)

@logto/experience-legacy@1.11.0

Minor Changes

• f1b1d9e: new MFA prompt policy

  You can now cutomize the MFA prompt policy in the Console.

  First, choose if you want to enable Require MFA:

  • Enable: Users will be prompted to set up MFA during the sign-in process which cannot be skipped. If the user fails to set up MFA or deletes their MFA settings, they will be locked out of their account until they set up MFA again.
  • Disable: Users can skip the MFA setup process during sign-up flow.

  If you choose to Disable, you can choose the MFA setup prompt:

  • Do not ask users to set up MFA.
  • Ask users to set up MFA during registration (skippable, one-time prompt). The same prompt as previous policy (UserControlled)
  • Ask users to set up MFA on their sign-in after registration (skippable, one-time prompt)

@logto/integration-tests@1.11.0

Minor Changes

• f1b1d9e: new MFA prompt policy

  You can now cutomize the MFA prompt policy in the Console.

  First, choose if you want to enable Require MFA:

  • Enable: Users will be prompted to set up MFA during the sign-in process which cannot be skipped. If the user fails to set up MFA or deletes their MFA settings, they will be locked out of their account until they set up MFA again.
  • Disable: Users can skip the MFA setup process during sign-up flow.

  If you choose to Disable, you can choose the MFA setup prompt:

  • Do not ask users to set up MFA.
  • Ask users to set up MFA during registration (skippable, one-time prompt). The same prompt as previous policy (UserControlled)
  • Ask users to set up MFA on their sign-in after registration (skippable, one-time prompt)

Patch Changes

• 239b81e: loose redirect uri restrictions

  Logto has been following the industry best practices for OAuth2.0 and OIDC from the start. However, in the real world, there are things we cannot control, like third-party services or operation systems like Windows.

  This update relaxes restrictions on redirect URIs to allow the following:

  1. A mix of native and HTTP(S) redirect URIs. For example, a native app can now use a redirect URI like https://example.com.
  2. Native schemes without a period (.). For example, myapp://callback is now allowed.

  When such URIs are configured, Logto Console will display a prominent warning. This change is backward-compatible and will not affect existing applications.

  We hope this change will make it easier for you to integrate Logto with your applications.

[github-actions]

COMPARE TO master

Total Size Diff 📈 +8.73 KB

Diff by File

Name	Diff
.changeset/brown-donkeys-share.md	📈 +73 Bytes
.changeset/chilled-radios-cover.md	📈 +466 Bytes
.changeset/hot-oranges-join.md	📈 +969 Bytes
.changeset/nervous-apes-suffer.md	📈 +929 Bytes
.changeset/rotten-lizards-buy.md	📈 +70 Bytes
packages/cli/CHANGELOG.md	📈 +608 Bytes
packages/cli/package.json	0 Bytes
packages/connectors/connector-xiaomi/CHANGELOG.md	📈 +97 Bytes
packages/connectors/connector-yunpian-sms/CHANGELOG.md	📈 +100 Bytes
packages/console/CHANGELOG.md	📈 +1.63 KB
packages/console/package.json	0 Bytes
packages/core/CHANGELOG.md	📈 +1.92 KB
packages/core/package.json	0 Bytes
packages/create/CHANGELOG.md	📈 +88 Bytes
packages/create/package.json	0 Bytes
packages/experience-legacy/CHANGELOG.md	📈 +832 Bytes
packages/experience-legacy/package.json	0 Bytes
packages/experience/CHANGELOG.md	📈 +832 Bytes
packages/experience/package.json	0 Bytes
packages/integration-tests/CHANGELOG.md	📈 +1.63 KB
packages/integration-tests/package.json	0 Bytes
packages/phrases/CHANGELOG.md	📈 +1.63 KB
packages/phrases/package.json	0 Bytes
packages/schemas/CHANGELOG.md	📈 +974 Bytes
packages/schemas/alterations/1.23.0-1732851150-rename-saml-application-constraints.ts	📈 +950 Bytes
packages/schemas/alterations/1.23.0-1733212543-add-saml-application-type-to-idp-initiated-sso-application-allow-list.ts	📈 +950 Bytes
packages/schemas/alterations/1.23.0-1735012422-add-saml-application-sessions-table.ts	📈 +1.27 KB
packages/schemas/alterations/next-1732851150-rename-saml-application-constraints.ts	📈 +950 Bytes
packages/schemas/alterations/next-1733212543-add-saml-application-type-to-idp-initiated-sso-application-allow-list.ts	📈 +950 Bytes
packages/schemas/alterations/next-1735012422-add-saml-application-sessions-table.ts	📈 +1.27 KB
packages/schemas/package.json	0 Bytes
packages/toolkit/core-kit/CHANGELOG.md	📈 +847 Bytes
packages/toolkit/core-kit/package.json	0 Bytes
packages/tunnel/CHANGELOG.md	📈 +91 Bytes
packages/tunnel/package.json	0 Bytes
pnpm-lock.yaml	0 Bytes