@mastra/chroma 1.0.1 → 1.0.2-alpha.0

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # @mastra/chroma
 
+## 1.0.2-alpha.0
+
+### Patch Changes
+
+- Security remediation for the 2026-06-17 "easy-day-js" supply-chain incident. Patch bump to publish clean versions and move the `latest` dist-tag forward, superseding the compromised versions that declared the malicious `easy-day-js` dependency. ([#18056](https://github.com/mastra-ai/mastra/pull/18056))
+
+- Updated dependencies [[`77a2351`](https://github.com/mastra-ai/mastra/commit/77a2351ee79296e360bce822cb3391f7cfd6489d)]:
+  - @mastra/core@1.43.1-alpha.0
+
 ## 1.0.1
 
 ### Patch Changes

package/LICENSE.md

@@ -1,3 +1,18 @@
+Portions of this software are licensed as follows:
+
+- All content that resides under any directory named "ee/" within this
+  repository, including but not limited to:
+  - `packages/core/src/auth/ee/`
+  - `packages/server/src/server/auth/ee/`
+    is licensed under the license defined in `ee/LICENSE`.
+
+- All third-party components incorporated into the Mastra Software are
+  licensed under the original license provided by the owner of the
+  applicable component.
+
+- Content outside of the above-mentioned directories or restrictions is
+  available under the "Apache License 2.0" as defined below.
+
 # Apache License 2.0
 
 Copyright (c) 2025 Kepler Software, Inc.

package/dist/docs/SKILL.md

@@ -3,7 +3,7 @@ name: mastra-chroma
 description: Documentation for @mastra/chroma. Use when working with @mastra/chroma APIs, configuration, or implementation.
 metadata:
   package: "@mastra/chroma"
-  version: "1.0.1"
+  version: "1.0.2-alpha.0"
 ---
 
 ## When to use
@@ -16,12 +16,12 @@ Read the individual reference documents for detailed explanations and code examp
 
 ### Docs
 
-- [Retrieval, Semantic Search, Reranking](references/docs-rag-retrieval.md) - Guide on retrieval processes in Mastra's RAG systems, including semantic search, filtering, and re-ranking.
-- [Storing Embeddings in A Vector Database](references/docs-rag-vector-databases.md) - Guide on vector storage options in Mastra, including embedded and dedicated vector databases for similarity search.
+- [Retrieval, semantic search, reranking](references/docs-rag-retrieval.md) - Guide on retrieval processes in Mastra's RAG systems, including semantic search, filtering, and re-ranking.
+- [Storing embeddings in a vector database](references/docs-rag-vector-databases.md) - Guide on vector storage options in Mastra, including embedded and dedicated vector databases for similarity search.
 
 ### Reference
 
-- [Reference: Chroma Vector Store](references/reference-vectors-chroma.md) - Documentation for the ChromaVector class in Mastra, which provides vector search using ChromaDB.
+- [Reference: Chroma vector store](references/reference-vectors-chroma.md) - Documentation for the ChromaVector class in Mastra, which provides vector search using ChromaDB.
 
 
 Read [assets/SOURCE_MAP.json](assets/SOURCE_MAP.json) for source code references.

package/dist/docs/assets/SOURCE_MAP.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.1",
+  "version": "1.0.2-alpha.0",
   "package": "@mastra/chroma",
   "exports": {},
   "modules": {}

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

@@ -1,10 +1,10 @@
-# Retrieval in RAG Systems
+# Retrieval in RAG systems
 
 After storing embeddings, you need to retrieve relevant chunks to answer user queries.
 
 Mastra provides flexible retrieval options with support for semantic search, filtering, and re-ranking.
 
-## How Retrieval Works
+## How retrieval works
 
 1. The user's query is converted to an embedding using the same model used for document embeddings
 2. This embedding is compared to stored embeddings using vector similarity
@@ -14,7 +14,7 @@ Mastra provides flexible retrieval options with support for semantic search, fil
 - Re-ranked for better relevance
 - Processed through a knowledge graph
 
-## Basic Retrieval
+## Basic retrieval
 
 The simplest approach is direct semantic search. This method uses vector similarity to find chunks that are semantically similar to the query:
 
@@ -63,7 +63,7 @@ Results include both the text content and a similarity score:
 ]
 ```
 
-## Advanced Retrieval options
+## Advanced retrieval options
 
 ### Metadata Filtering
 
@@ -272,7 +272,7 @@ import { PGVECTOR_PROMPT } from '@mastra/pg'
 export const ragAgent = new Agent({
   id: 'rag-agent',
   name: 'RAG Agent',
-  model: 'openai/gpt-5.1',
+  model: 'openai/gpt-5.5',
   instructions: `
   Process queries using the provided context. Structure responses to be concise and relevant.
   ${PGVECTOR_PROMPT}
@@ -289,7 +289,7 @@ import { PINECONE_PROMPT } from '@mastra/pinecone'
 export const ragAgent = new Agent({
   id: 'rag-agent',
   name: 'RAG Agent',
-  model: 'openai/gpt-5.1',
+  model: 'openai/gpt-5.5',
   instructions: `
   Process queries using the provided context. Structure responses to be concise and relevant.
   ${PINECONE_PROMPT}
@@ -306,7 +306,7 @@ import { QDRANT_PROMPT } from '@mastra/qdrant'
 export const ragAgent = new Agent({
   id: 'rag-agent',
   name: 'RAG Agent',
-  model: 'openai/gpt-5.1',
+  model: 'openai/gpt-5.5',
   instructions: `
   Process queries using the provided context. Structure responses to be concise and relevant.
   ${QDRANT_PROMPT}
@@ -323,7 +323,7 @@ import { CHROMA_PROMPT } from '@mastra/chroma'
 export const ragAgent = new Agent({
   id: 'rag-agent',
   name: 'RAG Agent',
-  model: 'openai/gpt-5.1',
+  model: 'openai/gpt-5.5',
   instructions: `
   Process queries using the provided context. Structure responses to be concise and relevant.
   ${CHROMA_PROMPT}
@@ -340,7 +340,7 @@ import { ASTRA_PROMPT } from '@mastra/astra'
 export const ragAgent = new Agent({
   id: 'rag-agent',
   name: 'RAG Agent',
-  model: 'openai/gpt-5.1',
+  model: 'openai/gpt-5.5',
   instructions: `
   Process queries using the provided context. Structure responses to be concise and relevant.
   ${ASTRA_PROMPT}
@@ -357,7 +357,7 @@ import { LIBSQL_PROMPT } from '@mastra/libsql'
 export const ragAgent = new Agent({
   id: 'rag-agent',
   name: 'RAG Agent',
-  model: 'openai/gpt-5.1',
+  model: 'openai/gpt-5.5',
   instructions: `
   Process queries using the provided context. Structure responses to be concise and relevant.
   ${LIBSQL_PROMPT}
@@ -374,7 +374,7 @@ import { UPSTASH_PROMPT } from '@mastra/upstash'
 export const ragAgent = new Agent({
   id: 'rag-agent',
   name: 'RAG Agent',
-  model: 'openai/gpt-5.1',
+  model: 'openai/gpt-5.5',
   instructions: `
   Process queries using the provided context. Structure responses to be concise and relevant.
   ${UPSTASH_PROMPT}
@@ -391,7 +391,7 @@ import { VECTORIZE_PROMPT } from '@mastra/vectorize'
 export const ragAgent = new Agent({
   id: 'rag-agent',
   name: 'RAG Agent',
-  model: 'openai/gpt-5.1',
+  model: 'openai/gpt-5.5',
   instructions: `
   Process queries using the provided context. Structure responses to be concise and relevant.
   ${VECTORIZE_PROMPT}
@@ -408,7 +408,7 @@ import { MONGODB_PROMPT } from '@mastra/mongodb'
 export const ragAgent = new Agent({
   id: 'rag-agent',
   name: 'RAG Agent',
-  model: 'openai/gpt-5.1',
+  model: 'openai/gpt-5.5',
   instructions: `
   Process queries using the provided context. Structure responses to be concise and relevant.
   ${MONGODB_PROMPT}
@@ -425,7 +425,7 @@ import { OPENSEARCH_PROMPT } from '@mastra/opensearch'
 export const ragAgent = new Agent({
   id: 'rag-agent',
   name: 'RAG Agent',
-  model: 'openai/gpt-5.1',
+  model: 'openai/gpt-5.5',
   instructions: `
   Process queries using the provided context. Structure responses to be concise and relevant.
   ${OPENSEARCH_PROMPT}
@@ -442,7 +442,7 @@ import { S3VECTORS_PROMPT } from '@mastra/s3vectors'
 export const ragAgent = new Agent({
   id: 'rag-agent',
   name: 'RAG Agent',
-  model: 'openai/gpt-5.1',
+  model: 'openai/gpt-5.5',
   instructions: `
   Process queries using the provided context. Structure responses to be concise and relevant.
   ${S3VECTORS_PROMPT}
@@ -472,7 +472,10 @@ const initialResults = await pgVector.query({
 })
 
 // Create a relevance scorer
-const relevanceProvider = new MastraAgentRelevanceScorer('relevance-scorer', 'openai/gpt-5.1')
+const relevanceProvider = new MastraAgentRelevanceScorer(
+  'relevance-scorer',
+  'openai/gpt-5.5',
+)
 
 // Re-rank the results
 const rerankedResults = await rerank({

package/dist/docs/references/docs-rag-vector-databases.md

@@ -1,8 +1,8 @@
-# Storing Embeddings in A Vector Database
+# Storing embeddings in a vector database
 
 After generating embeddings, you need to store them in a database that supports vector similarity search. Mastra provides a consistent interface for storing and querying embeddings across various vector databases.
 
-## Supported Databases
+## Supported databases
 
 **MongoDB**:
 
@@ -234,7 +234,7 @@ await store.upsert({
 })
 ```
 
-**ElasticSearch**:
+**Elasticsearch**:
 
 ```ts
 import { ElasticSearchVector } from '@mastra/elasticsearch'
@@ -337,7 +337,7 @@ await store.upsert({
 })
 ```
 
-## Using Vector Storage
+## Using vector storage
 
 Once initialized, all vector stores share the same interface for creating indexes, upserting embeddings, and querying.
 
@@ -355,11 +355,11 @@ await store.createIndex({
 
 The dimension size must match the output dimension of your chosen embedding model. Common dimension sizes are:
 
-- OpenAI text-embedding-3-small: 1536 dimensions (or custom, e.g., 256)
-- Cohere embed-multilingual-v3: 1024 dimensions
-- Google gemini-embedding-001: 768 dimensions (or custom)
+- `OpenAI text-embedding-3-small`: 1536 dimensions (or custom, e.g., 256)
+- `Cohere embed-multilingual-v3`: 1024 dimensions
+- `Google gemini-embedding-001`: 768 dimensions (or custom)
 
-> **Warning:** Index dimensions cannot be changed after creation. To use a different model, delete and recreate the index with the new dimension size.
+> **Warning:** Index dimensions can't be changed after creation. To use a different model, delete and recreate the index with the new dimension size.
 
 ### Naming Rules for Databases
 
@@ -490,7 +490,7 @@ Index names must:
 - Example: `My_Index` is not valid (contains uppercase letters)
 - Example: `_myindex` is not valid (begins with underscore)
 
-**ElasticSearch**:
+**Elasticsearch**:
 
 Index names must:
 
@@ -543,7 +543,7 @@ The upsert operation:
 - Creates new vectors if they don't exist
 - Automatically handles batching for large datasets
 
-## Adding Metadata
+## Adding metadata
 
 Vector stores support rich metadata (any JSON-serializable fields) for filtering and organization. Since metadata is stored with no fixed schema, use consistent field naming to avoid unexpected query results.
 
@@ -581,9 +581,9 @@ Key metadata considerations:
 - Only include fields you plan to filter or sort by - extra fields add overhead
 - Add timestamps (e.g., 'createdAt', 'lastUpdated') to track content freshness
 
-## Deleting Vectors
+## Deleting vectors
 
-When building RAG applications, you often need to clean up stale vectors when documents are deleted or updated. Mastra provides the `deleteVectors` method that supports deleting vectors by metadata filters, making it easy to remove all embeddings associated with a specific document.
+When building RAG applications, you often need to clean up stale vectors when documents are deleted or updated. Mastra provides the `deleteVectors` method that supports deleting vectors by metadata filters, making it straightforward to remove all embeddings associated with a specific document.
 
 ### Delete by Metadata Filter
 
@@ -637,7 +637,7 @@ await store.deleteVectors({
 })
 ```
 
-## Best Practices
+## Best practices
 
 - Create indexes before bulk insertions
 - Use batch operations for large insertions (the upsert method handles batching automatically)

package/dist/docs/references/reference-vectors-chroma.md

@@ -1,4 +1,4 @@
-# Chroma Vector Store
+# Chroma vector store
 
 The ChromaVector class provides vector search using [Chroma](https://docs.trychroma.com/docs/overview/getting-started), an open-source embedding database. It offers efficient vector search with metadata filtering and hybrid search capabilities.
 
@@ -10,27 +10,27 @@ The ChromaVector class provides vector search using [Chroma](https://docs.trychr
 >
 > [Get started with Chroma Cloud](https://trychroma.com/signup)
 
-## Constructor Options
+## Constructor options
 
-**host?:** (`string`): The host address of the Chroma server. Defaults to 'localhost'
+**host** (`string`): The host address of the Chroma server. Defaults to 'localhost'
 
-**port?:** (`number`): The port number of the Chroma server. Defaults to 8000
+**port** (`number`): The port number of the Chroma server. Defaults to 8000
 
-**ssl?:** (`boolean`): Whether to use SSL/HTTPS for connections. Defaults to false
+**ssl** (`boolean`): Whether to use SSL/HTTPS for connections. Defaults to false
 
-**apiKey?:** (`string`): A Chroma Cloud API key
+**apiKey** (`string`): A Chroma Cloud API key
 
-**tenant?:** (`string`): The tenant name in the Chroma server to connect to. Defaults to 'default\_tenant' for single-node Chroma. Auto-resolved for Chroma Cloud users based on the provided API key
+**tenant** (`string`): The tenant name in the Chroma server to connect to. Defaults to 'default\_tenant' for single-node Chroma. Auto-resolved for Chroma Cloud users based on the provided API key
 
-**database?:** (`string`): The database name to connect to. Defaults to 'default\_database' for single-node Chroma. Auto-resolved for Chroma Cloud users based on the provided API key
+**database** (`string`): The database name to connect to. Defaults to 'default\_database' for single-node Chroma. Auto-resolved for Chroma Cloud users based on the provided API key
 
-**headers?:** (`Record<string, any>`): Additional HTTP headers to send with requests
+**headers** (`Record<string, any>`): Additional HTTP headers to send with requests
 
-**fetchOptions?:** (`RequestInit`): Additional fetch options for HTTP requests
+**fetchOptions** (`RequestInit`): Additional fetch options for HTTP requests
 
-## Running a Chroma Server
+## Running a Chroma server
 
-If you are a Chroma Cloud user, simply provide the `ChromaVector` constructor your API key, tenant, and database name.
+If you are a Chroma Cloud user, provide the `ChromaVector` constructor your API key, tenant, and database name.
 
 When you install the `@mastra/chroma` package, you get access to the [Chroma CLI](https://docs.trychroma.com/docs/cli/db), which can set these as environment variables for you: `chroma db connect [DB-NAME] --env-file`.
 
@@ -42,37 +42,37 @@ Otherwise, you have several options for setting up your single-node Chroma serve
 
 ## Methods
 
-### createIndex()
+### `createIndex()`
 
-**indexName:** (`string`): Name of the index to create
+**indexName** (`string`): Name of the index to create
 
-**dimension:** (`number`): Vector dimension (must match your embedding model)
+**dimension** (`number`): Vector dimension (must match your embedding model)
 
-**metric?:** (`'cosine' | 'euclidean' | 'dotproduct'`): Distance metric for similarity search (Default: `cosine`)
+**metric** (`'cosine' | 'euclidean' | 'dotproduct'`): Distance metric for similarity search (Default: `cosine`)
 
-### forkIndex()
+### `forkIndex()`
 
 Note: Forking is only supported on Chroma Cloud, or if you deploy your own OSS **distributed** Chroma.
 
-`forkIndex` lets you fork an existing Chroma index instantly. Operations on the forked index do not affect the original one. Learn more on the [Chroma docs](https://docs.trychroma.com/cloud/collection-forking).
+`forkIndex` lets you fork an existing Chroma index instantly. Operations on the forked index don't affect the original one. Learn more on the [Chroma docs](https://docs.trychroma.com/cloud/collection-forking).
 
-**indexName:** (`string`): Name of the index to fork
+**indexName** (`string`): Name of the index to fork
 
-**newIndexName:** (`string`): The name of the forked index
+**newIndexName** (`string`): The name of the forked index
 
-### upsert()
+### `upsert()`
 
-**indexName:** (`string`): Name of the index to upsert into
+**indexName** (`string`): Name of the index to upsert into
 
-**vectors:** (`number[][]`): Array of embedding vectors
+**vectors** (`number[][]`): Array of embedding vectors
 
-**metadata?:** (`Record<string, any>[]`): Metadata for each vector
+**metadata** (`Record<string, any>[]`): Metadata for each vector
 
-**ids?:** (`string[]`): Optional vector IDs (auto-generated if not provided)
+**ids** (`string[]`): Optional vector IDs (auto-generated if not provided)
 
-**documents?:** (`string[]`): Chroma-specific: Original text documents associated with the vectors
+**documents** (`string[]`): Chroma-specific: Original text documents associated with the vectors
 
-### query()
+### `query()`
 
 Query an index using a `queryVector`. Returns an array of semantically similar records in order of distance from the `queryVector`. Each record has the shape:
 
@@ -88,19 +88,19 @@ Query an index using a `queryVector`. Returns an array of semantically similar r
 
 You can also provide the shape of your metadata to a `query` call for type inference: `query<T>()`.
 
-**indexName:** (`string`): Name of the index to query
+**indexName** (`string`): Name of the index to query
 
-**queryVector:** (`number[]`): Query vector to find similar vectors
+**queryVector** (`number[]`): Query vector to find similar vectors
 
-**topK?:** (`number`): Number of results to return (Default: `10`)
+**topK** (`number`): Number of results to return (Default: `10`)
 
-**filter?:** (`Record<string, any>`): Metadata filters for the query
+**filter** (`Record<string, any>`): Metadata filters for the query
 
-**includeVector?:** (`boolean`): Whether to include vectors in the results (Default: `false`)
+**includeVector** (`boolean`): Whether to include vectors in the results (Default: `false`)
 
-**documentFilter?:** (`Record<string, any>`): Chroma-specific: Filter to apply on the document content
+**documentFilter** (`Record<string, any>`): Chroma-specific: Filter to apply on the document content
 
-### get()
+### `get()`
 
 Get records from your Chroma index by IDs, metadata, and document filters. It returns an array of records of the shape:
 
@@ -115,27 +115,27 @@ Get records from your Chroma index by IDs, metadata, and document filters. It re
 
 You can also provide the shape of your metadata to a `get` call for type inference: `get<T>()`.
 
-**indexName:** (`string`): Name of the index to query
+**indexName** (`string`): Name of the index to query
 
-**ids?:** (`string[]`): A list of record IDs to return. If not provided, all records are returned.
+**ids** (`string[]`): A list of record IDs to return. If not provided, all records are returned.
 
-**filter?:** (`Record<string, any>`): Metadata filters.
+**filter** (`Record<string, any>`): Metadata filters.
 
-**includeVector?:** (`boolean`): Whether to include vectors in the results (Default: `false`)
+**includeVector** (`boolean`): Whether to include vectors in the results (Default: `false`)
 
-**documentFilter?:** (`Record<string, any>`): Chroma-specific: Filter to apply on the document content
+**documentFilter** (`Record<string, any>`): Chroma-specific: Filter to apply on the document content
 
-**limit?:** (`number`): The maximum number of records to return (Default: `100`)
+**limit** (`number`): The maximum number of records to return (Default: `100`)
 
-**offset?:** (`number`): Offset for returning records. Use with \`limit\` to paginate results.
+**offset** (`number`): Offset for returning records. Use with \`limit\` to paginate results.
 
-### listIndexes()
+### `listIndexes()`
 
 Returns an array of index names as strings.
 
-### describeIndex()
+### `describeIndex()`
 
-**indexName:** (`string`): Name of the index to describe
+**indexName** (`string`): Name of the index to describe
 
 Returns:
 
@@ -147,27 +147,27 @@ interface IndexStats {
 }
 ```
 
-### deleteIndex()
+### `deleteIndex()`
 
-**indexName:** (`string`): Name of the index to delete
+**indexName** (`string`): Name of the index to delete
 
-### updateVector()
+### `updateVector()`
 
 Update a single vector by ID or by metadata filter. Either `id` or `filter` must be provided, but not both.
 
-**indexName:** (`string`): Name of the index containing the vector to update
+**indexName** (`string`): Name of the index containing the vector to update
 
-**id?:** (`string`): ID of the vector to update (mutually exclusive with filter)
+**id** (`string`): ID of the vector to update (mutually exclusive with filter)
 
-**filter?:** (`Record<string, any>`): Metadata filter to identify vector(s) to update (mutually exclusive with id)
+**filter** (`Record<string, any>`): Metadata filter to identify vector(s) to update (mutually exclusive with id)
 
-**update:** (`object`): Update parameters
+**update** (`object`): Update parameters
 
 The `update` object can contain:
 
-**vector?:** (`number[]`): New vector to replace the existing one
+**vector** (`number[]`): New vector to replace the existing one
 
-**metadata?:** (`Record<string, any>`): New metadata to replace the existing metadata
+**metadata** (`Record<string, any>`): New metadata to replace the existing metadata
 
 Example:
 
@@ -187,21 +187,21 @@ await vectorStore.updateVector({
 })
 ```
 
-### deleteVector()
+### `deleteVector()`
 
-**indexName:** (`string`): Name of the index containing the vector to delete
+**indexName** (`string`): Name of the index containing the vector to delete
 
-**id:** (`string`): ID of the vector to delete
+**id** (`string`): ID of the vector to delete
 
-### deleteVectors()
+### `deleteVectors()`
 
 Delete multiple vectors by IDs or by metadata filter. This method enables bulk deletion and source-based vector management. Either `ids` or `filter` must be provided, but not both.
 
-**indexName:** (`string`): Name of the index containing the vectors to delete
+**indexName** (`string`): Name of the index containing the vectors to delete
 
-**ids?:** (`string[]`): Array of vector IDs to delete (mutually exclusive with filter)
+**ids** (`string[]`): Array of vector IDs to delete (mutually exclusive with filter)
 
-**filter?:** (`Record<string, any>`): Metadata filter to identify vectors to delete (mutually exclusive with ids)
+**filter** (`Record<string, any>`): Metadata filter to identify vectors to delete (mutually exclusive with ids)
 
 Example:
 
@@ -227,7 +227,7 @@ await vectorStore.deleteVectors({
 })
 ```
 
-## Response Types
+## Response types
 
 Query results are returned in this format:
 
@@ -241,7 +241,7 @@ interface QueryResult {
 }
 ```
 
-## Error Handling
+## Error handling
 
 The store throws typed errors that can be caught:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mastra/chroma",
-  "version": "1.0.1",
+  "version": "1.0.2-alpha.0",
   "description": "Chroma vector store provider for Mastra",
   "type": "module",
   "main": "dist/index.js",
@@ -20,20 +20,21 @@
   },
   "license": "Apache-2.0",
   "dependencies": {
-    "chromadb": "^3.1.6"
+    "chromadb": "^3.3.3"
   },
   "devDependencies": {
-    "@types/node": "22.19.7",
-    "@vitest/coverage-v8": "4.0.18",
-    "@vitest/ui": "4.0.18",
-    "eslint": "^9.37.0",
+    "@types/node": "22.19.21",
+    "@vitest/coverage-v8": "4.1.8",
+    "@vitest/ui": "4.1.8",
+    "eslint": "^10.4.1",
     "tsup": "^8.5.1",
-    "typescript": "^5.9.3",
-    "vitest": "4.0.18",
-    "@internal/lint": "0.0.63",
-    "@internal/storage-test-utils": "0.0.59",
-    "@internal/types-builder": "0.0.38",
-    "@mastra/core": "1.8.0"
+    "tsx": "^4.22.4",
+    "typescript": "^6.0.3",
+    "vitest": "4.1.8",
+    "@internal/lint": "0.0.105",
+    "@internal/storage-test-utils": "0.0.101",
+    "@internal/types-builder": "0.0.80",
+    "@mastra/core": "1.43.1-alpha.0"
   },
   "peerDependencies": {
     "@mastra/core": ">=1.0.0-0 <2.0.0-0"
@@ -57,7 +58,7 @@
   "scripts": {
     "build:lib": "tsup --silent --config tsup.config.ts",
     "build:watch": "tsup --watch --silent --config tsup.config.ts",
-    "pretest": "docker compose up -d",
+    "pretest": "docker compose up -d --wait",
     "posttest": "docker compose down -v",
     "test": "vitest run",
     "lint": "eslint ."