@lobehub/lobehub 2.0.0-next.260 → 2.0.0-next.261

package/CHANGELOG.md

@@ -2,6 +2,31 @@
 
 # Changelog
 
+## [Version 2.0.0-next.261](https://github.com/lobehub/lobe-chat/compare/v2.0.0-next.260...v2.0.0-next.261)
+
+<sup>Released on **2026-01-10**</sup>
+
+#### ✨ Features
+
+- **userMemories**: Support to use customized Qstash client with extra header for workflows.
+
+<br/>
+
+<details>
+<summary><kbd>Improvements and Fixes</kbd></summary>
+
+#### What's improved
+
+- **userMemories**: Support to use customized Qstash client with extra header for workflows, closes [#11378](https://github.com/lobehub/lobe-chat/issues/11378) ([3417af4](https://github.com/lobehub/lobe-chat/commit/3417af4))
+
+</details>
+
+<div align="right">
+
+[![](https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square)](#readme-top)
+
+</div>
+
 ## [Version 2.0.0-next.260](https://github.com/lobehub/lobe-chat/compare/v2.0.0-next.259...v2.0.0-next.260)
 
 <sup>Released on **2026-01-10**</sup>

package/changelog/v1.json

@@ -1,4 +1,9 @@
 [
+  {
+    "children": {},
+    "date": "2026-01-10",
+    "version": "2.0.0-next.261"
+  },
   {
     "children": {},
     "date": "2026-01-10",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lobehub/lobehub",
-  "version": "2.0.0-next.260",
+  "version": "2.0.0-next.261",
   "description": "LobeHub - an open-source,comprehensive AI Agent framework that supports speech synthesis, multimodal, and extensible Function Call plugin system. Supports one-click free deployment of your private ChatGPT/LLM web application.",
   "keywords": [
     "framework",

package/src/app/(backend)/api/workflows/memory-user-memory/pipelines/chat-topic/process-topics/route.ts

@@ -12,6 +12,10 @@ import {
   type MemoryExtractionPayloadInput,
   normalizeMemoryExtractionPayload,
 } from '@/server/services/memory/userMemory/extract';
+import { Client } from '@upstash/qstash'
+import { parseMemoryExtractionConfig } from '@/server/globalConfig/parseMemoryExtractionConfig';
+
+const { upstashWorkflowExtraHeaders } = parseMemoryExtractionConfig();
 
 const CEP_LAYERS: LayersEnum[] = [LayersEnum.Context, LayersEnum.Experience, LayersEnum.Preference];
 const IDENTITY_LAYERS: LayersEnum[] = [LayersEnum.Identity];
@@ -136,5 +140,17 @@ export const { POST } = serve<MemoryExtractionPayloadInput>((context) =>
         span.end();
       }
     },
-  ),
-);
+  ), {
+    // NOTICE(@nekomeowww): Here as scenarios like Vercel Deployment Protection,
+    // intermediate context.run(...) won't offer customizable headers like context.trigger(...) / client.trigger(...)
+    // for passing additional headers, we have to provide a custom QStash client with the required headers here.
+    //
+    // Refer to the doc for more details:
+    // https://upstash.com/docs/workflow/troubleshooting/vercel#step-2-pass-header-when-triggering
+    qstashClient: new Client({
+      headers: {
+        ...upstashWorkflowExtraHeaders,
+      },
+      token: process.env.QSTASH_TOKEN!
+    })
+});

package/src/app/(backend)/api/workflows/memory-user-memory/pipelines/chat-topic/process-user-topics/route.ts

@@ -10,13 +10,14 @@ import {
 import { forEachBatchSequential } from '@/server/services/memory/userMemory/topicBatching';
 import { MemorySourceType } from '@lobechat/types';
 import { parseMemoryExtractionConfig } from '@/server/globalConfig/parseMemoryExtractionConfig';
+import { Client } from '@upstash/qstash'
 
 const TOPIC_PAGE_SIZE = 50;
 const TOPIC_BATCH_SIZE = 4;
 
-export const { POST } = serve<MemoryExtractionPayloadInput>(async (context) => {
-  const { upstashWorkflowExtraHeaders } = parseMemoryExtractionConfig();
+const { upstashWorkflowExtraHeaders } = parseMemoryExtractionConfig();
 
+export const { POST } = serve<MemoryExtractionPayloadInput>(async (context) => {
   const params = normalizeMemoryExtractionPayload(context.requestPayload || {});
   if (!params.userIds.length) {
     return { message: 'No user ids provided for topic processing.' };
@@ -125,4 +126,17 @@ export const { POST } = serve<MemoryExtractionPayloadInput>(async (context) => {
   }
 
   return { processedUsers: params.userIds.length };
+}, {
+  // NOTICE(@nekomeowww): Here as scenarios like Vercel Deployment Protection,
+  // intermediate context.run(...) won't offer customizable headers like context.trigger(...) / client.trigger(...)
+  // for passing additional headers, we have to provide a custom QStash client with the required headers here.
+  //
+  // Refer to the doc for more details:
+  // https://upstash.com/docs/workflow/troubleshooting/vercel#step-2-pass-header-when-triggering
+  qstashClient: new Client({
+    headers: {
+      ...upstashWorkflowExtraHeaders,
+    },
+    token: process.env.QSTASH_TOKEN!
+  })
 });

package/src/app/(backend)/api/workflows/memory-user-memory/pipelines/chat-topic/process-users/route.ts

@@ -1,5 +1,6 @@
 import { serve } from '@upstash/workflow/nextjs';
 import { chunk } from 'es-toolkit/compat';
+import { Client } from '@upstash/qstash'
 
 import {
   MemoryExtractionExecutor,
@@ -13,9 +14,9 @@ import { parseMemoryExtractionConfig } from '@/server/globalConfig/parseMemoryEx
 const USER_PAGE_SIZE = 50;
 const USER_BATCH_SIZE = 10;
 
-export const { POST } = serve<MemoryExtractionPayloadInput>(async (context) => {
-  const { upstashWorkflowExtraHeaders } = parseMemoryExtractionConfig();
+const { upstashWorkflowExtraHeaders } = parseMemoryExtractionConfig();
 
+export const { POST } = serve<MemoryExtractionPayloadInput>(async (context) => {
   const params = normalizeMemoryExtractionPayload(context.requestPayload || {});
   if (params.sources.length === 0) {
     return { message: 'No sources provided, skip memory extraction.' };
@@ -73,4 +74,17 @@ export const { POST } = serve<MemoryExtractionPayloadInput>(async (context) => {
     nextCursor: cursor ? cursor.id : null,
     processedUsers: ids.length,
   };
+}, {
+  // NOTICE(@nekomeowww): Here as scenarios like Vercel Deployment Protection,
+  // intermediate context.run(...) won't offer customizable headers like context.trigger(...) / client.trigger(...)
+  // for passing additional headers, we have to provide a custom QStash client with the required headers here.
+  //
+  // Refer to the doc for more details:
+  // https://upstash.com/docs/workflow/troubleshooting/vercel#step-2-pass-header-when-triggering
+  qstashClient: new Client({
+    headers: {
+      ...upstashWorkflowExtraHeaders,
+    },
+    token: process.env.QSTASH_TOKEN!
+  })
 });