[pull] main from lobehub:main

[pull]

See Commits and Changes for more details.

---

Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

[cr-gpt]

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request introduces a minor bug fix to allow the use of email as a name in the Logto authentication provider. The changes are implemented in the CHANGELOG.md file to document the new version 1.22.2 and in the src/libs/next-auth/sso-providers/logto.ts file to modify the user profile mapping.

Class diagram for Logto authentication provider changes

classDiagram
    class LogtoProfile {
        +String email
        +String sub
        +String picture
        +String name
        +String username
    }
    class OIDCUserConfig {
        +LogtoProfile profile
    }
    class OIDCConfig {
        +String email
        +String id
        +String image
        +String name
        +String providerAccountId
    }
    OIDCUserConfig --> LogtoProfile
    OIDCConfig --> OIDCUserConfig
    note for OIDCConfig "Updated to use email as name if name and username are not available"

Loading

File-Level Changes

Change	Details	Files
Allow using email as name in Logto authentication	Add fallback to use email as name if name and username are not available Update user profile mapping in LobeLogtoProvider function	src/libs/next-auth/sso-providers/logto.ts
Update CHANGELOG.md for version 1.22.2	Add new section for version 1.22.2 Document the bug fix for using email as name in Logto Include link to the related issue (🐛 fix: allow use email as name in logto lobehub/lobe-chat#4350)	CHANGELOG.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, pull[bot]!). We assume it knows what it's doing!