chore(deps): update svhd/logto docker tag to v1.35.0 #6078
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.34.0→1.35.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
logto-io/logto (svhd/logto)
v1.35.0Compare Source
Highlights
recaptcha.netfor regions where the default domain may be blocked.New features & enhancements
reCAPTCHA improvements
Domain customization
You can now customize the domain for reCAPTCHA. This is particularly useful for users in regions where the default
google.com/recaptchadomain may be inaccessible, allowing them to use alternatives likerecaptcha.net.Enterprise checkbox mode
You can now choose between two verification modes for reCAPTCHA Enterprise:
Note: The verification mode must match your reCAPTCHA key type configured in Google Cloud Console.
Third-party SPA & Native applications
Previously, only traditional web applications could be marked as third-party apps. Now you can also create third-party single-page applications (SPA) and native applications, enabling more flexible OAuth/OIDC integration scenarios.
Client IP in passwordless connector payload
The
SendMessageDatatype now includes an optionalipfield that contains the client IP address of the user who triggered the message. This can be used by HTTP email/SMS connectors for:Email/SMS template fallback
Email and SMS connectors now fall back to
TemplateType.Genericif a usage-specific template is not found. Additionally, the email template retrieval logic will also attempt to retrieve thegenerictemplate with default locale if both the locale-specific and fallback templates are unavailable.Bug fixes & stability
SAML relay state length fix
The data type of the
relay_statecolumn in thesaml_application_sessionstable has been changed fromvarchar(256)tovarchar(512)to accommodate longer Relay State values. This fix enables Firebase integration with Logto as a Service Provider, which previously failed due to relay state length constraints (approximately 300-400 characters).Additionally, error handling logic in SAML authentication flow APIs has been improved to provide more straightforward error messages.
SAML app creation API parameter fix
Fixed the API parameter naming from "type" to "types" for SAML app creation, ensuring the filter works correctly and paywall calculations are accurate.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.