Skip to content

Conversation

@chargome
Copy link
Member

@chargome chargome commented Jan 2, 2026

We want to prevent having a vulnerable version in our deps, this change will only affect how we use types internally and is not breaking.

closes #18645

@chargome chargome self-assigned this Jan 2, 2026
@linear
Copy link

linear bot commented Jan 2, 2026

@chargome chargome marked this pull request as draft January 2, 2026 09:49
@github-actions
Copy link
Contributor

github-actions bot commented Jan 2, 2026

node-overhead report 🧳

Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.

Scenario Requests/s % of Baseline Prev. Requests/s Change %
GET Baseline 8,861 - 8,716 +2%
GET With Sentry 1,694 19% 1,605 +6%
GET With Sentry (error only) 6,133 69% 5,980 +3%
POST Baseline 1,192 - 1,184 +1%
POST With Sentry 544 46% 573 -5%
POST With Sentry (error only) 1,055 89% 1,054 +0%
MYSQL Baseline 3,337 - 3,219 +4%
MYSQL With Sentry 459 14% 366 +25%
MYSQL With Sentry (error only) 2,723 82% 2,653 +3%

View base workflow run

@chargome chargome marked this pull request as ready for review January 2, 2026 11:48
@chargome chargome requested a review from logaretm January 2, 2026 11:48
@chargome chargome merged commit ba7f90a into develop Jan 2, 2026
208 checks passed
@chargome chargome deleted the cg/JS-1376/next-vulnerability-in-getsentrysentry-javascript branch January 2, 2026 11:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

next vulnerability in getsentry/sentry-javascript

3 participants