@mastra/upstash 1.0.1 → 1.0.2

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # @mastra/upstash
 
+## 1.0.2
+
+### Patch Changes
+
+- Add a clear runtime error when `queryVector` is omitted for vector stores that require a vector for queries. Previously, omitting `queryVector` would produce confusing SDK-level errors; now each store throws a structured `MastraError` with `ErrorCategory.USER` explaining that metadata-only queries are not supported by that backend. ([#13286](https://github.com/mastra-ai/mastra/pull/13286))
+
+- Updated dependencies [[`df170fd`](https://github.com/mastra-ai/mastra/commit/df170fd139b55f845bfd2de8488b16435bd3d0da), [`ae55343`](https://github.com/mastra-ai/mastra/commit/ae5534397fc006fd6eef3e4f80c235bcdc9289ef), [`c290cec`](https://github.com/mastra-ai/mastra/commit/c290cec5bf9107225de42942b56b487107aa9dce), [`f03e794`](https://github.com/mastra-ai/mastra/commit/f03e794630f812b56e95aad54f7b1993dc003add), [`aa4a5ae`](https://github.com/mastra-ai/mastra/commit/aa4a5aedb80d8d6837bab8cbb2e301215d1ba3e9), [`de3f584`](https://github.com/mastra-ai/mastra/commit/de3f58408752a8d80a295275c7f23fc306cf7f4f), [`d3fb010`](https://github.com/mastra-ai/mastra/commit/d3fb010c98f575f1c0614452667396e2653815f6), [`702ee1c`](https://github.com/mastra-ai/mastra/commit/702ee1c41be67cc532b4dbe89bcb62143508f6f0), [`f495051`](https://github.com/mastra-ai/mastra/commit/f495051eb6496a720f637fc85b6d69941c12554c), [`e622f1d`](https://github.com/mastra-ai/mastra/commit/e622f1d3ab346a8e6aca6d1fe2eac99bd961e50b), [`861f111`](https://github.com/mastra-ai/mastra/commit/861f11189211b20ddb70d8df81a6b901fc78d11e), [`00f43e8`](https://github.com/mastra-ai/mastra/commit/00f43e8e97a80c82b27d5bd30494f10a715a1df9), [`1b6f651`](https://github.com/mastra-ai/mastra/commit/1b6f65127d4a0d6c38d0a1055cb84527db529d6b), [`96a1702`](https://github.com/mastra-ai/mastra/commit/96a1702ce362c50dda20c8b4a228b4ad1a36a17a), [`cb9f921`](https://github.com/mastra-ai/mastra/commit/cb9f921320913975657abb1404855d8c510f7ac5), [`114e7c1`](https://github.com/mastra-ai/mastra/commit/114e7c146ac682925f0fb37376c1be70e5d6e6e5), [`1b6f651`](https://github.com/mastra-ai/mastra/commit/1b6f65127d4a0d6c38d0a1055cb84527db529d6b), [`72df4a8`](https://github.com/mastra-ai/mastra/commit/72df4a8f9bf1a20cfd3d9006a4fdb597ad56d10a)]:
+  - @mastra/core@1.8.0
+
+## 1.0.2-alpha.0
+
+### Patch Changes
+
+- Add a clear runtime error when `queryVector` is omitted for vector stores that require a vector for queries. Previously, omitting `queryVector` would produce confusing SDK-level errors; now each store throws a structured `MastraError` with `ErrorCategory.USER` explaining that metadata-only queries are not supported by that backend. ([#13286](https://github.com/mastra-ai/mastra/pull/13286))
+
+- Updated dependencies [[`df170fd`](https://github.com/mastra-ai/mastra/commit/df170fd139b55f845bfd2de8488b16435bd3d0da), [`ae55343`](https://github.com/mastra-ai/mastra/commit/ae5534397fc006fd6eef3e4f80c235bcdc9289ef), [`c290cec`](https://github.com/mastra-ai/mastra/commit/c290cec5bf9107225de42942b56b487107aa9dce), [`f03e794`](https://github.com/mastra-ai/mastra/commit/f03e794630f812b56e95aad54f7b1993dc003add), [`aa4a5ae`](https://github.com/mastra-ai/mastra/commit/aa4a5aedb80d8d6837bab8cbb2e301215d1ba3e9), [`de3f584`](https://github.com/mastra-ai/mastra/commit/de3f58408752a8d80a295275c7f23fc306cf7f4f), [`d3fb010`](https://github.com/mastra-ai/mastra/commit/d3fb010c98f575f1c0614452667396e2653815f6), [`702ee1c`](https://github.com/mastra-ai/mastra/commit/702ee1c41be67cc532b4dbe89bcb62143508f6f0), [`f495051`](https://github.com/mastra-ai/mastra/commit/f495051eb6496a720f637fc85b6d69941c12554c), [`e622f1d`](https://github.com/mastra-ai/mastra/commit/e622f1d3ab346a8e6aca6d1fe2eac99bd961e50b), [`861f111`](https://github.com/mastra-ai/mastra/commit/861f11189211b20ddb70d8df81a6b901fc78d11e), [`00f43e8`](https://github.com/mastra-ai/mastra/commit/00f43e8e97a80c82b27d5bd30494f10a715a1df9), [`1b6f651`](https://github.com/mastra-ai/mastra/commit/1b6f65127d4a0d6c38d0a1055cb84527db529d6b), [`96a1702`](https://github.com/mastra-ai/mastra/commit/96a1702ce362c50dda20c8b4a228b4ad1a36a17a), [`cb9f921`](https://github.com/mastra-ai/mastra/commit/cb9f921320913975657abb1404855d8c510f7ac5), [`114e7c1`](https://github.com/mastra-ai/mastra/commit/114e7c146ac682925f0fb37376c1be70e5d6e6e5), [`1b6f651`](https://github.com/mastra-ai/mastra/commit/1b6f65127d4a0d6c38d0a1055cb84527db529d6b), [`72df4a8`](https://github.com/mastra-ai/mastra/commit/72df4a8f9bf1a20cfd3d9006a4fdb597ad56d10a)]:
+  - @mastra/core@1.8.0-alpha.0
+
 ## 1.0.1
 
 ### Patch Changes

package/dist/docs/SKILL.md

@@ -3,7 +3,7 @@ name: mastra-upstash
 description: Documentation for @mastra/upstash. Use when working with @mastra/upstash APIs, configuration, or implementation.
 metadata:
   package: "@mastra/upstash"
-  version: "1.0.1"
+  version: "1.0.2"
 ---
 
 ## When to use

package/dist/docs/assets/SOURCE_MAP.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.1",
+  "version": "1.0.2",
   "package": "@mastra/upstash",
   "exports": {},
   "modules": {}

package/dist/docs/references/docs-memory-working-memory.md

@@ -18,15 +18,15 @@ Working memory can persist at two different scopes:
 Here's a minimal example of setting up an agent with working memory:
 
 ```typescript
-import { Agent } from "@mastra/core/agent";
-import { Memory } from "@mastra/memory";
+import { Agent } from '@mastra/core/agent'
+import { Memory } from '@mastra/memory'
 
 // Create agent with working memory enabled
 const agent = new Agent({
-  id: "personal-assistant",
-  name: "PersonalAssistant",
-  instructions: "You are a helpful personal assistant.",
-  model: "openai/gpt-5.1",
+  id: 'personal-assistant',
+  name: 'PersonalAssistant',
+  instructions: 'You are a helpful personal assistant.',
+  model: 'openai/gpt-5.1',
   memory: new Memory({
     options: {
       workingMemory: {
@@ -34,7 +34,7 @@ const agent = new Agent({
       },
     },
   }),
-});
+})
 ```
 
 ## How it Works
@@ -57,7 +57,7 @@ const memory = new Memory({
   options: {
     workingMemory: {
       enabled: true,
-      scope: "resource", // Memory persists across all user threads
+      scope: 'resource', // Memory persists across all user threads
       template: `# User Profile
 - **Name**:
 - **Location**:
@@ -67,7 +67,7 @@ const memory = new Memory({
 `,
     },
   },
-});
+})
 ```
 
 **Use cases:**
@@ -82,12 +82,12 @@ When using resource-scoped memory, make sure to pass the `resource` parameter in
 
 ```typescript
 // Resource-scoped memory requires resource
-const response = await agent.generate("Hello!", {
+const response = await agent.generate('Hello!', {
   memory: {
-    thread: "conversation-123",
-    resource: "user-alice-456", // Same user across different threads
+    thread: 'conversation-123',
+    resource: 'user-alice-456', // Same user across different threads
   },
-});
+})
 ```
 
 ### Thread-Scoped Memory
@@ -100,7 +100,7 @@ const memory = new Memory({
   options: {
     workingMemory: {
       enabled: true,
-      scope: "thread", // Memory is isolated per thread
+      scope: 'thread', // Memory is isolated per thread
       template: `# User Profile
 - **Name**:
 - **Interests**:
@@ -108,7 +108,7 @@ const memory = new Memory({
 `,
     },
   },
-});
+})
 ```
 
 **Use cases:**
@@ -165,7 +165,7 @@ const memory = new Memory({
 `,
     },
   },
-});
+})
 ```
 
 ## Designing Effective Templates
@@ -190,7 +190,7 @@ const basicMemory = new Memory({
       template: `User Facts:\n- Name:\n- Favorite Color:\n- Current Topic:`,
     },
   },
-});
+})
 ```
 
 You can also store the key facts in a short paragraph format if you prefer a more narrative style:
@@ -203,7 +203,7 @@ const paragraphMemory = new Memory({
       template: `Important Details:\n\nKeep a short paragraph capturing the user's important facts (name, main goal, current task).`,
     },
   },
-});
+})
 ```
 
 ## Structured Working Memory
@@ -215,8 +215,8 @@ Working memory can also be defined using a structured schema instead of a Markdo
 ### Example: Schema-Based Working Memory
 
 ```typescript
-import { z } from "zod";
-import { Memory } from "@mastra/memory";
+import { z } from 'zod'
+import { Memory } from '@mastra/memory'
 
 const userProfileSchema = z.object({
   name: z.string().optional(),
@@ -229,7 +229,7 @@ const userProfileSchema = z.object({
       deadlines: z.array(z.string()).optional(),
     })
     .optional(),
-});
+})
 
 const memory = new Memory({
   options: {
@@ -239,7 +239,7 @@ const memory = new Memory({
       // template: ... (do not set)
     },
   },
-});
+})
 ```
 
 When a schema is provided, the agent receives the working memory as a JSON object. For example:
@@ -314,9 +314,9 @@ When creating a thread, you can provide initial working memory through the metad
 ```typescript
 // Create a thread with initial working memory
 const thread = await memory.createThread({
-  threadId: "thread-123",
-  resourceId: "user-456",
-  title: "Medical Consultation",
+  threadId: 'thread-123',
+  resourceId: 'user-456',
+  title: 'Medical Consultation',
   metadata: {
     workingMemory: `# Patient Profile
 - Name: John Doe
@@ -326,15 +326,15 @@ const thread = await memory.createThread({
 - Medical History: Hypertension (controlled)
 `,
   },
-});
+})
 
 // The agent will now have access to this information in all messages
 await agent.generate("What's my blood type?", {
   memory: {
     thread: thread.id,
-    resource: "user-456",
+    resource: 'user-456',
   },
-});
+})
 // Response: "Your blood type is O+."
 ```
 
@@ -345,7 +345,7 @@ You can also update an existing thread's working memory:
 ```typescript
 // Update thread metadata to add/modify working memory
 await memory.updateThread({
-  id: "thread-123",
+  id: 'thread-123',
   title: thread.title,
   metadata: {
     ...thread.metadata,
@@ -357,7 +357,7 @@ await memory.updateThread({
 - Medical History: Hypertension (controlled)
 `,
   },
-});
+})
 ```
 
 ### Direct Memory Update
@@ -366,10 +366,10 @@ Alternatively, use the `updateWorkingMemory` method directly:
 
 ```typescript
 await memory.updateWorkingMemory({
-  threadId: "thread-123",
-  resourceId: "user-456", // Required for resource-scoped memory
-  workingMemory: "Updated memory content...",
-});
+  threadId: 'thread-123',
+  resourceId: 'user-456', // Required for resource-scoped memory
+  workingMemory: 'Updated memory content...',
+})
 ```
 
 ## Read-Only Working Memory
@@ -382,15 +382,15 @@ In some scenarios, you may want an agent to have access to working memory data w
 To enable read-only mode, set `readOnly: true` in the memory options:
 
 ```typescript
-const response = await agent.generate("What do you know about me?", {
+const response = await agent.generate('What do you know about me?', {
   memory: {
-    thread: "conversation-123",
-    resource: "user-alice-456",
+    thread: 'conversation-123',
+    resource: 'user-alice-456',
     options: {
       readOnly: true, // Working memory is provided but cannot be updated
     },
   },
-});
+})
 ```
 
 ## Examples