Environment

• Client Type: Desktop App (Electron)
• Desktop Version: v2.0.0-next.183 (auto-updated Dec 31, 2025)
• Server: Self-hosted lobehub/lobe-chat-database:1.143.2 (latest Docker Hub image)
• Auth: OIDC configured and working
• OS: macOS

Bug Description

After the Desktop app auto-updated to v2.0.0-next.183, the UI fails to render properly when connected to a self-hosted v1.143.2 server. OIDC login completes successfully, but post-login the UI components don't load due to apparent API/configuration changes between v1 and v2.

Root Cause

The v2 Desktop client expects v2 server API responses, but self-hosted users running the latest published Docker image (v1.143.2) have servers returning v1 data structures.

The Problem

1. No v2.0.0-next Docker images are published - Docker Hub only has v1.x tags
2. Desktop app auto-updated to v2 without warning or compatibility check
3. Self-hosted v1.x users have no path forward - cannot upgrade server (no images), cannot downgrade Desktop (no old versions available)

Expected Behavior

Either:

1. Desktop app should be backward-compatible with v1.x servers, OR
2. v2.0.0-next Docker images should be published so self-hosted users can upgrade, OR
3. Old Desktop versions should be available for download to maintain v1.x compatibility

Related Issues

• next.183版本的Lobehub desktop强制要求OIDC验证 #11082 - Forced OIDC requirement (different issue - this is post-login)
• v2.0.0-next. 183 刚刚点击更新到新版本，结果就没法使用了。需要强制登陆？ #11083 - Duplicate of next.183版本的Lobehub desktop强制要求OIDC验证 #11082

Additional Context

This breaks the self-hosted experience entirely. Users cannot use the Desktop app until either:

• They build a custom Docker image from the v2.0.0-next.183 Git tag
• Official v2 Docker images are published