chore(deps): bump exa-js from 1.10.3 to 2.12.1 in /backend#841
chore(deps): bump exa-js from 1.10.3 to 2.12.1 in /backend#841dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [exa-js](https://github.com/exa-labs/exa-js) from 1.10.3 to 2.12.1. - [Release notes](https://github.com/exa-labs/exa-js/releases) - [Commits](https://github.com/exa-labs/exa-js/commits) --- updated-dependencies: - dependency-name: exa-js dependency-version: 2.12.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit e54f216. Configure here.
| "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.
Lockfile not updated to match new major version
High Severity
The package.json declares "exa-js": "^2.12.1" but the bun.lock still declares "exa-js": "^1.0.11" in the workspace section and resolves to exa-js@1.10.2. This mismatch means bun 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.
| "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.
Major version bump may break undocumented extras option
Medium Severity
The getContents call in exa.ts passes extras: { imageLinks: 1 } which does not appear in any exa-js v2 documentation. When v2.12.1 is actually installed, this option may be silently ignored or rejected, resulting in image link data no longer being included in fetch-content responses — a silent loss of functionality with no error surfaced to callers.
Reviewed by Cursor Bugbot for commit e54f216. Configure here.
PR Metrics
Updated Wed, 06 May 2026 19:45:53 GMT · run #1404 |
Bumps exa-js from 1.10.3 to 2.12.1.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Note
Medium Risk
Updates a major-version dependency (
exa-js1.x → 2.x), which may introduce breaking API/behavior changes in any Exa integration paths at runtime despite being a small diff.Overview
Bumps the backend dependency
exa-jsfrom the 1.x line to^2.12.1inbackend/package.json.Reviewed by Cursor Bugbot for commit e54f216. Bugbot is set up for automated code reviews on this repo. Configure here.