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-gitlab@1.0.0

Major Changes

• 31296f0: add GitLab social connector leveraging OAuth2

  Major Changes

  • Initial release of the GitLab connector.

    This release introduces the Logto connector for GitLab, enabling social sign-in using GitLab accounts. It supports OAuth 2.0 authentication flow, fetching user information, and handling errors gracefully.

  Features

  • OAuth 2.0 Authentication: Support for OAuth 2.0 authentication flow with GitLab.
  • User Information Retrieval: Fetches user details such as full name, email, profile URL, and avatar.
  • Error Handling: Graceful handling of OAuth errors, including token exchange failures and user-denied permissions.
  • Configurable Scope: Allows customization of OAuth scopes to access different levels of user information.

Patch Changes

• Updated dependencies [27d2c91]
  • @logto/connector-oauth@1.5.0

@logto/connector-patreon@1.0.0

Major Changes

• aba0892: add Patreon social connector

  Major Changes

  • Initial release of the Patreon connector.

    This release introduces the Logto connector for Patreon, enabling social sign-in using Patreon accounts. It supports OAuth 2.0 authentication flow, fetching user information, and handling errors gracefully.

  Features

  • OAuth 2.0 Authentication: Support for OAuth 2.0 authentication flow with Patreon.
  • User Information Retrieval: Fetches user details such as full name, email, profile URL, and avatar.
  • Error Handling: Graceful handling of OAuth errors, including token exchange failures and user-denied permissions.
  • Configurable Scope: Allows customization of OAuth scopes to access different levels of user information.

Patch Changes

• Updated dependencies [27d2c91]
  • @logto/connector-oauth@1.5.0

@logto/cli@1.20.0

Minor Changes

• 0183d0c: split translate command from @logto/cli and create a standalone package

  The "translate" command has greatly increased the size of the "@logto/cli" package, as it involves TypeScript code manipulation and has to use "typescrpt" as a "dependency".
  In fact, only a small number of developers who want to contribute Logto will use this command, so we believe it's best to separate the less frequently used "translate" command from the "cli" package to keep it small and simple.

  Please also be noted that this change is actually a breaking change for those who use the "translate" command. However, the CLI has to be bundle-released with the "Logto" open-source distribution, and we feel it is still too early to make a major version bump for Logto. Therefore, the "minor" bump is used this time.

Patch Changes

• Updated dependencies [e0326c9]
• Updated dependencies [25187ef]
• Updated dependencies [479d589]
  • @logto/schemas@1.20.0

@logto/connector-kook@0.2.0

Minor Changes

• 4b01ce7: add KOOK social connector

Patch Changes

• Updated dependencies [27d2c91]
  • @logto/connector-oauth@1.5.0

@logto/connector-oauth@1.5.0

Minor Changes

• 27d2c91: adding support for nested attributes

@logto/phrases@1.14.0

Minor Changes

• f150a67: display user password information on user details page

• e0326c9: Add personal access token (PAT)

  Personal access tokens (PATs) provide a secure way for users to grant access tokens without using their credentials and interactive sign-in.

  You can create a PAT by going to the user's detail page in Console or using the Management API POST /users/:userId/personal-access-tokens.

  To use a PAT, call the token exchange endpoint POST /oidc/token with the following parameters:

  1. grant_type: REQUIRED. The value of this parameter must be urn:ietf:params:oauth:grant-type:token-exchange indicates that a token exchange is being performed.
  2. resource: OPTIONAL. The resource indicator, the same as other token requests.
  3. scope: OPTIONAL. The requested scopes, the same as other token requests.
  4. subject_token: REQUIRED. The user's PAT.
  5. subject_token_type: REQUIRED. The type of the security token provided in the subject_token parameter. The value of this parameter must be urn:logto:token-type:personal_access_token.
  6. client_id: REQUIRED. The client identifier of the client application that is making the request, the returned access token will contain this client_id claim.

  And the response will be a JSON object with the following properties:

  1. access_token: REQUIRED. The access token of the user, which is the same as other token requests like authorization_code or refresh_token.
  2. issued_token_type: REQUIRED. The type of the issued token. The value of this parameter must be urn:ietf:params:oauth:token-type:access_token.
  3. token_type: REQUIRED. The type of the token. The value of this parameter must be Bearer.
  4. expires_in: REQUIRED. The lifetime in seconds of the access token.
  5. scope: OPTIONAL. The scopes of the access token.

• 53060c2: add ar-SA language (credit to @zaaakher)

@logto/phrases-experience@1.8.0

Minor Changes

• 53060c2: add ar-SA language (credit to @zaaakher)

@logto/schemas@1.20.0

Minor Changes

• e0326c9: Add personal access token (PAT)

  Personal access tokens (PATs) provide a secure way for users to grant access tokens without using their credentials and interactive sign-in.

  You can create a PAT by going to the user's detail page in Console or using the Management API POST /users/:userId/personal-access-tokens.

  To use a PAT, call the token exchange endpoint POST /oidc/token with the following parameters:

  1. grant_type: REQUIRED. The value of this parameter must be urn:ietf:params:oauth:grant-type:token-exchange indicates that a token exchange is being performed.
  2. resource: OPTIONAL. The resource indicator, the same as other token requests.
  3. scope: OPTIONAL. The requested scopes, the same as other token requests.
  4. subject_token: REQUIRED. The user's PAT.
  5. subject_token_type: REQUIRED. The type of the security token provided in the subject_token parameter. The value of this parameter must be urn:logto:token-type:personal_access_token.
  6. client_id: REQUIRED. The client identifier of the client application that is making the request, the returned access token will contain this client_id claim.

  And the response will be a JSON object with the following properties:

  1. access_token: REQUIRED. The access token of the user, which is the same as other token requests like authorization_code or refresh_token.
  2. issued_token_type: REQUIRED. The type of the issued token. The value of this parameter must be urn:ietf:params:oauth:token-type:access_token.
  3. token_type: REQUIRED. The type of the token. The value of this parameter must be Bearer.
  4. expires_in: REQUIRED. The lifetime in seconds of the access token.
  5. scope: OPTIONAL. The scopes of the access token.

• 25187ef: add support for login_hint parameter in sign-in method

  This feature allows you to provide a suggested identifier (email, phone, or username) for the user, improving the sign-in experience especially in scenarios where the user's identifier is known or can be inferred.

  Example:

  // Example usage (React project using React SDK)
  void signIn({
    redirectUri,
    loginHint: "user@example.com",
    firstScreen: "signIn", // or 'register'
  });

Patch Changes

• 479d589: bump @withtyped dependency version
• Updated dependencies [f150a67]
• Updated dependencies [e0326c9]
• Updated dependencies [53060c2]
  • @logto/phrases@1.14.0
  • @logto/phrases-experience@1.8.0

@logto/translate@0.1.0

Minor Changes

• 0183d0c: split translate command from @logto/cli and create a standalone package

  The "translate" command has greatly increased the size of the "@logto/cli" package, as it involves TypeScript code manipulation and has to use "typescrpt" as a "dependency".
  In fact, only a small number of developers who want to contribute Logto will use this command, so we believe it's best to separate the less frequently used "translate" command from the "cli" package to keep it small and simple.

  Please also be noted that this change is actually a breaking change for those who use the "translate" command. However, the CLI has to be bundle-released with the "Logto" open-source distribution, and we feel it is still too early to make a major version bump for Logto. Therefore, the "minor" bump is used this time.

Patch Changes

• Updated dependencies [f150a67]
• Updated dependencies [e0326c9]
• Updated dependencies [53060c2]
  • @logto/phrases@1.14.0
  • @logto/phrases-experience@1.8.0

@logto/connector-wecom@0.3.1

Patch Changes

• 763dd60: fix wecom connector platform, should be Universal instead of null

@logto/create@1.20.0

Patch Changes

• Updated dependencies [0183d0c]
  • @logto/cli@1.20.0

@logto/console@1.18.0

Minor Changes

• f150a67: display user password information on user details page

• e0326c9: Add personal access token (PAT)

  Personal access tokens (PATs) provide a secure way for users to grant access tokens without using their credentials and interactive sign-in.

  You can create a PAT by going to the user's detail page in Console or using the Management API POST /users/:userId/personal-access-tokens.

  To use a PAT, call the token exchange endpoint POST /oidc/token with the following parameters:

  1. grant_type: REQUIRED. The value of this parameter must be urn:ietf:params:oauth:grant-type:token-exchange indicates that a token exchange is being performed.
  2. resource: OPTIONAL. The resource indicator, the same as other token requests.
  3. scope: OPTIONAL. The requested scopes, the same as other token requests.
  4. subject_token: REQUIRED. The user's PAT.
  5. subject_token_type: REQUIRED. The type of the security token provided in the subject_token parameter. The value of this parameter must be urn:logto:token-type:personal_access_token.
  6. client_id: REQUIRED. The client identifier of the client application that is making the request, the returned access token will contain this client_id claim.

  And the response will be a JSON object with the following properties:

  1. access_token: REQUIRED. The access token of the user, which is the same as other token requests like authorization_code or refresh_token.
  2. issued_token_type: REQUIRED. The type of the issued token. The value of this parameter must be urn:ietf:params:oauth:token-type:access_token.
  3. token_type: REQUIRED. The type of the token. The value of this parameter must be Bearer.
  4. expires_in: REQUIRED. The lifetime in seconds of the access token.
  5. scope: OPTIONAL. The scopes of the access token.

• b837efe: add access deny method to the custom token claims script

  Introduce a new api parameter to the custom token claims script. This parameter is used to provide more access control context over the token exchange process.
  Use api.denyAccess() to reject the token exchange request. Use this method to implement your own access control logics.

  const getCustomJwtClaims: async ({ api }) => {
    // Reject the token request, with a custom error message
    return api.denyAccess('Access denied');
  }

Patch Changes

• ee1947a: support entering name while creating a user
• ff6b304: fix: should not show custom JWT paywall for OSS users
• 3b9714b: set lang attribute for <html>
• fae8725: improve RTL language support

@logto/core@1.20.0

Minor Changes

• e0326c9: Add personal access token (PAT)

  Personal access tokens (PATs) provide a secure way for users to grant access tokens without using their credentials and interactive sign-in.

  You can create a PAT by going to the user's detail page in Console or using the Management API POST /users/:userId/personal-access-tokens.

  To use a PAT, call the token exchange endpoint POST /oidc/token with the following parameters:

  1. grant_type: REQUIRED. The value of this parameter must be urn:ietf:params:oauth:grant-type:token-exchange indicates that a token exchange is being performed.
  2. resource: OPTIONAL. The resource indicator, the same as other token requests.
  3. scope: OPTIONAL. The requested scopes, the same as other token requests.
  4. subject_token: REQUIRED. The user's PAT.
  5. subject_token_type: REQUIRED. The type of the security token provided in the subject_token parameter. The value of this parameter must be urn:logto:token-type:personal_access_token.
  6. client_id: REQUIRED. The client identifier of the client application that is making the request, the returned access token will contain this client_id claim.

  And the response will be a JSON object with the following properties:

  1. access_token: REQUIRED. The access token of the user, which is the same as other token requests like authorization_code or refresh_token.
  2. issued_token_type: REQUIRED. The type of the issued token. The value of this parameter must be urn:ietf:params:oauth:token-type:access_token.
  3. token_type: REQUIRED. The type of the token. The value of this parameter must be Bearer.
  4. expires_in: REQUIRED. The lifetime in seconds of the access token.
  5. scope: OPTIONAL. The scopes of the access token.

• 3d3a220: add support for additional first screen options

  This feature introduces new first screen options, allowing developers to customize the initial screen presented to users. In addition to the existing sign_in and register options, the following first screen choices are now supported:

  • identifier:sign_in: Only display specific identifier-based sign-in methods to users.
  • identifier:register: Only display specific identifier-based registration methods to users.
  • reset_password: Allow users to directly access the password reset page.
  • single_sign_on: Allow users to directly access the single sign-on (SSO) page.

  Example:

  // Example usage (React project using React SDK)
  void signIn({
    redirectUri,
    firstScreen: "identifier:sign_in",
    /**
     * Optional. Specifies which sign-in methods to display on the identifier sign-in page.
     * If not specified, the default sign-in experience configuration will be used.
     * This option is effective when the `firstScreen` value is `identifier:sign_in`, `identifier:register`, or `reset_password`.
     */
    identifiers: ["email", "phone"],
  });

• 25187ef: add support for login_hint parameter in sign-in method

  This feature allows you to provide a suggested identifier (email, phone, or username) for the user, improving the sign-in experience especially in scenarios where the user's identifier is known or can be inferred.

  Example:

  // Example usage (React project using React SDK)
  void signIn({
    redirectUri,
    loginHint: "user@example.com",
    firstScreen: "signIn", // or 'register'
  });

• b837efe: add access deny method to the custom token claims script

  Introduce a new api parameter to the custom token claims script. This parameter is used to provide more access control context over the token exchange process.
  Use api.denyAccess() to reject the token exchange request. Use this method to implement your own access control logics.

  const getCustomJwtClaims: async ({ api }) => {
    // Reject the token request, with a custom error message
    return api.denyAccess('Access denied');
  }

• cc346b4: add password policy checking api

  Add POST /api/sign-in-exp/default/check-password API to check if the password meets the password policy configured in the default sign-in experience. A user ID is required for this API if rejects user info is enabled in the password policy.

  Here's a non-normative example of the request and response:

  POST /api/sign-in-exp/default/check-password
  Content-Type: application/json
  
  {
    "password": "123",
    "userId": "some-user-id"
  }

  400 Bad Request
  Content-Type: application/json
  
  {
    "result": false,
    "issues": [
      { "code": "password_rejected.too_short" },
      { "code": "password_rejected.character_types" },
      { "code": "password_rejected.restricted.sequence" }
    ]
  }

Patch Changes

• a748fc8: fix: add hasPassword field to user API response

• fae8725: improve RTL language support

• 6951e31: introduce new parse_error query parameter flag. The value of parse_error can only be false.

  By default, Logto returns the parsed error code and error description in all the RequestError error responses. This is to ensure the error responses are consistent and easy to understand.

  However, when integrating Logto with Google OAuth, the error response body containing code will be rejected by Google. code is considered as a reserved OIDC key, can't be used as the error code key in the error response body.

  To workaround this, we add a new parse_error query parameter flag. When parsing the OIDC error body, if the parse_error is set to false, only oidc error body will be returned.

  example:

  curl -X POST "http://localhost:3001/oidc/token?parse_error=false"
  

  {
    "error": "invalid_grant",
    "error_description": "Invalid value for parameter 'code': 'invalid_code'."
  }

• 5aab7c0: prevent user registration and profile fulfillment with SSO-only email domains

  Emails associated with SSO-enabled domains should only be used through the SSO authentication process.

  Bug fix:

  • Creating a new user with a verification record that contains an SSO-only email domain should return a 422 RequestError with the error code session.sso_required.
  • Updating a user profile with an SSO-only email domain should return a 422 RequestError with the error code session.sso_required.

• Updated dependencies [f150a67]

• Updated dependencies [ee1947a]

• Updated dependencies [baa8577]

• Updated dependencies [ff6b304]

• Updated dependencies [e0326c9]

• Updated dependencies [3d3a220]

• Updated dependencies [25187ef]

• Updated dependencies [479d589]

• Updated dependencies [2626616]

• Updated dependencies [3b9714b]

• Updated dependencies [ab90f43]

• Updated dependencies [fae8725]

• Updated dependencies [0183d0c]

• Updated dependencies [b837efe]

• Updated dependencies [53060c2]

  • @logto/console@1.18.0
  • @logto/phrases@1.14.0
  • @logto/experience@1.9.0
  • @logto/schemas@1.20.0
  • @logto/experience-legacy@1.9.0
  • @logto/demo-app@1.4.1
  • @logto/cli@1.20.0
  • @logto/phrases-experience@1.8.0

@logto/experience@1.9.0

Minor Changes

• baa8577: migrate experience app using Experience API.

  Migrate experience app API requests from legacy Interaction API to the new Experience API, except the following endpoints:

  • GET /api/interaction/consent
  • POST /api/interaction/consent

  Those endpoints are used in the third-party application's consent page only. Remain unchanged.

• 3d3a220: add support for additional first screen options

  This feature introduces new first screen options, allowing developers to customize the initial screen presented to users. In addition to the existing sign_in and register options, the following first screen choices are now supported:

  • identifier:sign_in: Only display specific identifier-based sign-in methods to users.
  • identifier:register: Only display specific identifier-based registration methods to users.
  • reset_password: Allow users to directly access the password reset page.
  • single_sign_on: Allow users to directly access the single sign-on (SSO) page.

  Example:

  // Example usage (React project using React SDK)
  void signIn({
    redirectUri,
    firstScreen: "identifier:sign_in",
    /**
     * Optional. Specifies which sign-in methods to display on the identifier sign-in page.
     * If not specified, the default sign-in experience configuration will be used.
     * This option is effective when the `firstScreen` value is `identifier:sign_in`, `identifier:register`, or `reset_password`.
     */
    identifiers: ["email", "phone"],
  });

• 25187ef: add support for login_hint parameter in sign-in method

  This feature allows you to provide a suggested identifier (email, phone, or username) for the user, improving the sign-in experience especially in scenarios where the user's identifier is known or can be inferred.

  Example:

  // Example usage (React project using React SDK)
  void signIn({
    redirectUri,
    loginHint: "user@example.com",
    firstScreen: "signIn", // or 'register'
  });

• 2626616: allow link new social identity to an existing user account when registration is disabled.

  Previous behavior

  Sign-in with a social identity that does not have an existing user account will throw an identity_not_exist error. When the registration is disabled, the error message will be shown, the user will not be able to create a new account or link the social identity to an existing account via verified email or phone number.

  Expected behavior

  When the registration is disabled, if a related user account is found, the user should be able to link the social identity to an existing account via a verified email or phone number.

  Updates

  When the registration is disabled:

  • Show identity_not_exist error message if no related user account is found.
  • Automatically link the social identity to the existing account if a related user account is found and social automatic account linking is enabled.
  • Redirect the user to the social link account page if a related user account is found and social automatic account linking is disabled.
  • Hide the register button on the social link account page if the registration is disabled.

  When the registration is enabled:

  • Automatically register a new account with the social identity if no related user account is found.
  • Automatically link the social identity to the existing account if a related user account is found and social automatic account linking is enabled.
  • Redirect the user to the social link account page if a related user account is found and social automatic account linking is disabled.
  • Show the register new account button on the social link account page.

Patch Changes

• 3b9714b: set lang attribute for <html>

• ab90f43: fix(experience): prevent errors from applying unsupported cached identifier types

  Previously, cached identifier input values were applied to all pages without type checking, potentially causing errors. Now, the type is verified before application to ensure compatibility with each page's supported types.

• fae8725: improve RTL language support

@logto/experience-legacy@1.9.0

Minor Changes

• 2626616: allow link new social identity to an existing user account when registration is disabled.

  Previous behavior

  Sign-in with a social identity that does not have an existing user account will throw an identity_not_exist error. When the registration is disabled, the error message will be shown, the user will not be able to create a new account or link the social identity to an existing account via verified email or phone number.

  Expected behavior

  When the registration is disabled, if a related user account is found, the user should be able to link the social identity to an existing account via a verified email or phone number.

  Updates

  When the registration is disabled:

  • Show identity_not_exist error message if no related user account is found.
  • Automatically link the social identity to the existing account if a related user account is found and social automatic account linking is enabled.
  • Redirect the user to the social link account page if a related user account is found and social automatic account linking is disabled.
  • Hide the register button on the social link account page if the registration is disabled.

  When the registration is enabled:

  • Automatically register a new account with the social identity if no related user account is found.
  • Automatically link the social identity to the existing account if a related user account is found and social automatic account linking is enabled.
  • Redirect the user to the social link account page if a related user account is found and social automatic account linking is disabled.
  • Show the register new account button on the social link account page.

@logto/integration-tests@1.9.0

Minor Changes

• 3d3a220: add support for additional first screen options

  This feature introduces new first screen options, allowing developers to customize the initial screen presented to users. In addition to the existing sign_in and register options, the following first screen choices are now supported:

  • identifier:sign_in: Only display specific identifier-based sign-in methods to users.
  • identifier:register: Only display specific identifier-based registration methods to users.
  • reset_password: Allow users to directly access the password reset page.
  • single_sign_on: Allow users to directly access the single sign-on (SSO) page.

  Example:

  // Example usage (React project using React SDK)
  void signIn({
    redirectUri,
    firstScreen: "identifier:sign_in",
    /**
     * Optional. Specifies which sign-in methods to display on the identifier sign-in page.
     * If not specified, the default sign-in experience configuration will be used.
     * This option is effective when the `firstScreen` value is `identifier:sign_in`, `identifier:register`, or `reset_password`.
     */
    identifiers: ["email", "phone"],
  });

Patch Changes

• cc346b4: add password policy checking api

  Add POST /api/sign-in-exp/default/check-password API to check if the password meets the password policy configured in the default sign-in experience. A user ID is required for this API if rejects user info is enabled in the password policy.

  Here's a non-normative example of the request and response:

  POST /api/sign-in-exp/default/check-password
  Content-Type: application/json
  
  {
    "password": "123",
    "userId": "some-user-id"
  }

  400 Bad Request
  Content-Type: application/json
  
  {
    "result": false,
    "issues": [
      { "code": "password_rejected.too_short" },
      { "code": "password_rejected.character_types" },
      { "code": "password_rejected.restricted.sequence" }
    ]
  }

@logto/demo-app@1.4.1

Patch Changes

• 3b9714b: set lang attribute for <html>
• fae8725: improve RTL language support

@logto/elements@0.0.1

Patch Changes

• fae8725: improve RTL language support

[github-actions]

COMPARE TO master

Total Size Diff ⚠️ 📈 +17.61 KB

Diff by File

Name	Diff
.changeset/brave-horses-knock.md	📈 +112 Bytes
.changeset/dry-candles-design.md	📈 +77 Bytes
.changeset/fast-adults-dream.md	📈 +798 Bytes
.changeset/fresh-shrimps-rhyme.md	📈 +478 Bytes
.changeset/friendly-rice-sell.md	📈 +87 Bytes
.changeset/funny-goats-tap.md	📈 +1.79 KB
.changeset/hip-cats-destroy.md	📈 +111 Bytes
.changeset/nine-vans-whisper.md	📈 +1.18 KB
.changeset/pink-baboons-mix.md	📈 +66 Bytes
.changeset/polite-bats-learn.md	📈 +80 Bytes
.changeset/popular-monkeys-complain.md	📈 +539 Bytes
.changeset/proud-baboons-hope.md	📈 +68 Bytes
.changeset/proud-books-itch.md	📈 +1.68 KB
.changeset/quiet-penguins-join.md	📈 +119 Bytes
.changeset/rare-moons-unite.md	📈 +342 Bytes
.changeset/rare-poems-happen.md	📈 +160 Bytes
.changeset/selfish-kangaroos-perform.md	📈 +786 Bytes
.changeset/silly-hotels-greet.md	📈 +849 Bytes
.changeset/spicy-cameras-sleep.md	📈 +565 Bytes
.changeset/tiny-fishes-bake.md	📈 +942 Bytes
.changeset/violet-beds-yawn.md	📈 +78 Bytes
.changeset/witty-rivers-laugh.md	📈 +525 Bytes
.changeset/yellow-yaks-bathe.md	📈 +802 Bytes
.changeset/young-moons-deny.md	📈 +109 Bytes
packages/cli/CHANGELOG.md	📈 +995 Bytes
packages/cli/package.json	0 Bytes
packages/connectors/connector-gitlab/CHANGELOG.md	📈 +929 Bytes
packages/connectors/connector-gitlab/package.json	0 Bytes
packages/connectors/connector-kook/CHANGELOG.md	📈 +181 Bytes
packages/connectors/connector-kook/package.json	0 Bytes
packages/connectors/connector-oauth2/CHANGELOG.md	📈 +80 Bytes
packages/connectors/connector-oauth2/package.json	0 Bytes
packages/connectors/connector-patreon/CHANGELOG.md	📈 +917 Bytes
packages/connectors/connector-patreon/package.json	0 Bytes
packages/connectors/connector-wecom/CHANGELOG.md	📈 +113 Bytes
packages/connectors/connector-wecom/package.json	0 Bytes
packages/console/CHANGELOG.md	📈 +2.58 KB
packages/console/package.json	0 Bytes
packages/core/CHANGELOG.md	📈 +6.99 KB
packages/core/package.json	0 Bytes
packages/create/CHANGELOG.md	📈 +88 Bytes
packages/create/package.json	0 Bytes
packages/demo-app/CHANGELOG.md	📈 +119 Bytes
packages/demo-app/package.json	0 Bytes
packages/elements/CHANGELOG.md	📈 +90 Bytes
packages/elements/package.json	0 Bytes
packages/experience-legacy/CHANGELOG.md	📈 +1.68 KB
packages/experience-legacy/package.json	0 Bytes
packages/experience/CHANGELOG.md	📈 +4.18 KB
packages/experience/package.json	0 Bytes
packages/integration-tests/CHANGELOG.md	📈 +1.97 KB
packages/integration-tests/package.json	0 Bytes
packages/phrases-experience/CHANGELOG.md	📈 +84 Bytes
packages/phrases-experience/package.json	0 Bytes
packages/phrases/CHANGELOG.md	📈 +1.88 KB
packages/phrases/package.json	0 Bytes
packages/schemas/CHANGELOG.md	📈 +2.47 KB
packages/schemas/alterations/1.20.0-1723448981-personal-access-tokens.ts	📈 +1.16 KB
packages/schemas/alterations/1.20.0-1724229102-add-report-sub-updates-cloud-scope.ts	📈 +2.91 KB
packages/schemas/alterations/1.20.0-1724316971-add-verified-identifier-to-verification-statuses.ts	📈 +468 Bytes
packages/schemas/alterations/1.20.0-1725971571-add-verification-record.ts	📈 +1.1 KB
packages/schemas/alterations/next-1723448981-personal-access-tokens.ts	📈 +1.16 KB
packages/schemas/alterations/next-1724229102-add-report-sub-updates-cloud-scope.ts	📈 +2.91 KB
packages/schemas/alterations/next-1724316971-add-verified-identifier-to-verification-statuses.ts	📈 +468 Bytes
packages/schemas/alterations/next-1725971571-add-verification-record.ts	📈 +1.1 KB
packages/schemas/package.json	0 Bytes
packages/translate/CHANGELOG.md	📈 +1.02 KB
packages/translate/package.json	0 Bytes
pnpm-lock.yaml	📈 +3.48 KB