Update @sentry/electron to 7.15.0 to resolve Dependabot alert #241 - #4241
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Collaborator
📊 Performance Test ResultsComparing 758b9d5 vs trunk app-size
site-editor
site-startup
Results are median values from multiple test runs. Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change (<50ms diff) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issues
How AI was used in this PR
Claude Code performed the dependency bump, ran the verification suite (typecheck + affected tests +
npm audit), and drafted this PR. The author reviewed the changes.Proposed Changes
Bumps
@sentry/electronfrom7.13.0to7.15.0to resolve a Dependabot security alert on a transitive Sentry dependency. The update carries the Sentry core subtree forward (@sentry/*10.50.0→10.62.0), which is where the vulnerable package lived.No behavior change for users — this is a security-maintenance update. The Sentry API surface Studio relies on (
init,setUser,captureException) is unchanged.Testing Instructions
npm installnpm run typecheck— passes across all workspacesnpm test -- apps/studio/src/tests/index.test.ts apps/studio/src/tests/updates.test.ts apps/studio/src/tests/ipc-handlers.test.ts— Sentry-touching tests pass (22/22)npm audit— no remaining Sentry-related advisoriesPre-merge Checklist