Skip to content

chore(deps): update dependency @sentry/node to v10 #25

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.

Sign up for GitHub

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

Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dependency @sentry/node to v10 #25

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@
"zod": "^3.22.0"
},
"devDependencies": {
"@sentry/node": "^9.4.0",
"@sentry/node": "^10.0.0",

@devin-ai-integration devin-ai-integration Bot Aug 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔍 @sentry/node is declared but never used anywhere in the repo

A repo-wide search finds no reference to @sentry/node outside package.json (no imports in src/, scripts/, or tsup.config.ts). This major-version bump therefore has no code impact, but it also suggests the devDependency is dead weight and could simply be removed instead of being maintained by dependency bots.

Open in Devin Review

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

@devin-ai-integration devin-ai-integration Bot Aug 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔍 Verify Sentry v10 runtime requirement against declared engines

engines.node is >=18.0.0. Sentry SDK v10 raised its minimum supported Node version relative to v9; if the new minimum exceeds 18.0.0, installs on the low end of the supported range could warn or fail. Since the package is unused at runtime this is low risk, but worth confirming against the Sentry v10 migration notes before merge.

Open in Devin Review

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

"@types/inquirer": "^9.0.7",
"@types/node": "^22.13.0",
"@types/ws": "^8.5.14",
Expand Down
Loading