@mastra/mongodb 1.25.0-alpha.0 → 1.25.0

package/dist/docs/SKILL.md

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

package/dist/docs/assets/SOURCE_MAP.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.25.0-alpha.0",
+  "version": "1.25.0",
   "package": "@mastra/mongodb",
   "exports": {},
   "modules": {}

package/dist/docs/references/docs-memory-semantic-recall.md

@@ -435,6 +435,8 @@ When using PostgreSQL as your vector store, you can optimize semantic recall per
 
 PostgreSQL supports both IVFFlat and HNSW indexes. By default, Mastra creates an IVFFlat index, but HNSW indexes typically provide better performance, especially with OpenAI embeddings which use inner product distance.
 
+Semantic recall always filters by thread or resource. PgVector uses the vector index for these searches only with HNSW on pgvector 0.8.0 or newer. With IVFFlat, each search compares the query against every message in the thread or resource.
+
 ```typescript
 import { Memory } from '@mastra/memory'
 import { PostgresStore, PgVector } from '@mastra/pg'

package/dist/docs/references/reference-rag-retrieval.md

@@ -251,7 +251,11 @@ const results = await pgVector.query({
 })
 ```
 
-Postgres vector indexes (HNSW and IVFFlat) can't restrict that search to rows matching a condition. When a filter is present, pgVector instead compares the query vector against every matching row and returns the closest `topK`. Results are exact, but the work grows with the number of rows the filter matches. Indexing the metadata column speeds up row retrieval. The distance comparisons still happen per row.
+With an HNSW index on pgvector 0.8.0 or newer, PostgreSQL searches the index and skips rows that don't match the filter. When the index search can't fill `topK`, pgVector reruns the query as an exact search.
+
+With IVFFlat, or HNSW on older pgvector versions, pgVector compares the query vector against every matching row. Results are exact, but the work grows with the number of matching rows.
+
+Indexing the metadata fields you filter on speeds up both cases and gives PostgreSQL the row counts it needs to choose between them.
 
 ### Vector Query Tool
 

package/dist/index.cjs

@@ -10,7 +10,7 @@ let _mastra_core_agent = require("@mastra/core/agent");
 let _mastra_core_evals = require("@mastra/core/evals");
 let _mastra_core_storage_domains_skills = require("@mastra/core/storage/domains/skills");
 // package.json
-var version = "1.25.0-alpha.0";
+var version = "1.25.0";
 // src/vector/filter.ts
 /**
 * Translator for MongoDB filter queries.

package/dist/index.js

@@ -9,7 +9,7 @@ import { MessageList } from "@mastra/core/agent";
 import { saveScorePayloadSchema } from "@mastra/core/evals";
 import { skillSnapshotFieldValuesEqual } from "@mastra/core/storage/domains/skills";
 // package.json
-var version = "1.25.0-alpha.0";
+var version = "1.25.0";
 // src/vector/filter.ts
 /**
 * Translator for MongoDB filter queries.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/mongodb",
-  "version": "1.25.0-alpha.0",
+  "version": "1.25.0",
   "description": "MongoDB provider for Mastra - includes vector store capabilities",
   "license": "Apache-2.0",
   "type": "module",
@@ -32,12 +32,12 @@
     "tsx": "^4.23.15",
     "typescript": "^7.0.2",
     "vitest": "4.1.12",
-    "@internal/lint": "0.0.146",
-    "@internal/storage-test-utils": "0.0.142",
-    "@internal/types-builder": "0.0.121",
-    "@mastra/core": "1.81.0-alpha.2",
-    "@internal/core": "0.1.4-alpha.0",
-    "@mastra/memory": "1.40.0-alpha.1"
+    "@internal/core": "0.1.4",
+    "@internal/lint": "0.0.147",
+    "@internal/storage-test-utils": "0.0.143",
+    "@internal/types-builder": "0.0.122",
+    "@mastra/core": "1.81.0",
+    "@mastra/memory": "1.40.0"
   },
   "peerDependencies": {
     "@mastra/core": ">=1.76.0-0 <2.0.0-0"