@mastra/memory 1.32.2-alpha.0 → 1.32.2-alpha.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/dist/docs/SKILL.md +1 -1
  2. package/dist/docs/assets/SOURCE_MAP.json +1 -1
  3. package/dist/docs/references/docs-evals-evals-with-memory.md +3 -1
  4. package/package.json +5 -5
package/dist/docs/SKILL.md CHANGED
@@ -3,7 +3,7 @@ name: mastra-memory
3
3
  description: Documentation for @mastra/memory. Use when working with @mastra/memory APIs, configuration, or implementation.
4
4
  metadata:
5
5
  package: "@mastra/memory"
6
- version: "1.32.2-alpha.0"
6
+ version: "1.32.2-alpha.1"
7
7
  ---
8
8
 
9
9
  ## When to use
package/dist/docs/assets/SOURCE_MAP.json CHANGED
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "1.32.2-alpha.0",
2
+ "version": "1.32.2-alpha.1",
3
3
  "package": "@mastra/memory",
4
4
  "exports": {},
5
5
  "modules": {
package/dist/docs/references/docs-evals-evals-with-memory.md CHANGED
@@ -90,7 +90,9 @@ const average = scores.reduce((a, b) => a + b, 0) / scores.length
90
90
 
91
91
  ## Dataset experiments with an inline task
92
92
 
93
- `dataset.startExperiment({ target: agent })` **doesn't** forward a `memory` option to the agent, only `requestContext`. To run a stored dataset against a memory-enabled agent, use an inline `task` function and stash `{ threadId, resourceId }` in each item's `metadata`. The scorer pipeline still runs as normal.
93
+ `dataset.startExperiment()` accepts `targetType` and `targetId` for a registered target, or an inline `task` function. For a registered memory-enabled agent, the runner creates a fresh thread per item by default. See [memory-enabled experiment targets](https://mastra.ai/docs/evals/experiments) for resource isolation and request context options.
94
+
95
+ To choose each item's thread explicitly through `agent.generate()`, use an inline `task` and store `{ threadId, resourceId }` in each item's `metadata`. The scorer pipeline still runs as normal.
94
96
 
95
97
  ```typescript
96
98
  import { randomUUID } from 'node:crypto'
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mastra/memory",
3
- "version": "1.32.2-alpha.0",
3
+ "version": "1.32.2-alpha.1",
4
4
  "description": "",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
@@ -52,7 +52,7 @@
52
52
  "probe-image-size": "^7.2.3",
53
53
  "xxhash-wasm": "^1.1.0",
54
54
  "zod": "^4.6.4",
55
- "@mastra/schema-compat": "1.3.11"
55
+ "@mastra/schema-compat": "1.3.12-alpha.0"
56
56
  },
57
57
  "devDependencies": {
58
58
  "@ai-sdk/openai": "^1.3.24",
@@ -70,11 +70,11 @@
70
70
  "typescript-eslint": "^8.57.0",
71
71
  "vitest": "4.1.11",
72
72
  "@internal/ai-sdk-v4": "0.0.84",
73
- "@internal/ai-v6": "0.0.84",
74
- "@internal/lint": "0.0.137",
75
73
  "@internal/ai-sdk-v5": "0.0.84",
74
+ "@internal/lint": "0.0.137",
76
75
  "@internal/types-builder": "0.0.112",
77
- "@mastra/core": "1.72.0-alpha.0"
76
+ "@internal/ai-v6": "0.0.84",
77
+ "@mastra/core": "1.72.0-alpha.1"
78
78
  },
79
79
  "peerDependencies": {
80
80
  "@mastra/core": ">=1.4.1-0 <2.0.0-0"