Skip to content

release: version packages - #9972

Open
silverhand-bot wants to merge 1 commit into
masterfrom
changeset-release/master
Open

silverhand-bot wants to merge 1 commit into
masterfrom
changeset-release/master

Conversation

@silverhand-bot

@silverhand-bot silverhand-bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Collaborator

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-amazon@0.4.0

Minor Changes

  • 51564b0: add a disableEmailSync switch to the Amazon connector

    The connector always synced the email field returned by Amazon to the user profile. This switch makes that configurable, matching the control the Microsoft Azure AD and standard OAuth2 connectors already offer. It is off by default, so existing connectors keep their current behavior.

@logto/connector-dingtalk-web@0.5.0

Minor Changes

  • 51564b0: add a disableEmailSync switch to the DingTalk web connector

    The connector always synced the email field returned by DingTalk to the user profile. This switch makes that configurable, matching the control the Microsoft Azure AD and standard OAuth2 connectors already offer. It is off by default, so existing connectors keep their current behavior.

@logto/connector-facebook@1.7.0

Minor Changes

  • 51564b0: add a disableEmailSync switch to the Facebook connector

    The connector always synced the email field returned by Facebook to the user profile. This switch makes that configurable, matching the control the Microsoft Azure AD and standard OAuth2 connectors already offer. It is off by default, so existing connectors keep their current behavior.

@logto/connector-feishu-web@1.5.0

Minor Changes

  • 51564b0: add a disableEmailSync switch to the Feishu web connector

    The connector always synced the email field returned by Feishu to the user profile. This switch makes that configurable, matching the control the Microsoft Azure AD and standard OAuth2 connectors already offer. It is off by default, so existing connectors keep their current behavior.

@logto/connector-naver@1.5.0

Minor Changes

  • 51564b0: add a disableEmailSync switch to the Naver connector

    The connector always synced the email field returned by Naver to the user profile. This switch makes that configurable, matching the control the Microsoft Azure AD and standard OAuth2 connectors already offer. It is off by default, so existing connectors keep their current behavior.

@logto/connector-saml@1.4.0

Minor Changes

  • 51564b0: add a disableEmailSync switch to the SAML connector

    The connector always synced the attribute that Profile Mapping maps to email to the user profile. This switch makes that configurable, matching the control the Microsoft Azure AD and standard OAuth2 connectors already offer. It is off by default, so existing connectors keep their current behavior.

@logto/connector-wecom@0.7.0

Minor Changes

  • 51564b0: add a disableEmailSync switch to the WeCom connector

    The connector always synced the email field returned by WeCom to the user profile. This switch makes that configurable, matching the control the Microsoft Azure AD and standard OAuth2 connectors already offer. It is off by default, so existing connectors keep their current behavior.

@logto/phrases@1.34.0

Minor Changes

  • 70a58d3: show a friendly error page when an OIDC error can't be sent back to the app

    When a browser hits an OIDC error that can't safely be redirected back to the app, such as a redirect_uri that isn't registered or an unknown client_id, it now sees a localized page in the style of the sign-in experience instead of raw JSON. Developers can expand "Error details" to see the error response. API clients keep receiving the same JSON.

  • 450fa7d: add a refresh token lifetime setting for dynamic apps

    Dynamic app (client ID metadata document) clients previously always used the default 14-day refresh token lifetime, so users had to sign in again every 14 days. Set "Refresh token time to live (TTL) in days" in the dynamic app settings, from 1 to 180 days, to apply one lifetime to all dynamic app clients. Changes apply to the next token issued.

    The lifetime is now fixed from the first issuance for every dynamic app client: rotating a refresh token keeps its original expiration. Previously, dynamic app clients declaring application_type: native or a token endpoint authentication method other than none got a fresh lifetime on every refresh, up to 180 days; their users now sign in again once the configured lifetime ends.

  • f101e4b: add a tenant setting to turn off the "Add another 2-step verification" suggestion

    When a user's only MFA factor is the email, phone number, or passkey they also sign in with, Logto suggests adding another factor during sign-up or sign-in. Turn off "Suggest adding another MFA factor" in Console > Multi-factor authentication > Policy, or set mfa.skipAdditionalBindingSuggestion to true in the sign-in experience, to never show this suggestion. Required MFA set-up, backup codes, and passkey prompts are not affected.

  • 93d3f39: report self-hosted license usage and warn in Console when usage exceeds plan limits

    Self-hosted deployments with an active license evaluate usage locally, warn in Console when limits are exceeded without blocking features, and include aggregated usage counts in license refreshes unless SELF_HOSTED_LICENSE_USAGE_REPORTING_DISABLED=1 is set on every Core instance.

Patch Changes

  • 1838646: use dedicated i18n error codes for organization invitation validation errors

    Organization invitation creation and status update errors now return specific, localized codes under the organization namespace instead of the generic request.invalid_input, so clients can reliably distinguish each failure case and messages render in the user's language. HTTP status codes are unchanged.

    If your integration matches request.invalid_input for these responses, update it to match the new codes:

    • POST /api/organization-invitations
      • organization.expires_at_in_future (400): the value of expiresAt is not in the future.
      • organization.invitee_already_member (422): the invitee is already a member of the organization.
    • PUT /api/organization-invitations/{id}/status
      • organization.invitation_status_not_changeable (422): the invitation is no longer pending.
      • organization.accepted_user_id_required (422): acceptedUserId is missing when accepting.
      • organization.accepted_user_email_mismatch (422): the accepted user's primary email does not match the invitee.
  • dfbe3d0: delete log rows older than a given timestamp through the Management API

    DELETE /api/logs takes an end_time boundary, an optional start_time boundary, and a limit. Both boundaries are unix timestamps in milliseconds with the same inclusive semantics as GET /api/logs; limit defaults to 1000 and is capped at 10000. Each call deletes at most limit log rows, webhook delivery logs included, and reports hasMore, so operators can loop it to purge a large backlog while keeping every request bounded.

@logto/schemas@1.47.0

Minor Changes

  • f2caf27: support per-organization role assignments in one-time token context

  • 0567ce3: support migrating MFA factors in the post first-factor verification action

    The action result now accepts an optional mfaVerifications field to carry over TOTP, backup codes, and WebAuthn factors when a user is migrated just in time. Migrated factors are challenged in the same sign-in when MFA is required. A factor identical to an existing one is skipped, and a conflicting factor fails the sign-in instead of being replaced.

  • 450fa7d: add a refresh token lifetime setting for dynamic apps

    Dynamic app (client ID metadata document) clients previously always used the default 14-day refresh token lifetime, so users had to sign in again every 14 days. Set "Refresh token time to live (TTL) in days" in the dynamic app settings, from 1 to 180 days, to apply one lifetime to all dynamic app clients. Changes apply to the next token issued.

    The lifetime is now fixed from the first issuance for every dynamic app client: rotating a refresh token keeps its original expiration. Previously, dynamic app clients declaring application_type: native or a token endpoint authentication method other than none got a fresh lifetime on every refresh, up to 180 days; their users now sign in again once the configured lifetime ends.

  • f101e4b: add a tenant setting to turn off the "Add another 2-step verification" suggestion

    When a user's only MFA factor is the email, phone number, or passkey they also sign in with, Logto suggests adding another factor during sign-up or sign-in. Turn off "Suggest adding another MFA factor" in Console > Multi-factor authentication > Policy, or set mfa.skipAdditionalBindingSuggestion to true in the sign-in experience, to never show this suggestion. Required MFA set-up, backup codes, and passkey prompts are not affected.

  • 93d3f39: report self-hosted license usage and warn in Console when usage exceeds plan limits

    Self-hosted deployments with an active license evaluate usage locally, warn in Console when limits are exceeded without blocking features, and include aggregated usage counts in license refreshes unless SELF_HOSTED_LICENSE_USAGE_REPORTING_DISABLED=1 is set on every Core instance.

  • 34d5ffc: widen tenants.id and every tenant-ID-bearing column (118 columns across 78 tables) to varchar(64)

    The widening runs online: catalog-only alter statements under briefly-held, timeout-bounded locks, with the dependent check constraints re-validated without blocking writes and no table data rewritten. To keep the migration bounded, the large partial and expression indexes on logs, oidc_model_instances, users, and service_logs are dropped, with temporary covering indexes standing in until follow-up releases rebuild the live ones concurrently; eight legacy expression indexes that row-level security already made unusable for tenant queries are removed for good. The maximum length of a custom tenant ID is unchanged in this release.

Patch Changes

  • 59f7e27: record why Logto rejected an action result in the action audit log

    When a post first-factor verification or post sign-in action returns a result that Logto does not accept, such as an invalid user patch, a malformed migrated MFA factor, a changed sign-in identifier, or an identity conflict, the action audit log entry is now marked as an error and carries a validation field with the rejection reason. It names the failing field paths, or the index, type, and reason of the rejected MFA factor, and never includes values from the result such as secrets or backup codes. Accepted results are recorded with validation: { outcome: 'accepted' }.

  • e1f121e: fix S3 file uploads to buckets with ACLs disabled by supporting isPublic: false in storage provider configuration

  • 805da84: prevent users who are required to use MFA from turning off MFA verification on sign-in

    Users who are required to use MFA by an admin or by an organization that requires MFA are now always asked for MFA verification on sign-in, even if they previously turned off 2-step verification. The Account Center hides the 2-step verification toggle for these users, and GET /api/my-account/mfa-settings returns a new required field that indicates whether MFA verification on sign-in is required for the user.

  • Updated dependencies [70a58d3]

  • Updated dependencies [1838646]

  • Updated dependencies [450fa7d]

  • Updated dependencies [dfbe3d0]

  • Updated dependencies [f101e4b]

  • Updated dependencies [93d3f39]

    • @logto/phrases@1.34.0

@logto/cli@1.47.0

Patch Changes

@logto/connector-aws-ses@1.5.7

Patch Changes

  • 7eca559: honor sendFrom and replyTo of the i18n email template

    With a custom i18n email template, the AWS SES connector always sent from the configured emailAddress and ignored the template's sendFrom and replyTo. It now uses them (with handlebars replaced), like the SMTP and SendGrid connectors; without them, the behavior is unchanged.

@logto/connector-sendgrid-email@1.5.7

Patch Changes

  • 766e954: honor sendFrom and replyTo of the i18n email template

    With a custom i18n template, the SendGrid connector put the configured sender name on the recipient and dropped it from from, and ignored the template's replyTo. The recipient is now addressed by email only, from.name comes from the template's sendFrom (falling back to the configured fromName), and reply_to is set from the template's replyTo.

@logto/connector-smtp@1.5.7

Patch Changes

  • 585dfd8: validate SMTP connector config before creating the transport

    The connector now gives nodemailer only the options its config declares, so any other keys in a stored or tested config are ignored when sending, as is path under tls. Configs that use declared options keep working, including implicit TLS on port 465 when secure is not set. The config also declares dkim with domainName, keySelector and privateKey: other keys under dkim are ignored, and a dkim object missing any of the three fails validation.

@logto/create@1.47.0

Patch Changes

  • @logto/cli@1.47.0

@logto/api@1.47.0

@logto/console@1.44.0

Minor Changes

  • 450fa7d: add a refresh token lifetime setting for dynamic apps

    Dynamic app (client ID metadata document) clients previously always used the default 14-day refresh token lifetime, so users had to sign in again every 14 days. Set "Refresh token time to live (TTL) in days" in the dynamic app settings, from 1 to 180 days, to apply one lifetime to all dynamic app clients. Changes apply to the next token issued.

    The lifetime is now fixed from the first issuance for every dynamic app client: rotating a refresh token keeps its original expiration. Previously, dynamic app clients declaring application_type: native or a token endpoint authentication method other than none got a fresh lifetime on every refresh, up to 180 days; their users now sign in again once the configured lifetime ends.

  • f101e4b: add a tenant setting to turn off the "Add another 2-step verification" suggestion

    When a user's only MFA factor is the email, phone number, or passkey they also sign in with, Logto suggests adding another factor during sign-up or sign-in. Turn off "Suggest adding another MFA factor" in Console > Multi-factor authentication > Policy, or set mfa.skipAdditionalBindingSuggestion to true in the sign-in experience, to never show this suggestion. Required MFA set-up, backup codes, and passkey prompts are not affected.

  • 93d3f39: report self-hosted license usage and warn in Console when usage exceeds plan limits

    Self-hosted deployments with an active license evaluate usage locally, warn in Console when limits are exceeded without blocking features, and include aggregated usage counts in license refreshes unless SELF_HOSTED_LICENSE_USAGE_REPORTING_DISABLED=1 is set on every Core instance.

Patch Changes

  • 02549b2: fix redirect URI mismatches caused by the Console decoding URIs on save

    The Console percent-decoded redirect URIs and post sign-out redirect URIs when saving application settings, so https://example.com/a%2Fb was stored as https://example.com/a/b and no longer matched the URI sent by the client. These URIs are now saved exactly as entered.

    CORS allowed origins are no longer percent-decoded either, and a literal % in any of these fields, such as https://example.com/100%, no longer causes the save to fail. Trailing slashes are still removed from CORS allowed origins.

  • 9d694fd: fix the delete button for uploaded files in SAML enterprise SSO connector settings

    Clicking the delete icon next to an uploaded IdP metadata XML file or signing certificate on a SAML enterprise SSO connector now removes the file. Previously the file stayed in place.

@logto/core@1.47.0

Minor Changes

  • f2caf27: support per-organization role assignments in one-time token context

  • 70a58d3: show a friendly error page when an OIDC error can't be sent back to the app

    When a browser hits an OIDC error that can't safely be redirected back to the app, such as a redirect_uri that isn't registered or an unknown client_id, it now sees a localized page in the style of the sign-in experience instead of raw JSON. Developers can expand "Error details" to see the error response. API clients keep receiving the same JSON.

  • 0567ce3: support migrating MFA factors in the post first-factor verification action

    The action result now accepts an optional mfaVerifications field to carry over TOTP, backup codes, and WebAuthn factors when a user is migrated just in time. Migrated factors are challenged in the same sign-in when MFA is required. A factor identical to an existing one is skipped, and a conflicting factor fails the sign-in instead of being replaced.

  • 1838646: use dedicated i18n error codes for organization invitation validation errors

    Organization invitation creation and status update errors now return specific, localized codes under the organization namespace instead of the generic request.invalid_input, so clients can reliably distinguish each failure case and messages render in the user's language. HTTP status codes are unchanged.

    If your integration matches request.invalid_input for these responses, update it to match the new codes:

    • POST /api/organization-invitations
      • organization.expires_at_in_future (400): the value of expiresAt is not in the future.
      • organization.invitee_already_member (422): the invitee is already a member of the organization.
    • PUT /api/organization-invitations/{id}/status
      • organization.invitation_status_not_changeable (422): the invitation is no longer pending.
      • organization.accepted_user_id_required (422): acceptedUserId is missing when accepting.
      • organization.accepted_user_email_mismatch (422): the accepted user's primary email does not match the invitee.
  • 450fa7d: add a refresh token lifetime setting for dynamic apps

    Dynamic app (client ID metadata document) clients previously always used the default 14-day refresh token lifetime, so users had to sign in again every 14 days. Set "Refresh token time to live (TTL) in days" in the dynamic app settings, from 1 to 180 days, to apply one lifetime to all dynamic app clients. Changes apply to the next token issued.

    The lifetime is now fixed from the first issuance for every dynamic app client: rotating a refresh token keeps its original expiration. Previously, dynamic app clients declaring application_type: native or a token endpoint authentication method other than none got a fresh lifetime on every refresh, up to 180 days; their users now sign in again once the configured lifetime ends.

  • dfbe3d0: delete log rows older than a given timestamp through the Management API

    DELETE /api/logs takes an end_time boundary, an optional start_time boundary, and a limit. Both boundaries are unix timestamps in milliseconds with the same inclusive semantics as GET /api/logs; limit defaults to 1000 and is capped at 10000. Each call deletes at most limit log rows, webhook delivery logs included, and reports hasMore, so operators can loop it to purge a large backlog while keeping every request bounded.

  • f101e4b: add a tenant setting to turn off the "Add another 2-step verification" suggestion

    When a user's only MFA factor is the email, phone number, or passkey they also sign in with, Logto suggests adding another factor during sign-up or sign-in. Turn off "Suggest adding another MFA factor" in Console > Multi-factor authentication > Policy, or set mfa.skipAdditionalBindingSuggestion to true in the sign-in experience, to never show this suggestion. Required MFA set-up, backup codes, and passkey prompts are not affected.

  • 93d3f39: report self-hosted license usage and warn in Console when usage exceeds plan limits

    Self-hosted deployments with an active license evaluate usage locally, warn in Console when limits are exceeded without blocking features, and include aggregated usage counts in license refreshes unless SELF_HOSTED_LICENSE_USAGE_REPORTING_DISABLED=1 is set on every Core instance.

  • 006a765: export WebAuthn credentials from the user MFA verifications Management API

    GET /api/users/{userId}/mfa-verifications now accepts an includeWebAuthnCredentials query parameter. When it is provided with a truthy value (true, 1, yes), each WebAuthn verification includes its stored credential: credentialId, publicKey (base64url COSE), counter (signCount), transports, and rpId. These fields are omitted by default, so existing callers get the same response. Tenants can use them to migrate passkeys on the same domain. The user binding is the path userId, whose UTF-8 bytes Logto registers as the WebAuthn userHandle. The parameter is also honored under read-only access, since a WebAuthn public key and credential ID cannot be used to sign in. The Account API response is unchanged.

Patch Changes

  • 59f7e27: record why Logto rejected an action result in the action audit log

    When a post first-factor verification or post sign-in action returns a result that Logto does not accept, such as an invalid user patch, a malformed migrated MFA factor, a changed sign-in identifier, or an identity conflict, the action audit log entry is now marked as an error and carries a validation field with the rejection reason. It names the failing field paths, or the index, type, and reason of the rejected MFA factor, and never includes values from the result such as secrets or backup codes. Accepted results are recorded with validation: { outcome: 'accepted' }.

  • e1f121e: fix S3 file uploads to buckets with ACLs disabled by supporting isPublic: false in storage provider configuration

  • 0049b89: issue access tokens with only the API resource permissions that still exist

    When an app exchanged an authorization code or a device code for an access token for an API resource, the token could still include permissions (scopes) that had been removed from that API resource after the user granted them. Logto now issues these tokens, both opaque and JWT, with only the granted permissions that the API resource still has. If all of them have been removed, the token's scope is empty. The refresh token grant already behaved this way.

  • 51ca514: accept empty display URLs in client ID metadata documents

    Some MCP clients that use a client ID metadata document (CIMD) set the optional client_uri, policy_uri, tos_uri, or logo_uri properties to an empty string. Logto rejected these documents before the authorization flow started. Logto now treats these empty values as omitted. Non-empty invalid URLs are still rejected.

  • 4885ab7: handle social identity targets that contain special characters

  • bab5464: return 400 instead of 500 when a Management API request contains a NUL character

    A NUL character (\u0000 in a JSON body or %00 in a query or path) in a text value, for example GET /api/users?search=%00 or POST /api/roles with a name containing \u0000, made PostgreSQL reject the query with invalid byte sequence for encoding "UTF8": 0x00 and the API responded with 500 Internal server error. It now responds with 400 request.invalid_input.

  • c5399e3: sign in a SAML SSO user only through the connector that linked their identity

    An enterprise SSO identity linked through a SAML connector no longer signs in through a different connector that reports the same IdP entity ID. That sign-in now fails with user.enterprise_sso_identity_not_exists. OIDC connectors are unchanged. If two SAML connectors in a tenant use the same IdP entity ID, each user keeps signing in through the connector they were first linked through.

  • 7ba0206: count email and phone MFA factors when issuing organization tokens for organizations that require MFA

    Users whose only MFA factor is the email verification code or SMS verification code enabled in the sign-in experience were always denied organization tokens for organizations that require MFA, even after completing MFA at sign-in. Organization token issuance now uses the same MFA factors as sign-in, and the Console's tenant MFA status and list of members without MFA follow the same rule.

    This also means MFA factors that are not enabled in the sign-in experience, and backup codes that have all been used, no longer count as configured MFA. Users in an organization that requires MFA whose only MFA is such a factor (for example, a TOTP added through the Management API while TOTP is not enabled, or a factor that was later disabled) are denied organization tokens until they set up an enabled MFA factor. With the organization MFA policy set to mandatory in the sign-in experience, they are asked to do so at their next sign-in.

  • 805da84: prevent users who are required to use MFA from turning off MFA verification on sign-in

    Users who are required to use MFA by an admin or by an organization that requires MFA are now always asked for MFA verification on sign-in, even if they previously turned off 2-step verification. The Account Center hides the 2-step verification toggle for these users, and GET /api/my-account/mfa-settings returns a new required field that indicates whether MFA verification on sign-in is required for the user.

  • 268be66: reject API resource indicators that are not valid URIs in POST /api/resources

    The Management API accepted any string as the indicator of a new API resource, for example not a uri, and saved it. The Console already requires a valid URI, and OIDC rejects authorization requests for a resource indicator that is not an absolute URI, so a resource created this way could never be requested. The API now responds with 400 guard.invalid_input instead.

  • 08b8a0e: emit one AttributeValue per item for multi-valued SAML attributes

    A mapped claim that holds an array, such as roles or organizations, was written into the SAML assertion as one JSON-encoded string (["Development","Employees"]). Service providers expect one saml:AttributeValue element per value, as the SAML core specification describes, so role-based rules on the SP side could not match. Each item is now emitted as its own AttributeValue.

    Object items, such as those of organization_data and sso_identities, stay JSON-encoded, one per AttributeValue.

    This changes the assertion shape for existing integrations. A service provider that parses the JSON-encoded string of an array claim now receives one AttributeValue per item and should read them as a list, and an empty array yields the attribute without a value instead of [].

  • 426f4dc: count every attempt at a verification code toward its retry limit, and accept a correct code from at most one request

    An attempt after the limit is reached gets verification_code.exceed_max_try, and any other request that presents a code already used gets verification_code.not_found.

  • 9b4106d: link enterprise SSO sign-ins to existing accounts by email only on the connector's email domains

    Upgrade note: an enterprise SSO sign-in is linked automatically to an existing account with the same email only when the email's domain is listed in the connector's "Enterprise email domains", so list every email domain the connector serves.

  • Updated dependencies [59f7e27]

  • Updated dependencies [e1f121e]

  • Updated dependencies [02549b2]

  • Updated dependencies [f2caf27]

  • Updated dependencies [70a58d3]

  • Updated dependencies [0567ce3]

  • Updated dependencies [1838646]

  • Updated dependencies [450fa7d]

  • Updated dependencies [dfbe3d0]

  • Updated dependencies [f101e4b]

  • Updated dependencies [805da84]

  • Updated dependencies [93d3f39]

  • Updated dependencies [9d694fd]

  • Updated dependencies [34d5ffc]

    • @logto/schemas@1.47.0
    • @logto/console@1.44.0
    • @logto/phrases@1.34.0
    • @logto/account@0.8.1
    • @logto/cli@1.47.0

@logto/account@0.8.1

Patch Changes

  • 805da84: prevent users who are required to use MFA from turning off MFA verification on sign-in

    Users who are required to use MFA by an admin or by an organization that requires MFA are now always asked for MFA verification on sign-in, even if they previously turned off 2-step verification. The Account Center hides the 2-step verification toggle for these users, and GET /api/my-account/mfa-settings returns a new required field that indicates whether MFA verification on sign-in is required for the user.

@github-actions github-actions Bot added the size/m label Nov 5, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from 14b3efa to e356b7c Compare November 5, 2026 06:42
@github-actions github-actions Bot added size/m and removed size/m labels Nov 5, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from e356b7c to 404d9cc Compare November 5, 2026 06:44
@github-actions github-actions Bot added size/m and removed size/m labels Nov 5, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from 404d9cc to 4f04b41 Compare November 5, 2026 06:44
@github-actions github-actions Bot added size/m and removed size/m labels Nov 5, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from 4f04b41 to 7e85e6c Compare November 5, 2026 06:47
@github-actions github-actions Bot added size/m and removed size/m labels Nov 5, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from 7e85e6c to c9a31ed Compare November 6, 2026 02:48
@github-actions github-actions Bot added size/m and removed size/m labels Nov 6, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from c9a31ed to 348a545 Compare November 8, 2026 15:14
@github-actions github-actions Bot added size/m and removed size/m labels Nov 8, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from 348a545 to 0d1d9bb Compare November 8, 2026 15:34
@github-actions github-actions Bot added size/m and removed size/m labels Nov 8, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from 0d1d9bb to 9f59ca3 Compare November 9, 2026 02:51
@github-actions github-actions Bot removed the size/m label Nov 9, 2026
@github-actions github-actions Bot added size/l and removed size/l labels Nov 9, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from 0224251 to 4f5ce20 Compare November 9, 2026 06:10
@github-actions github-actions Bot added size/l and removed size/l labels Nov 9, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from 4f5ce20 to f4fc580 Compare November 9, 2026 06:11
@github-actions github-actions Bot added size/l and removed size/l labels Nov 9, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from f4fc580 to 9ddeb23 Compare November 9, 2026 07:35
@github-actions github-actions Bot added size/l and removed size/l labels Nov 9, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from 9ddeb23 to c92d700 Compare November 9, 2026 07:49
@github-actions github-actions Bot added size/l and removed size/l labels Nov 9, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from c92d700 to b00443e Compare November 9, 2026 08:09
@github-actions github-actions Bot added size/l and removed size/l labels Nov 9, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from b00443e to 0c623ee Compare November 10, 2026 01:57
@github-actions github-actions Bot added size/l and removed size/l labels Nov 10, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from 0c623ee to 16417ca Compare November 10, 2026 05:25
@github-actions github-actions Bot added size/l and removed size/l labels Nov 10, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from 16417ca to 205cafb Compare November 10, 2026 05:34
@github-actions github-actions Bot added size/l and removed size/l labels Nov 10, 2026
@silverhand-bot
silverhand-bot force-pushed the changeset-release/master branch from 205cafb to 02c350d Compare November 10, 2026 12:24
@github-actions github-actions Bot added size/l and removed size/l labels Nov 10, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

1 participant