-
Notifications
You must be signed in to change notification settings - Fork 313
chore(deps): bump exa-js from 1.10.3 to 2.12.1 in /backend #841
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -34,7 +34,7 @@ | |
| "dotenv": "^17.2.3", | ||
| "drizzle-orm": "^0.45.2", | ||
| "elysia": "^1.4.28", | ||
| "exa-js": "^1.0.11", | ||
| "exa-js": "^2.12.1", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Major version bump may break undocumented
|
||
| "ipaddr.js": "^2.3.0", | ||
| "jose": "^6.2.2", | ||
| "openai": "^6.34.0", | ||
|
|
||


There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lockfile not updated to match new major version
High Severity
The
package.jsondeclares"exa-js": "^2.12.1"but thebun.lockstill declares"exa-js": "^1.0.11"in the workspace section and resolves toexa-js@1.10.2. This mismatch meansbun install --frozen-lockfile(typical in CI) will fail, and any fresh install will pull v2.x which may break the application due to major version API changes without corresponding code updates.Reviewed by Cursor Bugbot for commit e54f216. Configure here.