@lobehub/lobehub 2.0.0-next.233 → 2.0.0-next.234

package/.github/workflows/e2e.yml

@@ -80,18 +80,12 @@ jobs:
       - name: Run E2E tests
         run: bun run e2e
 
-      - name: Upload Cucumber HTML report (on failure)
+      - name: Upload E2E test artifacts (on failure)
         if: failure()
         uses: actions/upload-artifact@v6
         with:
-          name: cucumber-report
-          path: e2e/reports
-          if-no-files-found: ignore
-
-      - name: Upload screenshots (on failure)
-        if: failure()
-        uses: actions/upload-artifact@v6
-        with:
-          name: test-screenshots
-          path: e2e/screenshots
-          if-no-files-found: ignore
+            name: e2e-artifacts
+            path: |
+              e2e/reports
+              e2e/screenshots
+            if-no-files-found: ignore

package/.github/workflows/test.yml

@@ -102,8 +102,8 @@ jobs:
       - name: Install deps
         run: bun i
 
-      - name: Run tests with blob reporter
-        run: bunx vitest --coverage --reporter=blob --silent='passed-only' --shard=${{ matrix.shard }}/2
+      - name: Run tests
+        run: bunx vitest --coverage --silent='passed-only' --shard=${{ matrix.shard }}/2
 
       - name: Upload blob report
         if: ${{ !cancelled() }}
@@ -139,7 +139,7 @@ jobs:
           merge-multiple: true
 
       - name: Merge reports
-        run: bunx vitest --merge-reports --coverage
+        run: bunx vitest --merge-reports --reporter=default --coverage
 
       - name: Upload App Coverage to Codecov
         uses: codecov/codecov-action@v5

package/CHANGELOG.md

@@ -2,6 +2,40 @@
 
 # Changelog
 
+## [Version 2.0.0-next.234](https://github.com/lobehub/lobe-chat/compare/v2.0.0-next.233...v2.0.0-next.234)
+
+<sup>Released on **2026-01-07**</sup>
+
+#### ✨ Features
+
+- **misc**: Add browser compatibility detection and fallback page, add the lobehub market tools servers.
+
+#### 🐛 Bug Fixes
+
+- **editor**: Fix slash command codeblock not working.
+
+<br/>
+
+<details>
+<summary><kbd>Improvements and Fixes</kbd></summary>
+
+#### What's improved
+
+- **misc**: Add browser compatibility detection and fallback page, closes [#11309](https://github.com/lobehub/lobe-chat/issues/11309) ([8be32c2](https://github.com/lobehub/lobe-chat/commit/8be32c2))
+- **misc**: Add the lobehub market tools servers, closes [#11315](https://github.com/lobehub/lobe-chat/issues/11315) ([a4003a3](https://github.com/lobehub/lobe-chat/commit/a4003a3))
+
+#### What's fixed
+
+- **editor**: Fix slash command codeblock not working, closes [#11321](https://github.com/lobehub/lobe-chat/issues/11321) ([f9a35eb](https://github.com/lobehub/lobe-chat/commit/f9a35eb))
+
+</details>
+
+<div align="right">
+
+[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
+
+</div>
+
 ## [Version 2.0.0-next.233](https://github.com/lobehub/lobe-chat/compare/v2.0.0-next.232...v2.0.0-next.233)
 
 <sup>Released on **2026-01-07**</sup>

package/CLAUDE.md

@@ -80,7 +80,7 @@ When creating new Linear issues using `mcp__linear-server__create_issue`, **MUST
 
 ### PR Linear Issue Association (REQUIRED)
 
-**When creating PRs for Linear issues, MUST include magic keywords in PR body:** `Fixes LOBE-123`, `Closes LOBE-123`, or `Resolves LOBE-123`
+**When creating PRs for Linear issues, MUST include magic keywords in PR body:** `Fixes LOBE-123`, `Closes LOBE-123`, or `Resolves LOBE-123`, and summarize the work done in the linear issue comment and update the issue status to "In Review".
 
 ### IMPORTANT: Per-Issue Completion Rule
 

package/changelog/v1.json

@@ -1,4 +1,13 @@
 [
+  {
+    "children": {
+      "features": [
+        "Add browser compatibility detection and fallback page, add the lobehub market tools servers."
+      ]
+    },
+    "date": "2026-01-07",
+    "version": "2.0.0-next.234"
+  },
   {
     "children": {},
     "date": "2026-01-07",

package/docs/development/basic/feature-development.mdx

@@ -254,14 +254,14 @@ Let's take the subcomponent `OpeningQuestion.tsx` as an example. Component imple
 import { DeleteOutlined, PlusOutlined } from '@ant-design/icons';
 import { Flexbox, SortableList } from '@lobehub/ui';
 import { Button, Empty, Input } from 'antd';
-import { createStyles } from 'antd-style';
+import { createStaticStyles } from 'antd-style';
 import { memo, useCallback, useMemo, useState } from 'react';
 import { useTranslation } from 'react-i18next';
 
 import { useStore } from '../store';
 import { selectors } from '../store/selectors';
 
-const useStyles = createStyles(({ css, token }) => ({
+const styles = createStaticStyles(({ css, cssVar }) => ({
   empty: css`
     margin-block: 24px;
     margin-inline: 0;
@@ -270,7 +270,7 @@ const useStyles = createStyles(({ css, token }) => ({
     margin-block-end: 8px;
     padding-block: 2px;
     padding-inline: 10px 0;
-    background: ${token.colorBgContainer};
+    background: ${cssVar.colorBgContainer};
   `,
   questionItemContent: css`
     flex: 1;
@@ -281,7 +281,7 @@ const useStyles = createStyles(({ css, token }) => ({
   `,
   repeatError: css`
     margin: 0;
-    color: ${token.colorErrorText};
+    color: ${cssVar.colorErrorText};
   `,
 }));
 
@@ -292,7 +292,6 @@ interface QuestionItem {
 
 const OpeningQuestions = memo(() => {
   const { t } = useTranslation('setting');
-  const { styles } = useStyles();
   const [questionInput, setQuestionInput] = useState('');
 
   // Use selector to access corresponding configuration

package/docs/development/basic/feature-development.zh-CN.mdx

@@ -254,14 +254,14 @@ lobe-chat 是个国际化项目，新加的文案需要更新默认的 `locale`
 import { DeleteOutlined, PlusOutlined } from '@ant-design/icons';
 import { Flexbox, SortableList } from '@lobehub/ui';
 import { Button, Empty, Input } from 'antd';
-import { createStyles } from 'antd-style';
+import { createStaticStyles } from 'antd-style';
 import { memo, useCallback, useMemo, useState } from 'react';
 import { useTranslation } from 'react-i18next';
 
 import { useStore } from '../store';
 import { selectors } from '../store/selectors';
 
-const useStyles = createStyles(({ css, token }) => ({
+const styles = createStaticStyles(({ css, cssVar }) => ({
   empty: css`
     margin-block: 24px;
     margin-inline: 0;
@@ -270,7 +270,7 @@ const useStyles = createStyles(({ css, token }) => ({
     margin-block-end: 8px;
     padding-block: 2px;
     padding-inline: 10px 0;
-    background: ${token.colorBgContainer};
+    background: ${cssVar.colorBgContainer};
   `,
   questionItemContent: css`
     flex: 1;
@@ -281,7 +281,7 @@ const useStyles = createStyles(({ css, token }) => ({
   `,
   repeatError: css`
     margin: 0;
-    color: ${token.colorErrorText};
+    color: ${cssVar.colorErrorText};
   `,
 }));
 
@@ -292,7 +292,6 @@ interface QuestionItem {
 
 const OpeningQuestions = memo(() => {
   const { t } = useTranslation('setting');
-  const { styles } = useStyles();
   const [questionInput, setQuestionInput] = useState('');
 
   // 使用 selector 访问对应配置

package/e2e/README.md

@@ -84,13 +84,13 @@ HEADLESS=false BASE_URL=http://localhost:3000 npm run test:smoke
 Feature files are written in Gherkin syntax and placed in the `src/features/` directory:
 
 ```gherkin
-@discover @smoke
-Feature: Discover Smoke Tests
-  Critical path tests to ensure the discover module is functional
+@community @smoke
+Feature: Community Smoke Tests
+  Critical path tests to ensure the community module is functional
 
-  @DISCOVER-SMOKE-001 @P0
-  Scenario: Load discover assistant list page
-    Given I navigate to "/discover/assistant"
+  @COMMUNITY-SMOKE-001 @P0
+  Scenario: Load community assistant list page
+    Given I navigate to "/community/assistant"
     Then the page should load without errors
     And I should see the page body
     And I should see the search bar

package/e2e/src/features/community/detail-pages.feature

@@ -1,4 +1,4 @@
-@discover @detail
+@community @detail
 Feature: Discover Detail Pages
   Tests for detail pages in the discover module
 
@@ -9,7 +9,7 @@ Feature: Discover Detail Pages
   # Assistant Detail Page
   # ============================================
 
-  @DISCOVER-DETAIL-001 @P1
+  @COMMUNITY-DETAIL-001 @P1
   Scenario: Load assistant detail page and verify content
     Given I navigate to "/community/assistant"
     And I wait for the page to fully load
@@ -20,7 +20,7 @@ Feature: Discover Detail Pages
     And I should see the assistant author information
     And I should see the add to workspace button
 
-  @DISCOVER-DETAIL-002 @P1
+  @COMMUNITY-DETAIL-002 @P1
   Scenario: Navigate back from assistant detail page
     Given I navigate to "/community/assistant"
     And I wait for the page to fully load
@@ -32,7 +32,7 @@ Feature: Discover Detail Pages
   # Model Detail Page
   # ============================================
 
-  @DISCOVER-DETAIL-003 @P1
+  @COMMUNITY-DETAIL-003 @P1
   Scenario: Load model detail page and verify content
     Given I navigate to "/community/model"
     And I wait for the page to fully load
@@ -42,7 +42,7 @@ Feature: Discover Detail Pages
     And I should see the model description
     And I should see the model parameters information
 
-  @DISCOVER-DETAIL-004 @P1
+  @COMMUNITY-DETAIL-004 @P1
   Scenario: Navigate back from model detail page
     Given I navigate to "/community/model"
     And I wait for the page to fully load
@@ -54,7 +54,7 @@ Feature: Discover Detail Pages
   # Provider Detail Page
   # ============================================
 
-  @DISCOVER-DETAIL-005 @P1
+  @COMMUNITY-DETAIL-005 @P1
   Scenario: Load provider detail page and verify content
     Given I navigate to "/community/provider"
     And I wait for the page to fully load
@@ -64,7 +64,7 @@ Feature: Discover Detail Pages
     And I should see the provider description
     And I should see the provider website link
 
-  @DISCOVER-DETAIL-006 @P1
+  @COMMUNITY-DETAIL-006 @P1
   Scenario: Navigate back from provider detail page
     Given I navigate to "/community/provider"
     And I wait for the page to fully load
@@ -76,7 +76,7 @@ Feature: Discover Detail Pages
   # MCP Detail Page
   # ============================================
 
-  @DISCOVER-DETAIL-007 @P1
+  @COMMUNITY-DETAIL-007 @P1
   Scenario: Load MCP detail page and verify content
     Given I navigate to "/community/mcp"
     And I wait for the page to fully load
@@ -86,7 +86,7 @@ Feature: Discover Detail Pages
     And I should see the MCP description
     And I should see the install button
 
-  @DISCOVER-DETAIL-008 @P1
+  @COMMUNITY-DETAIL-008 @P1
   Scenario: Navigate back from MCP detail page
     Given I navigate to "/community/mcp"
     And I wait for the page to fully load

package/e2e/src/features/community/interactions.feature

@@ -1,4 +1,4 @@
-@discover @interactions
+@community @interactions
 Feature: Discover Interactions
   Tests for user interactions within the discover module
 
@@ -9,14 +9,14 @@ Feature: Discover Interactions
   # Assistant Page Interactions
   # ============================================
 
-  @DISCOVER-INTERACT-001 @P1
+  @COMMUNITY-INTERACT-001 @P1
   Scenario: Search for assistants
     Given I navigate to "/community/assistant"
     When I type "developer" in the search bar
     And I wait for the search results to load
     Then I should see filtered assistant cards
 
-  @DISCOVER-INTERACT-002 @P1
+  @COMMUNITY-INTERACT-002 @P1
   Scenario: Filter assistants by category
     Given I navigate to "/community/assistant"
     When I click on a category in the category menu
@@ -24,7 +24,7 @@ Feature: Discover Interactions
     Then I should see assistant cards filtered by the selected category
     And the URL should contain the category parameter
 
-  @DISCOVER-INTERACT-003 @P1
+  @COMMUNITY-INTERACT-003 @P1
   Scenario: Navigate to next page of assistants
     Given I navigate to "/community/assistant"
     When I click the next page button
@@ -32,7 +32,7 @@ Feature: Discover Interactions
     Then I should see different assistant cards
     And the URL should contain the page parameter
 
-  @DISCOVER-INTERACT-004 @P1
+  @COMMUNITY-INTERACT-004 @P1
   Scenario: Navigate to assistant detail page
     Given I navigate to "/community/assistant"
     When I click on the first assistant card
@@ -43,7 +43,7 @@ Feature: Discover Interactions
   # Model Page Interactions
   # ============================================
 
-  @DISCOVER-INTERACT-005 @P1
+  @COMMUNITY-INTERACT-005 @P1
   Scenario: Sort models
     Given I navigate to "/community/model"
     When I click on the sort dropdown
@@ -51,7 +51,7 @@ Feature: Discover Interactions
     And I wait for the sorted results to load
     Then I should see model cards in the sorted order
 
-  @DISCOVER-INTERACT-006 @P1
+  @COMMUNITY-INTERACT-006 @P1
   Scenario: Navigate to model detail page
     Given I navigate to "/community/model"
     When I click on the first model card
@@ -62,7 +62,7 @@ Feature: Discover Interactions
   # Provider Page Interactions
   # ============================================
 
-  @DISCOVER-INTERACT-007 @P1
+  @COMMUNITY-INTERACT-007 @P1
   Scenario: Navigate to provider detail page
     Given I navigate to "/community/provider"
     When I click on the first provider card
@@ -73,14 +73,14 @@ Feature: Discover Interactions
   # MCP Page Interactions
   # ============================================
 
-  @DISCOVER-INTERACT-008 @P1
+  @COMMUNITY-INTERACT-008 @P1
   Scenario: Filter MCP tools by category
     Given I navigate to "/community/mcp"
     When I click on a category in the category filter
     And I wait for the filtered results to load
     Then I should see MCP cards filtered by the selected category
 
-  @DISCOVER-INTERACT-009 @P1
+  @COMMUNITY-INTERACT-009 @P1
   Scenario: Navigate to MCP detail page
     Given I navigate to "/community/mcp"
     When I click on the first MCP card
@@ -91,21 +91,21 @@ Feature: Discover Interactions
   # Home Page Interactions
   # ============================================
 
-  @DISCOVER-INTERACT-010 @P1
+  @COMMUNITY-INTERACT-010 @P1
   Scenario: Navigate from home to assistant list
     Given I navigate to "/community"
     When I click on the "more" link in the featured assistants section
     Then I should be navigated to "/community/assistant"
     And I should see the page body
 
-  @DISCOVER-INTERACT-011 @P1
+  @COMMUNITY-INTERACT-011 @P1
   Scenario: Navigate from home to MCP list
     Given I navigate to "/community"
     When I click on the "more" link in the featured MCP tools section
     Then I should be navigated to "/community/mcp"
     And I should see the page body
 
-  @DISCOVER-INTERACT-012 @P1
+  @COMMUNITY-INTERACT-012 @P1
   Scenario: Click featured assistant from home
     Given I navigate to "/community"
     When I click on the first featured assistant card

package/e2e/src/features/community/smoke.feature

@@ -1,8 +1,8 @@
-@discover @smoke
+@community @smoke
 Feature: Community Smoke Tests
   Critical path tests to ensure the community/discover module is functional
 
-  @DISCOVER-SMOKE-001 @P0
+  @COMMUNITY-SMOKE-001 @P0
   Scenario: Load Community Home Page
     Given I navigate to "/community"
     Then the page should load without errors
@@ -10,7 +10,7 @@ Feature: Community Smoke Tests
     And I should see the featured assistants section
     And I should see the featured MCP tools section
 
-  @DISCOVER-SMOKE-002 @P0
+  @COMMUNITY-SMOKE-002 @P0
   Scenario: Load Assistant List Page
     Given I navigate to "/community/assistant"
     Then the page should load without errors
@@ -20,7 +20,7 @@ Feature: Community Smoke Tests
     And I should see assistant cards
     And I should see pagination controls
 
-  @DISCOVER-SMOKE-003 @P0
+  @COMMUNITY-SMOKE-003 @P0
   Scenario: Load Model List Page
     Given I navigate to "/community/model"
     Then the page should load without errors
@@ -28,14 +28,14 @@ Feature: Community Smoke Tests
     And I should see model cards
     And I should see the sort dropdown
 
-  @DISCOVER-SMOKE-004 @P0
+  @COMMUNITY-SMOKE-004 @P0
   Scenario: Load Provider List Page
     Given I navigate to "/community/provider"
     Then the page should load without errors
     And I should see the page body
     And I should see provider cards
 
-  @DISCOVER-SMOKE-005 @P0
+  @COMMUNITY-SMOKE-005 @P0
   Scenario: Load MCP List Page
     Given I navigate to "/community/mcp"
     Then the page should load without errors