Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: lobehub/lobe-chat
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.104.5
Choose a base ref
...
head repository: lobehub/lobe-chat
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.105.0
Choose a head ref
  • 3 commits
  • 26 files changed
  • 3 contributors

Commits on Jul 28, 2025

  1. Configuration menu
    Copy the full SHA
    7d85151 View commit details
    Browse the repository at this point in the history
  2. ✨ feat: Implement API Key management functionality (#8535)

    * ✨ feat: Implement API Key management functionality
    
    - Added new components for API Key management including creation, deletion, and display.
    - Introduced a new database schema for storing API Keys.
    - Implemented server and client services for API Key operations.
    - Integrated API Key management into the profile section with appropriate routing and feature flags.
    - Enhanced localization support for API Key related UI elements.
    
    This commit lays the groundwork for managing API Keys within the application, allowing users to create, view, and manage their keys effectively.
    
    * fix: server config unit test
    
    * ✨ feat(database): Create api_keys table with conditional existence check
    
    - Added a conditional check to create the "api_keys" table only if it does not already exist.
    - Ensured the foreign key constraint for "user_id" references the "users" table remains intact.
    
    This change enhances the migration process by preventing errors during table creation if the table already exists.
    
    * feat: Implement API Key management interface
    
    - Introduced a new Client component for managing API keys, including creation, updating, and deletion functionalities.
    - Replaced the previous page component with the new Client component in the API key management page.
    - Removed obsolete client and server service files related to API key management, streamlining the service layer.
    
    This update enhances the user experience by providing a dedicated interface for API key operations.
    MarioJames authored Jul 28, 2025
    Configuration menu
    Copy the full SHA
    fdaa725 View commit details
    Browse the repository at this point in the history
  3. 🔖 chore(release): v1.105.0 [skip ci]

    ## [Version 1.105.0](v1.104.5...v1.105.0)
    <sup>Released on **2025-07-28**</sup>
    
    #### ✨ Features
    
    - **misc**: Implement API Key management functionality.
    
    <br/>
    
    <details>
    <summary><kbd>Improvements and Fixes</kbd></summary>
    
    #### What's improved
    
    * **misc**: Implement API Key management functionality, closes [#8535](#8535) ([fdaa725](fdaa725))
    
    </details>
    
    <div align="right">
    
    [![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
    
    </div>
    semantic-release-bot committed Jul 28, 2025
    Configuration menu
    Copy the full SHA
    7bab44e View commit details
    Browse the repository at this point in the history
Loading