Skip to content

✨ feat: add server version check for desktop app#11710

Merged
Innei merged 5 commits intonextfrom
feat/server-version-check
Jan 22, 2026
Merged

✨ feat: add server version check for desktop app#11710
Innei merged 5 commits intonextfrom
feat/server-version-check

Conversation

@Innei
Copy link
Copy Markdown
Member

@Innei Innei commented Jan 22, 2026

💻 Change Type

  • ✨ feat

🔗 Related Issue

🔀 Description of Change

This PR adds server version compatibility check for the desktop app:

  • Server Version API: Consume /api/version endpoint to get server version
  • Version State Management: Add serverVersion and isServerVersionOutdated states to global store
  • Compatibility Check Hook: Add useCheckServerVersion hook with:
    • Detection when API doesn't exist (old server)
    • Version diff threshold (5 versions) for compatibility
  • Alert UI: Show ServerVersionOutdatedAlert modal when server is incompatible
  • Settings Display: Show server version tag in About page when different from client

The desktop app client is not compatible with old server versions. When detected:

  1. API returns 404 → Server too old
  2. Client version > Server version by 5+ patches → Server needs update

🧪 How to Test

  • Tested locally
  • Added/updated tests
  • No tests needed
  1. Run desktop app connected to an old server (without /api/version endpoint)
  2. Should see the outdated server alert
  3. Or test with server version much lower than client version

📸 Screenshots / Videos

📝 Additional Information

This feature is only active in desktop app environment (isDesktop === true).

Summary by Sourcery

Add server version compatibility checks to the desktop app and surface warnings when the connected server is too old.

New Features:

  • Introduce a server version compatibility check hook that queries the backend /api/version endpoint and computes version drift against the client.
  • Display a server version tag on the About page when the server version differs from the client in desktop environments.
  • Show a blocking server-outdated alert in the desktop app when the connected server is missing the version API or falls behind the client beyond a defined threshold.

Enhancements:

  • Extend global state and initialization logic to track server version metadata and whether the server is considered outdated.
  • Add localized copy for server version mismatch alerts and server version display in existing i18n dictionaries.

- Add /api/version endpoint consumption in globalService
- Add serverVersion and isServerVersionOutdated states to global store
- Add useCheckServerVersion hook to detect outdated server
- Show ServerVersionOutdatedAlert when server version is incompatible
- Display server version tag in settings when different from client
- Support version diff threshold (5 versions) for compatibility check
@dosubot dosubot bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Jan 22, 2026
@vercel
Copy link
Copy Markdown

vercel bot commented Jan 22, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
lobehub Canceled Canceled Jan 22, 2026 4:17pm

Request Review

@sourcery-ai
Copy link
Copy Markdown
Contributor

sourcery-ai bot commented Jan 22, 2026

Reviewer's Guide

Adds a desktop-only server version compatibility check: fetches /api/version, stores and compares server/client versions in global state, and shows a blocking alert and About-page tag when the server is too old or missing the version API.

Sequence diagram for desktop server version compatibility check

sequenceDiagram
  actor User
  participant DesktopApp
  participant StoreInitialization
  participant GlobalStore
  participant GlobalService
  participant Server
  participant AlertUI as ServerVersionOutdatedAlert

  User->>DesktopApp: Launch desktop app
  DesktopApp->>StoreInitialization: Render StoreInitialization
  StoreInitialization->>GlobalStore: useInitSystemStatus()
  StoreInitialization->>GlobalStore: useCheckServerVersion(isDesktop)
  activate GlobalStore
  GlobalStore->>GlobalService: getServerVersion()
  activate GlobalService
  GlobalService->>Server: GET /api/version
  alt Server supports /api/version and is compatible
    Server-->>GlobalService: 200 { version }
    GlobalService-->>GlobalStore: version string
    GlobalStore-->>GlobalStore: set serverVersion
    GlobalStore-->>DesktopApp: isServerVersionOutdated = false
    DesktopApp->>AlertUI: Render
    AlertUI-->>DesktopApp: Returns null (not shown)
  else Server too old or version too low
    Server-->>GlobalService: 404 or 200 { old version }
    GlobalService-->>GlobalStore: null or old version
    GlobalStore-->>GlobalStore: set isServerVersionOutdated = true
    GlobalStore-->>DesktopApp: isServerVersionOutdated = true
    DesktopApp->>AlertUI: Render
    AlertUI-->>User: Show outdated server modal
  end
  deactivate GlobalService
  deactivate GlobalStore
Loading

Sequence diagram for About page server version display

sequenceDiagram
  actor User
  participant AboutPage as AboutVersionComponent
  participant GlobalStore
  participant VersionHook as useCheckServerVersion
  participant GlobalService
  participant Server

  User->>AboutPage: Open Settings → About
  AboutPage->>GlobalStore: select latestVersion, serverVersion, useCheckServerVersion
  AboutPage->>VersionHook: useCheckServerVersion(isDesktop)
  activate VersionHook
  VersionHook->>GlobalService: getServerVersion()
  GlobalService->>Server: GET /api/version
  Server-->>GlobalService: 200 { version } or 404
  GlobalService-->>VersionHook: version or null
  VersionHook-->>GlobalStore: set serverVersion or isServerVersionOutdated
  deactivate VersionHook
  GlobalStore-->>AboutPage: serverVersion
  alt serverVersion exists and != CURRENT_VERSION
    AboutPage-->>User: Render client Tag vCURRENT_VERSION and server Tag v{serverVersion}
  else No serverVersion or same as client
    AboutPage-->>User: Render only client Tag vCURRENT_VERSION
  end
Loading

Updated class diagram for global server version state and service

classDiagram
  class GlobalState {
    <<interface>>
    +DatabaseLoadingState initClientDBStage
    +boolean isMobile
    +boolean isServerVersionOutdated
    +boolean isStatusInit
    +string latestVersion
    +NavigateFunction navigate
    +string serverVersion
    +SidebarTabKey sidebarKey
    +SystemStatus status
    +AsyncLocalStorage~SystemStatus~ statusStorage
  }

  class GlobalGeneralAction {
    <<interface>>
    +updateResourceManagerColumnWidth(column, width) void
    +updateSystemStatus(status, action) void
    +useCheckLatestVersion(enabledCheck) SWRResponse~string~
    +useCheckServerVersion(enabledCheck) SWRResponse~string_or_null~
    +useInitSystemStatus() SWRResponse
  }

  class GlobalService {
    +getLatestVersion() Promise~string~
    +getServerVersion() Promise~string_or_null~
    +getGlobalConfig() Promise~GlobalRuntimeConfig~
  }

  class BusinessGlobalService {
  }

  GlobalService --|> BusinessGlobalService
  GlobalGeneralAction --> GlobalState : updates
  GlobalGeneralAction --> GlobalService : calls getServerVersion

  class ServerVersionOutdatedAlert {
    +dismissed boolean
  }

  class GlobalStore {
    +boolean isServerVersionOutdated
    +string serverVersion
    +useCheckServerVersion(enabledCheck) SWRResponse~string_or_null~
  }

  GlobalStore --> GlobalService : getServerVersion
  ServerVersionOutdatedAlert --> GlobalStore : reads isServerVersionOutdated
Loading

File-Level Changes

Change Details Files
Add global hook and state for checking server version and marking it as outdated.
  • Extend global actions interface with useCheckServerVersion hook signature
  • Implement useCheckServerVersion using useOnlyFetchOnceSWR to call globalService.getServerVersion
  • On null response or large version gap, set isServerVersionOutdated in global store
  • Store serverVersion in global state when returned by server
src/store/global/actions/general.ts
src/store/global/initialState.ts
Introduce service method to retrieve server version from backend.
  • Define SERVER_VERSION_URL constant for /api/version
  • Implement getServerVersion that fetches URL, returns version string from JSON on 2xx, or null on errors/non-ok responses
src/services/global.ts
Wire server version check into app initialization and settings UI, and display server version when it differs from client.
  • Call useCheckServerVersion in StoreInitialization for desktop-only environment
  • In About Version component, subscribe to serverVersion and useCheckServerVersion, trigger check on desktop, and compute showServerVersion flag
  • Render server version Tag when present and different from CURRENT_VERSION
src/layout/GlobalProvider/StoreInitialization.tsx
src/app/[variants]/(main)/settings/about/features/Version.tsx
Add desktop-only modal alert for outdated server versions with upgrade CTA and dismiss option.
  • Create ServerVersionOutdatedAlert component that reads isServerVersionOutdated from global store and shows a styled warning overlay
  • Include alert in GlobalProvider wrapped with ClientOnly and guarded by isDesktop
  • Provide manual upgrade link and local-dismiss state so it does not re-render after dismiss
src/layout/GlobalProvider/ServerVersionOutdatedAlert.tsx
src/layout/GlobalProvider/index.tsx
Add i18n strings for server version warning and server version label in About page.
  • Define copy for serverVersionOutdated title, description, warning, upgrade button, and dismiss label
  • Add upgradeVersion.serverVersion translation for server version tag display
  • Ensure both default TS locale map and JSON locale files are updated
src/locales/default/common.ts
locales/en-US/common.json
locales/zh-CN/common.json

Possibly linked issues


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. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the 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 exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

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

@gru-agent
Copy link
Copy Markdown
Contributor

gru-agent bot commented Jan 22, 2026

TestGru Assignment

Summary

Link CommitId Status Reason
Detail bc53bb4 ✅ Finished

History Assignment

Files

File Pull Request
src/store/global/initialState.ts ❌ Failed (I failed to setup the environment.)
src/store/global/actions/general.ts ❌ Failed (I failed to setup the environment.)

Tip

You can @gru-agent and leave your feedback. TestGru will make adjustments based on your input

Copy link
Copy Markdown
Contributor

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 2 issues, and left some high level feedback:

  • The useCheckServerVersion hook is invoked both in StoreInitialization and in the About Version component for desktop, which is redundant given the useOnlyFetchOnceSWR behavior; consider centralizing this call (e.g., only during store initialization) to keep the flow simpler.
  • The version diff calculation comment table in useCheckServerVersion does not match the actual formula (e.g., 2.0.0 → 1.9.9 is shown as 91 but the formula yields 101); updating the examples to reflect the computation precisely would avoid confusion for future maintainers.
  • In getServerVersion, all non-OK responses and fetch errors are treated as 'old server' by returning null; if you need to distinguish between 'endpoint missing' and general server/network errors, consider checking specifically for 404 vs other status codes and handling them separately.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The `useCheckServerVersion` hook is invoked both in `StoreInitialization` and in the About `Version` component for desktop, which is redundant given the `useOnlyFetchOnceSWR` behavior; consider centralizing this call (e.g., only during store initialization) to keep the flow simpler.
- The version diff calculation comment table in `useCheckServerVersion` does not match the actual formula (e.g., 2.0.0 → 1.9.9 is shown as 91 but the formula yields 101); updating the examples to reflect the computation precisely would avoid confusion for future maintainers.
- In `getServerVersion`, all non-OK responses and fetch errors are treated as 'old server' by returning `null`; if you need to distinguish between 'endpoint missing' and general server/network errors, consider checking specifically for 404 vs other status codes and handling them separately.

## Individual Comments

### Comment 1
<location> `src/layout/GlobalProvider/ServerVersionOutdatedAlert.tsx:86-89` </location>
<code_context>
+const ServerVersionOutdatedAlert = () => {
+  const { styles } = useStyles();
+  const { t } = useTranslation('common');
+  const [dismissed, setDismissed] = useState(false);
+  const isServerVersionOutdated = useGlobalStore((s) => s.isServerVersionOutdated);
+
+  if (!isServerVersionOutdated || dismissed) return null;
+
+  return (
</code_context>

<issue_to_address>
**suggestion:** The dismissal state is not persisted, so the alert reappears on every reload.

Since `dismissed` is only local component state, the alert will reappear on every reload or new tab, even after “Continue Anyway” is selected. To avoid repeatedly interrupting users on long-lived outdated servers, consider persisting the dismissal (e.g., via localStorage or a global store flag keyed by version/session).

Suggested implementation:

```typescript
const SERVER_VERSION_OUTDATED_DISMISSED_KEY = 'serverVersionOutdated.dismissed';

const ServerVersionOutdatedAlert = () => {
  const { styles } = useStyles();
  const { t } = useTranslation('common');
  const [dismissed, setDismissed] = useState(false);
  const isServerVersionOutdated = useGlobalStore((s) => s.isServerVersionOutdated);

  useEffect(() => {
    try {
      const stored = window.localStorage.getItem(SERVER_VERSION_OUTDATED_DISMISSED_KEY);
      if (stored === 'true') {
        setDismissed(true);
      }
    } catch {
      // Ignore storage errors and fall back to non-persistent behavior
    }
  }, []);

  const handleDismiss = () => {
    try {
      window.localStorage.setItem(SERVER_VERSION_OUTDATED_DISMISSED_KEY, 'true');
    } catch {
      // Ignore storage errors; dismissal will still apply for this session
    }
    setDismissed(true);
  };

  if (!isServerVersionOutdated || dismissed) return null;

```

```typescript
        <div className={styles.closeButton} onClick={handleDismiss}>

```

1. Ensure `useEffect` is imported from React at the top of this file, e.g. update the existing React import to: `import React, { useEffect, useState } from 'react';` (or equivalent based on current import style).
2. If the project prefers a version-aware dismissal (i.e. reset when server version changes), you can extend this by incorporating the server version into `SERVER_VERSION_OUTDATED_DISMISSED_KEY` (e.g., `serverVersionOutdated.dismissed.${version}`) once the version is available in this component.
</issue_to_address>

### Comment 2
<location> `src/app/[variants]/(main)/settings/about/features/Version.tsx:19-30` </location>
<code_context>
 const Version = memo<{ mobile?: boolean }>(({ mobile }) => {
   const hasNewVersion = useNewVersion();
-  const [latestVersion] = useGlobalStore((s) => [s.latestVersion]);
+  const [latestVersion, serverVersion, useCheckServerVersion] = useGlobalStore((s) => [
+    s.latestVersion,
+    s.serverVersion,
+    s.useCheckServerVersion,
+  ]);
   const { t } = useTranslation('common');

+  useCheckServerVersion(isDesktop);
+
+  const showServerVersion = serverVersion && serverVersion !== CURRENT_VERSION;
</code_context>

<issue_to_address>
**suggestion:** Redundant server-version check between StoreInitialization and Version component.

This logic now calls `useCheckServerVersion` in both `StoreInitialization` and `Version` with the same key and `isDesktop` condition. Although SWR dedupes the network request, the extra hook adds unnecessary complexity and duplicates responsibility. It would be cleaner to keep `useCheckServerVersion` in a single place (e.g., initialization) and have `Version` consume `serverVersion` from the store instead of invoking the hook again.

```suggestion
const Version = memo<{ mobile?: boolean }>(({ mobile }) => {
  const hasNewVersion = useNewVersion();
  const [latestVersion, serverVersion] = useGlobalStore((s) => [
    s.latestVersion,
    s.serverVersion,
  ]);
  const { t } = useTranslation('common');

  const showServerVersion = serverVersion && serverVersion !== CURRENT_VERSION;
```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment on lines +86 to +89
const [dismissed, setDismissed] = useState(false);
const isServerVersionOutdated = useGlobalStore((s) => s.isServerVersionOutdated);

if (!isServerVersionOutdated || dismissed) return null;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: The dismissal state is not persisted, so the alert reappears on every reload.

Since dismissed is only local component state, the alert will reappear on every reload or new tab, even after “Continue Anyway” is selected. To avoid repeatedly interrupting users on long-lived outdated servers, consider persisting the dismissal (e.g., via localStorage or a global store flag keyed by version/session).

Suggested implementation:

const SERVER_VERSION_OUTDATED_DISMISSED_KEY = 'serverVersionOutdated.dismissed';

const ServerVersionOutdatedAlert = () => {
  const { styles } = useStyles();
  const { t } = useTranslation('common');
  const [dismissed, setDismissed] = useState(false);
  const isServerVersionOutdated = useGlobalStore((s) => s.isServerVersionOutdated);

  useEffect(() => {
    try {
      const stored = window.localStorage.getItem(SERVER_VERSION_OUTDATED_DISMISSED_KEY);
      if (stored === 'true') {
        setDismissed(true);
      }
    } catch {
      // Ignore storage errors and fall back to non-persistent behavior
    }
  }, []);

  const handleDismiss = () => {
    try {
      window.localStorage.setItem(SERVER_VERSION_OUTDATED_DISMISSED_KEY, 'true');
    } catch {
      // Ignore storage errors; dismissal will still apply for this session
    }
    setDismissed(true);
  };

  if (!isServerVersionOutdated || dismissed) return null;
        <div className={styles.closeButton} onClick={handleDismiss}>
  1. Ensure useEffect is imported from React at the top of this file, e.g. update the existing React import to: import React, { useEffect, useState } from 'react'; (or equivalent based on current import style).
  2. If the project prefers a version-aware dismissal (i.e. reset when server version changes), you can extend this by incorporating the server version into SERVER_VERSION_OUTDATED_DISMISSED_KEY (e.g., serverVersionOutdated.dismissed.${version}) once the version is available in this component.

Comment on lines 19 to +30
const Version = memo<{ mobile?: boolean }>(({ mobile }) => {
const hasNewVersion = useNewVersion();
const [latestVersion] = useGlobalStore((s) => [s.latestVersion]);
const [latestVersion, serverVersion, useCheckServerVersion] = useGlobalStore((s) => [
s.latestVersion,
s.serverVersion,
s.useCheckServerVersion,
]);
const { t } = useTranslation('common');

useCheckServerVersion(isDesktop);

const showServerVersion = serverVersion && serverVersion !== CURRENT_VERSION;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: Redundant server-version check between StoreInitialization and Version component.

This logic now calls useCheckServerVersion in both StoreInitialization and Version with the same key and isDesktop condition. Although SWR dedupes the network request, the extra hook adds unnecessary complexity and duplicates responsibility. It would be cleaner to keep useCheckServerVersion in a single place (e.g., initialization) and have Version consume serverVersion from the store instead of invoking the hook again.

Suggested change
const Version = memo<{ mobile?: boolean }>(({ mobile }) => {
const hasNewVersion = useNewVersion();
const [latestVersion] = useGlobalStore((s) => [s.latestVersion]);
const [latestVersion, serverVersion, useCheckServerVersion] = useGlobalStore((s) => [
s.latestVersion,
s.serverVersion,
s.useCheckServerVersion,
]);
const { t } = useTranslation('common');
useCheckServerVersion(isDesktop);
const showServerVersion = serverVersion && serverVersion !== CURRENT_VERSION;
const Version = memo<{ mobile?: boolean }>(({ mobile }) => {
const hasNewVersion = useNewVersion();
const [latestVersion, serverVersion] = useGlobalStore((s) => [
s.latestVersion,
s.serverVersion,
]);
const { t } = useTranslation('common');
const showServerVersion = serverVersion && serverVersion !== CURRENT_VERSION;

Check storageMode from electron store - only show alert when
using 'selfHost' mode, not 'cloud' mode.
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bc53bb460a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +29 to +33
const res = await fetch(SERVER_VERSION_URL);

if (!res.ok) {
return null;
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Treat only 404 as outdated server

The new check treats any non-OK response from /api/version as “server doesn’t support the API” by returning null, which then causes useCheckServerVersion to flag isServerVersionOutdated and show the blocking alert. This means transient failures (e.g., 500s, temporary auth/proxy errors, or brief network hiccups) will incorrectly warn that the server is too old even though it just failed to respond. Consider distinguishing a 404 (API truly missing) from other errors or surfacing a retry/error state so the outdated alert only appears when the endpoint is genuinely absent.

Useful? React with 👍 / 👎.

@Innei Innei force-pushed the feat/server-version-check branch from 6b50033 to 56c4d28 Compare January 22, 2026 13:22
Innei added 2 commits January 22, 2026 21:24
Previously any non-OK response was treated as "server doesn't support
the API", causing transient failures (500s, network issues) to
incorrectly show the outdated alert. Now only 404 returns null to
indicate a missing API, while other errors throw to allow SWR retry.
@codecov
Copy link
Copy Markdown

codecov bot commented Jan 22, 2026

Codecov Report

❌ Patch coverage is 23.91304% with 35 lines in your changes missing coverage. Please review.
✅ Project coverage is 74.31%. Comparing base (bf244f9) to head (ae40531).
⚠️ Report is 4 commits behind head on next.

Additional details and impacted files
@@            Coverage Diff             @@
##             next   #11710      +/-   ##
==========================================
- Coverage   74.33%   74.31%   -0.03%     
==========================================
  Files        1191     1191              
  Lines       94844    94890      +46     
  Branches    13002    13003       +1     
==========================================
+ Hits        70502    70516      +14     
- Misses      24252    24284      +32     
  Partials       90       90              
Flag Coverage Δ
app 67.26% <23.91%> (-0.03%) ⬇️
database 93.29% <ø> (ø)
packages/agent-runtime 90.20% <ø> (ø)
packages/context-engine 85.39% <ø> (ø)
packages/conversation-flow 92.28% <ø> (ø)
packages/file-loaders 88.66% <ø> (ø)
packages/memory-user-memory 69.68% <ø> (ø)
packages/model-bank 100.00% <ø> (ø)
packages/model-runtime 86.72% <ø> (ø)
packages/prompts 79.33% <ø> (ø)
packages/python-interpreter 92.90% <ø> (ø)
packages/ssrf-safe-fetch 0.00% <ø> (ø)
packages/utils 93.25% <ø> (ø)
packages/web-crawler 95.62% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
Store 68.06% <3.84%> (-0.08%) ⬇️
Services 50.62% <16.66%> (-0.11%) ⬇️
Server 67.81% <ø> (+0.01%) ⬆️
Libs 41.13% <ø> (ø)
Utils 93.82% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

- Implemented server version check functionality to notify users when their client version requires a newer server version.
- Added localized messages for server version outdated alerts in English and Chinese.
- Enhanced the global state management to track server version and its status.
- Updated UI components to display server version information and warnings appropriately.
- Introduced a new alert component to inform users about the need to upgrade their server for optimal performance.

Signed-off-by: Innei <tukon479@gmail.com>
@Innei Innei merged commit 0cf2723 into next Jan 22, 2026
32 of 36 checks passed
@Innei Innei deleted the feat/server-version-check branch January 22, 2026 15:20
@lobehubbot
Copy link
Copy Markdown
Member

❤️ Great PR @Innei ❤️

The growth of project is inseparable from user feedback and contribution, thanks for your contribution! If you are interesting with the lobehub developer community, please join our discord and then dm @arvinxx or @canisminor1990. They will invite you to our private developer channel. We are talking about the lobe-chat development or sharing ai newsletter around the world.

lobehubbot pushed a commit that referenced this pull request Jan 22, 2026
## [Version&nbsp;2.0.0-next.341](v2.0.0-next.340...v2.0.0-next.341)
<sup>Released on **2026-01-22**</sup>

#### ✨ Features

- **misc**: Add server version check for desktop app.

<br/>

<details>
<summary><kbd>Improvements and Fixes</kbd></summary>

#### What's improved

* **misc**: Add server version check for desktop app, closes [#11710](#11710) ([0cf2723](0cf2723))

</details>

<div align="right">

[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)

</div>
@lobehubbot
Copy link
Copy Markdown
Member

🎉 This PR is included in version 2.0.0-next.341 🎉

The release is available on:

Your semantic-release bot 📦🚀

JamieStivala pushed a commit to jaworldwideorg/OneJA-Bot that referenced this pull request Jan 23, 2026
## [Version&nbsp;1.153.0](v1.152.0...v1.153.0)
<sup>Released on **2026-01-23**</sup>

#### ♻ Code Refactoring

- **auth**: Remove NEXT_PUBLIC_AUTH_URL env variable.
- **model-select**: Migrate FunctionCallingModelSelect to LobeSelect.
- **ModelSwitchPanel**: Migrate from Popover to DropdownMenu with virtual scrolling.
- **userMemories**: Removed un-used code.
- **misc**: Improve memory data with experience and identity, move vercel-react-best-practices skills to .agents directory.

#### ✨ Features

- **database**: Added user memory activity.
- **desktop**: Add legacy local database detection and migration guidance.
- **misc**: Add platform-aware download client menu option, add server version check for desktop app, remove Clerk authentication code, skill setting page and skill store, support agent group unpublish agents, support client tasks mode, update the sandbox preinstall libs in sys role.

#### 🐛 Bug Fixes

- **copilot**: Pass correct scope when creating new session in PageEditor.
- **desktop**: Gracefully handle missing update manifest 404 errors.
- **model-runtime**: Filter unsupported image types (SVG) before sending to vision models.
- **pdf**: Upgrade pdfjs-dist and react-pdf to v5.x.
- **sidebar-drawer**: Fix drawer positioning and title style.
- **misc**: Fix group broadcast trigger tool use, fix local system tools, fix memory schema, fix multi agent tasks issue, fix multi tasks no summary issue, fix scope issue, fix tool argument scape and improve multi task run, fixed the sandbox tools call when error should use right callback, improve e2e server and complete i18n resources, slove the agent group editor not focus in editdata area, slove the agents header switch agents the lobeAI not show problem, sloved the old removeSessionTopics not work, TypewriterEffect not refreshing on language change, updata cron job ui & fixed commnuity pagenation goto error, update the agentbuilder tools not always use humanIntervention.

#### 💄 Styles

- **misc**: Improve auto scroll and group profile, update og, update share style.

<br/>

<details>
<summary><kbd>Improvements and Fixes</kbd></summary>

#### Code refactoring

* **auth**: Remove NEXT_PUBLIC_AUTH_URL env variable, closes [lobehub#11658](https://github.com/jaworldwideorg/OneJA-Bot/issues/11658) ([c0f9875](c0f9875))
* **model-select**: Migrate FunctionCallingModelSelect to LobeSelect, closes [lobehub#11664](https://github.com/jaworldwideorg/OneJA-Bot/issues/11664) ([ad51305](ad51305))
* **ModelSwitchPanel**: Migrate from Popover to DropdownMenu with virtual scrolling, closes [lobehub#11663](https://github.com/jaworldwideorg/OneJA-Bot/issues/11663) ([c9d9dff](c9d9dff))
* **userMemories**: Removed un-used code, closes [lobehub#11713](https://github.com/jaworldwideorg/OneJA-Bot/issues/11713) ([89750fc](89750fc))
* **misc**: Improve memory data with experience and identity, closes [lobehub#11717](https://github.com/jaworldwideorg/OneJA-Bot/issues/11717) ([bdb3eb4](bdb3eb4))
* **misc**: Move vercel-react-best-practices skills to .agents directory, closes [lobehub#11703](https://github.com/jaworldwideorg/OneJA-Bot/issues/11703) ([6df7731](6df7731))

#### What's improved

* **database**: Added user memory activity, closes [lobehub#11680](https://github.com/jaworldwideorg/OneJA-Bot/issues/11680) ([0160fbd](0160fbd))
* **desktop**: Add legacy local database detection and migration guidance, closes [lobehub#11682](https://github.com/jaworldwideorg/OneJA-Bot/issues/11682) ([5664b84](5664b84))
* **misc**: Add platform-aware download client menu option, closes [lobehub#11676](https://github.com/jaworldwideorg/OneJA-Bot/issues/11676) ([55abddc](55abddc))
* **misc**: Add server version check for desktop app, closes [lobehub#11710](https://github.com/jaworldwideorg/OneJA-Bot/issues/11710) ([0cf2723](0cf2723))
* **misc**: Remove Clerk authentication code, closes [lobehub#11711](https://github.com/jaworldwideorg/OneJA-Bot/issues/11711) ([395595a](395595a))
* **misc**: Skill setting page and skill store, closes [lobehub#11665](https://github.com/jaworldwideorg/OneJA-Bot/issues/11665) ([d8c0c26](d8c0c26))
* **misc**: Support agent group unpublish agents, closes [lobehub#11687](https://github.com/jaworldwideorg/OneJA-Bot/issues/11687) ([4e060be](4e060be))
* **misc**: Support client tasks mode, closes [lobehub#11666](https://github.com/jaworldwideorg/OneJA-Bot/issues/11666) ([98cf57b](98cf57b))
* **misc**: Update the sandbox preinstall libs in sys role, closes [lobehub#11688](https://github.com/jaworldwideorg/OneJA-Bot/issues/11688) ([404c577](404c577))

#### What's fixed

* **copilot**: Pass correct scope when creating new session in PageEditor, closes [lobehub#11714](https://github.com/jaworldwideorg/OneJA-Bot/issues/11714) ([0259270](0259270))
* **desktop**: Gracefully handle missing update manifest 404 errors, closes [lobehub#11625](https://github.com/jaworldwideorg/OneJA-Bot/issues/11625) ([13e95b9](13e95b9))
* **model-runtime**: Filter unsupported image types (SVG) before sending to vision models, closes [lobehub#11698](https://github.com/jaworldwideorg/OneJA-Bot/issues/11698) ([c0c99a7](c0c99a7))
* **pdf**: Upgrade pdfjs-dist and react-pdf to v5.x, closes [lobehub#11686](https://github.com/jaworldwideorg/OneJA-Bot/issues/11686) ([2b620df](2b620df))
* **sidebar-drawer**: Fix drawer positioning and title style, closes [lobehub#11655](https://github.com/jaworldwideorg/OneJA-Bot/issues/11655) ([cf5320e](cf5320e))
* **misc**: Fix group broadcast trigger tool use, closes [lobehub#11646](https://github.com/jaworldwideorg/OneJA-Bot/issues/11646) ([831a9b3](831a9b3))
* **misc**: Fix local system tools, closes [lobehub#11702](https://github.com/jaworldwideorg/OneJA-Bot/issues/11702) ([6548fc7](6548fc7))
* **misc**: Fix memory schema, closes [lobehub#11645](https://github.com/jaworldwideorg/OneJA-Bot/issues/11645) ([3baf780](3baf780))
* **misc**: Fix multi agent tasks issue, closes [lobehub#11672](https://github.com/jaworldwideorg/OneJA-Bot/issues/11672) ([9de773b](9de773b))
* **misc**: Fix multi tasks no summary issue, closes [lobehub#11685](https://github.com/jaworldwideorg/OneJA-Bot/issues/11685) ([26ce317](26ce317))
* **misc**: Fix scope issue, closes [lobehub#11719](https://github.com/jaworldwideorg/OneJA-Bot/issues/11719) ([17adde8](17adde8))
* **misc**: Fix tool argument scape and improve multi task run, closes [lobehub#11691](https://github.com/jaworldwideorg/OneJA-Bot/issues/11691) ([b13bb8a](b13bb8a))
* **misc**: Fixed the sandbox tools call when error should use right callback, closes [lobehub#11721](https://github.com/jaworldwideorg/OneJA-Bot/issues/11721) ([e8fce68](e8fce68))
* **misc**: Improve e2e server and complete i18n resources, closes [lobehub#11678](https://github.com/jaworldwideorg/OneJA-Bot/issues/11678) ([d450dd9](d450dd9))
* **misc**: Slove the agent group editor not focus in editdata area, closes [lobehub#11677](https://github.com/jaworldwideorg/OneJA-Bot/issues/11677) ([9ac84e6](9ac84e6))
* **misc**: Slove the agents header switch agents the lobeAI not show problem, closes [lobehub#11726](https://github.com/jaworldwideorg/OneJA-Bot/issues/11726) ([f45f508](f45f508))
* **misc**: Sloved the old removeSessionTopics not work, closes [lobehub#11671](https://github.com/jaworldwideorg/OneJA-Bot/issues/11671) ([06d41e5](06d41e5))
* **misc**: TypewriterEffect not refreshing on language change, closes [lobehub#11657](https://github.com/jaworldwideorg/OneJA-Bot/issues/11657) ([ba30f46](ba30f46))
* **misc**: Updata cron job ui & fixed commnuity pagenation goto error, closes [lobehub#11700](https://github.com/jaworldwideorg/OneJA-Bot/issues/11700) ([42ad2a0](42ad2a0))
* **misc**: Update the agentbuilder tools not always use humanIntervention, closes [lobehub#11696](https://github.com/jaworldwideorg/OneJA-Bot/issues/11696) ([0d3017b](0d3017b))

#### Styles

* **misc**: Improve auto scroll and group profile, closes [lobehub#11725](https://github.com/jaworldwideorg/OneJA-Bot/issues/11725) ([550acc2](550acc2))
* **misc**: Update og, closes [lobehub#11709](https://github.com/jaworldwideorg/OneJA-Bot/issues/11709) ([01cf4e4](01cf4e4))
* **misc**: Update share style, closes [lobehub#11716](https://github.com/jaworldwideorg/OneJA-Bot/issues/11716) ([3c70dfa](3c70dfa))

</details>

<div align="right">

[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)

</div>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

released on @next size:L This PR changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants