Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion examples/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@
"@types/node": "^22.5.5",
"tsx": "^4.19.2",
"typescript": "^5.0.0",
"vitest": "^4.0.17",
"vitest": "^4.1.0",
"zod": "^4.1.12"
},
"dependencies": {
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@
"typedoc": "^0.25.13",
"typescript": "^5.9.3",
"vite": "^7.3.1",
"vitest": "^4.0.17"
"vitest": "^4.1.0"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 @vitest/coverage-v8 pinned at 4.0.17 while vitest bumped to ^4.1.0 creates peer dependency mismatch

@vitest/coverage-v8 is pinned at exact version 4.0.17 in the root package.json:33, but vitest was bumped to ^4.1.0 (package.json:51). The lockfile confirms @vitest/coverage-v8@4.0.17 declares an exact peer dependency on vitest: 4.0.17, yet resolves against vitest@4.1.0. This version mismatch can cause runtime issues when collecting code coverage (e.g. pnpm test -- --coverage) because @vitest/coverage-v8 relies on vitest internals that may change between minor versions.

Prompt for agents
The root package.json has @vitest/coverage-v8 pinned at exact version 4.0.17 (line 33) while vitest was bumped to ^4.1.0 (line 51). These packages are designed to be used at matching versions — @vitest/coverage-v8 declares an exact peer dependency on the corresponding vitest version. Update @vitest/coverage-v8 to 4.1.0 (or ^4.1.0) to match the vitest version bump and re-run pnpm install to update the lockfile.
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

},
"packageManager": "pnpm@9.7.0",
"pnpm": {
Expand Down
2 changes: 1 addition & 1 deletion plugins/assemblyai/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@
"typescript": "^5.0.0"
},
"dependencies": {
"ws": "^8.16.0"
"ws": "^8.21.0"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚩 ws version in assemblyai now higher than catalog minimum

The ws dependency in plugins/assemblyai/package.json was bumped from ^8.16.0 to ^8.21.0, while the pnpm catalog (pnpm-lock.yaml catalogs section) specifies ws: ^8.18.0 resolving to 8.20.1. The assemblyai plugin declares its own ws dependency (not using catalog:) so this is independent. However, the minimum version 8.21.0 is now higher than what the catalog resolves to (8.20.1). This won't cause issues if the lockfile resolves a compatible version for assemblyai specifically, but it's worth noting the divergence from the catalog pattern used by other packages.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

},
"peerDependencies": {
"@livekit/agents": "workspace:*",
Expand Down
2 changes: 1 addition & 1 deletion plugins/mistralai/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@
"@microsoft/api-extractor": "^7.35.0",
"tsup": "^8.3.5",
"typescript": "^5.0.0",
"vitest": "^4.0.17"
"vitest": "^4.1.0"
},
"dependencies": {
"@mistralai/mistralai": "^2.2.1"
Expand Down
2 changes: 1 addition & 1 deletion plugins/test/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@
},
"dependencies": {
"fastest-levenshtein": "^1.0.16",
"vitest": "^4.0.17"
"vitest": "^4.1.0"
},
"peerDependencies": {
"@livekit/agents": "workspace:*",
Expand Down
Loading
Loading