[Snyk] Upgrade @sentry/browser from 9.10.0 to 9.17.0 #386
Conversation
Snyk has created this PR to upgrade @sentry/browser from 9.10.0 to 9.17.0. See this package in npm: @sentry/browser See this project in Snyk: https://app.snyk.io/org/reisene/project/3b48baaa-833b-4239-b348-16091472ee83?utm_source=github&utm_medium=referral&page=upgrade-pr
|
Aviator Changeset actions:
|
Current Aviator status
This PR was merged using Aviator.
See the real-time status of this PR on the
Aviator webapp.
Use the Aviator Chrome Extension
to see the status of your PR within GitHub.
|
|
Review changes with |
|
Please follow naming conventions! 😿 |
|
Important Review skippedIgnore keyword(s) in the title. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) |
Przewodnik RecenzentaZaktualizuj zależność @sentry/browser z wersji 9.10.0 do 9.17.0, aktualizując wersję w pliku package.json i regenerując plik blokady, aby uchwycić nowe rozwiązanie zależności. Diagram Sekwencji: Raportowanie Telemetrii z Zaktualizowanym @sentry/browsersequenceDiagram
participant UserApp as "Aplikacja Użytkownika"
participant SentryLib as "@sentry/browser v9.17.0"
participant SentryService as "Usługa Sentry"
UserApp->>SentryLib: captureException(error)
activate SentryLib
SentryLib->>SentryService: Przesyłanie Danych o Błędach (potencjalnie z ulepszeniami/poprawkami v9.17.0)
activate SentryService
SentryService-->>SentryLib: Potwierdzenie
deactivate SentryService
SentryLib-->>UserApp: Powrót
deactivate SentryLib
UserApp->>SentryLib: startTransaction(context)
activate SentryLib
SentryLib->>SentryService: Przesyłanie Danych o Wydajności (potencjalnie z ulepszeniami/poprawkami v9.17.0)
activate SentryService
SentryService-->>SentryLib: Potwierdzenie
deactivate SentryService
SentryLib-->>UserApp: Powrót
deactivate SentryLib
Zmiany na Poziomie Pliku
Wskazówki i poleceniaInterakcja z Sourcery
Dostosowywanie DoświadczeniaUzyskaj dostęp do swojego panelu, aby:
Uzyskiwanie Pomocy
Original review guide in EnglishReviewer's GuideUpgrade the @sentry/browser dependency from 9.10.0 to 9.17.0 by updating the version in package.json and regenerating the lockfile to capture the new dependency resolution. Sequence Diagram: Telemetry Reporting with Updated @sentry/browsersequenceDiagram
participant UserApp as "User Application"
participant SentryLib as "@sentry/browser v9.17.0"
participant SentryService as "Sentry Service"
UserApp->>SentryLib: captureException(error)
activate SentryLib
SentryLib->>SentryService: Transmit Error Data (potentially with v9.17.0 enhancements/fixes)
activate SentryService
SentryService-->>SentryLib: Acknowledgment
deactivate SentryService
SentryLib-->>UserApp: Return
deactivate SentryLib
UserApp->>SentryLib: startTransaction(context)
activate SentryLib
SentryLib->>SentryService: Transmit Performance Data (potentially with v9.17.0 enhancements/fixes)
activate SentryService
SentryService-->>SentryLib: Acknowledgment
deactivate SentryService
SentryLib-->>UserApp: Return
deactivate SentryLib
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hello @reisene, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
Summary of Changes
Hello team, gemini-code-assist here with a summary of this pull request. This PR, automatically generated by Snyk, aims to upgrade the @sentry/browser dependency from version 9.10.0 to 9.17.0. This is a significant version jump, covering 9 minor releases, and includes various fixes, features, and internal dependency updates as detailed in the Snyk description's release notes. The primary goal is to keep the project's dependencies up-to-date, which helps in addressing existing vulnerabilities and quickly identifying new ones.
Highlights
- Dependency Upgrade: The core change is the upgrade of the
@sentry/browserpackage from version9.10.0to9.17.0. - Internal Dependency Updates: Related internal Sentry packages (
@sentry-internal/browser-utils,@sentry-internal/feedback,@sentry-internal/replay,@sentry-internal/replay-canvas,@sentry/core) are also updated to version9.17.0. - Dependency Tree Cleanup: The
package-lock.jsonshows the removal of nested@sentry/coreentries under other Sentry packages (@sentry/node,@sentry/opentelemetry,@sentry/profiling-node), suggesting a potential flattening or optimization of the dependency tree.
Changelog
- package-lock.json
- Updated
@sentry/browserversion and integrity hash. - Updated versions and integrity hashes for internal Sentry dependencies (
@sentry-internal/browser-utils,@sentry-internal/feedback,@sentry-internal/replay,@sentry-internal/replay-canvas,@sentry/core). - Removed nested
@sentry/coreentries under@sentry/node,@sentry/opentelemetry, and@sentry/profiling-node.
- Updated
- package.json
- Updated the dependency range for
@sentry/browserfrom^9.10.0to^9.17.0.
- Updated the dependency range for
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
A version jumps ahead,
New features now are spread.
Check the lock file,
Stay a while,
Ensure no bugs are bred.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
|
Skipping bot pull request creation because the queue is empty and this pull request is up to date with |
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 Do not merge outdated PRsWonderful, this rule succeeded.Make sure PRs are almost up to date before merging
|
|
Here's the code health analysis summary for commits Analysis Summary
|
|
There was a problem hiding this comment.
Code Review
This pull request, automatically generated by Snyk, upgrades the @sentry/browser package from version 9.10.0 to 9.17.0. This is a beneficial update for keeping dependencies current.
The changes primarily involve updates to package.json and package-lock.json to reflect the new version and its transitive dependencies. Notably, this upgrade also brings @sentry/core to version 9.17.0. This core package is utilized by other Sentry libraries in your project, such as @sentry/node (currently at 9.0.1) and @sentry/profiling-node (at 9.17.0).
The update to package-lock.json indicates that npm has successfully deduplicated @sentry/core, ensuring a single version (9.17.0) is used across these Sentry packages. This is generally a positive outcome for consistency and potentially for bundle size.
Given the jump of several minor versions for @sentry/browser and the critical role of @sentry/core, thorough testing is highly recommended. This testing should cover Sentry's error reporting functionality in both browser-side code (e.g., src/js/script.js) and any Node.js contexts where Sentry is used (e.g., gulpfile.js). Please pay attention to any behavioral changes noted in the Sentry release notes for versions 9.10.1 through 9.17.0, particularly for @sentry/core and @sentry/node if applicable to your usage.
Summary of Findings
- Comprehensive Testing for Sentry Core Upgrade: The upgrade to
@sentry/[email protected]also upgrades the shared@sentry/coreto9.17.0. This core library is used by other Sentry packages in the project, including@sentry/[email protected]. Due to this shared dependency and the version jump, comprehensive testing is crucial to ensure continued compatibility and no regressions in error reporting across all parts of the application using Sentry (both browser and Node.js contexts).
Merge Readiness
This PR upgrades @sentry/browser and its core dependencies, which is a positive step for maintaining an up-to-date and secure codebase. The package version changes appear correct. The most important consideration is the potential impact of upgrading @sentry/core across multiple Sentry packages used in the project.
I recommend that this PR be merged after thorough testing has been conducted to validate Sentry's functionality in both browser and Node.js environments, ensuring no regressions or unexpected behaviors are introduced. Please refer to the Sentry release notes for any pertinent changes.
As an AI reviewer, I am not authorized to approve pull requests. Please ensure this change is reviewed and approved by a human maintainer after successful testing.
| "version": "9.17.0", | ||
| "resolved": "https://registry.npmjs.org/@sentry/core/-/core-9.17.0.tgz", | ||
| "integrity": "sha512-9f1A93/kY9lLH06L1thPx94IhyLjEP3aRxYAtjtBfzId8UtubSpwP92sbxgslodD73R4tURwWJj7nYZ9HLYBUg==", |
There was a problem hiding this comment.
The @sentry/core package has been upgraded from 9.10.0 to 9.17.0 as a result of the @sentry/browser upgrade. This is a significant jump for a core library.
Could you confirm that thorough testing will be performed to ensure this update doesn't introduce regressions or unexpected behavior? Specifically:
- Browser Context: Verify error reporting via
@sentry/browserinsrc/js/script.jscontinues to function as expected. - Node.js Context: Since
@sentry/[email protected]will now also be used by@sentry/[email protected](as used ingulpfile.js), please test Sentry functionality in this environment too. While Sentry aims for backward compatibility within major versions, changes in core can sometimes have subtle impacts.
Reviewing the release notes for @sentry/core between these versions for any breaking changes or significant behavioral modifications would also be prudent.
Snyk has created this PR to upgrade @sentry/browser from 9.10.0 to 9.17.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 9 versions ahead of your current version.
The recommended version was released 22 days ago.
Release notes
Package name: @sentry/browser
-
9.17.0 - 2025-05-08
- feat(node): Migrate to
Path
Size
@ sentry/browser
23.35 KB
@ sentry/browser - with treeshaking flags
23.19 KB
@ sentry/browser (incl. Tracing)
37.25 KB
@ sentry/browser (incl. Tracing, Replay)
74.47 KB
@ sentry/browser (incl. Tracing, Replay) - with treeshaking flags
68.34 KB
@ sentry/browser (incl. Tracing, Replay with Canvas)
79.12 KB
@ sentry/browser (incl. Tracing, Replay, Feedback)
90.93 KB
@ sentry/browser (incl. Feedback)
39.75 KB
@ sentry/browser (incl. sendFeedback)
27.98 KB
@ sentry/browser (incl. FeedbackAsync)
32.74 KB
@ sentry/react
25.16 KB
@ sentry/react (incl. Tracing)
39.24 KB
@ sentry/vue
27.63 KB
@ sentry/vue (incl. Tracing)
39.01 KB
@ sentry/svelte
23.38 KB
CDN Bundle
24.55 KB
CDN Bundle (incl. Tracing)
37.29 KB
CDN Bundle (incl. Tracing, Replay)
72.33 KB
CDN Bundle (incl. Tracing, Replay, Feedback)
77.64 KB
CDN Bundle - uncompressed
71.62 KB
CDN Bundle (incl. Tracing) - uncompressed
110.34 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed
221.63 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed
234.15 KB
@ sentry/nextjs (client)
40.84 KB
@ sentry/sveltekit (client)
37.73 KB
@ sentry/node
151.37 KB
@ sentry/node - without tracing
95.77 KB
@ sentry/aws-serverless
120.16 KB
-
9.16.1 - 2025-05-07
- fix(core): Make sure logs get flushed in server-runtime-client (#16222)
- ref(node): Remove vercel flushing code that does nothing (#16217)
Path
Size
@ sentry/browser
23.35 KB
@ sentry/browser - with treeshaking flags
23.19 KB
@ sentry/browser (incl. Tracing)
37.25 KB
@ sentry/browser (incl. Tracing, Replay)
74.47 KB
@ sentry/browser (incl. Tracing, Replay) - with treeshaking flags
68.34 KB
@ sentry/browser (incl. Tracing, Replay with Canvas)
79.12 KB
@ sentry/browser (incl. Tracing, Replay, Feedback)
90.93 KB
@ sentry/browser (incl. Feedback)
39.75 KB
@ sentry/browser (incl. sendFeedback)
27.98 KB
@ sentry/browser (incl. FeedbackAsync)
32.74 KB
@ sentry/react
25.16 KB
@ sentry/react (incl. Tracing)
39.24 KB
@ sentry/vue
27.63 KB
@ sentry/vue (incl. Tracing)
39.01 KB
@ sentry/svelte
23.38 KB
CDN Bundle
24.55 KB
CDN Bundle (incl. Tracing)
37.29 KB
CDN Bundle (incl. Tracing, Replay)
72.33 KB
CDN Bundle (incl. Tracing, Replay, Feedback)
77.64 KB
CDN Bundle - uncompressed
71.62 KB
CDN Bundle (incl. Tracing) - uncompressed
110.34 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed
221.63 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed
234.15 KB
@ sentry/nextjs (client)
40.84 KB
@ sentry/sveltekit (client)
37.73 KB
@ sentry/node
143.93 KB
@ sentry/node - without tracing
95.77 KB
@ sentry/aws-serverless
120.16 KB
-
9.16.0 - 2025-05-07
- feat: Create a Vite plugin that injects sentryConfig into the global config (#16197)
- feat(browser): Add option to sample linked traces consistently (#16037)
- feat(cloudflare): Add support for durable objects (#16180)
- feat(node): Add Prisma integration by default (#16073)
- feat(react-router): Add client-side router instrumentation (#16185)
- fix(node): Avoid double-wrapping http module (#16177)
- feat(cloudflare): Add logs exports (#16165)
- feat(vercel-edge): Add logs export (#16166)
- feat(cloudflare): Read
- feat(node): Drop
- fix(browser): Respect manually set sentry tracing headers in XHR requests (#16184)
- fix(core): Respect manually set sentry tracing headers in fetch calls (#16183)
- fix(feedback): Prevent
- fix(node): Use class constructor in docstring for winston transport (#16167)
- fix(node): Fix vercel flushing logic & add test for it (#16208)
- fix(node): Fix 404 route handling in express 5 (#16211)
- fix(logs): Ensure logs can be flushed correctly (#16216)
- ref(core): Switch to standardized log envelope (#16133)
Path
Size
@ sentry/browser
23.35 KB
@ sentry/browser - with treeshaking flags
23.19 KB
@ sentry/browser (incl. Tracing)
37.25 KB
@ sentry/browser (incl. Tracing, Replay)
74.47 KB
@ sentry/browser (incl. Tracing, Replay) - with treeshaking flags
68.34 KB
@ sentry/browser (incl. Tracing, Replay with Canvas)
79.12 KB
@ sentry/browser (incl. Tracing, Replay, Feedback)
90.93 KB
@ sentry/browser (incl. Feedback)
39.75 KB
@ sentry/browser (incl. sendFeedback)
27.98 KB
@ sentry/browser (incl. FeedbackAsync)
32.74 KB
@ sentry/react
25.16 KB
@ sentry/react (incl. Tracing)
39.24 KB
@ sentry/vue
27.63 KB
@ sentry/vue (incl. Tracing)
39.01 KB
@ sentry/svelte
23.38 KB
CDN Bundle
24.55 KB
CDN Bundle (incl. Tracing)
37.29 KB
CDN Bundle (incl. Tracing, Replay)
72.33 KB
CDN Bundle (incl. Tracing, Replay, Feedback)
77.64 KB
CDN Bundle - uncompressed
71.62 KB
CDN Bundle (incl. Tracing) - uncompressed
110.34 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed
221.63 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed
234.15 KB
@ sentry/nextjs (client)
40.84 KB
@ sentry/sveltekit (client)
37.73 KB
@ sentry/node
144.43 KB
@ sentry/node - without tracing
96.3 KB
@ sentry/aws-serverless
120.66 KB
-
9.15.0 - 2025-04-29
- feat: Export
- feat(core): Associate resource/tool/prompt invocations with request span instead of response span (#16126)
- fix: Vercel
- fix(node): Update version range for
- fix(react-router): Spread
- fix(react): Fix Redux integration failing with reducer injection (#16106)
- fix(remix): Add ESM-compatible exports (#16124)
- fix(remix): Avoid rewrapping root loader. (#16136)
Path
Size
@ sentry/browser
23.28 KB
@ sentry/browser - with treeshaking flags
23.1 KB
@ sentry/browser (incl. Tracing)
36.93 KB
@ sentry/browser (incl. Tracing, Replay)
74.1 KB
@ sentry/browser (incl. Tracing, Replay) - with treeshaking flags
67.47 KB
@ sentry/browser (incl. Tracing, Replay with Canvas)
78.76 KB
@ sentry/browser (incl. Tracing, Replay, Feedback)
90.58 KB
@ sentry/browser (incl. Feedback)
39.68 KB
@ sentry/browser (incl. sendFeedback)
27.9 KB
@ sentry/browser (incl. FeedbackAsync)
32.67 KB
@ sentry/react
25.09 KB
@ sentry/react (incl. Tracing)
38.93 KB
@ sentry/vue
27.5 KB
@ sentry/vue (incl. Tracing)
38.69 KB
@ sentry/svelte
23.31 KB
CDN Bundle
24.49 KB
CDN Bundle (incl. Tracing)
36.96 KB
CDN Bundle (incl. Tracing, Replay)
72 KB
CDN Bundle (incl. Tracing, Replay, Feedback)
77.3 KB
CDN Bundle - uncompressed
71.5 KB
CDN Bundle (incl. Tracing) - uncompressed
109.33 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed
220.62 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed
233.15 KB
@ sentry/nextjs (client)
40.51 KB
@ sentry/sveltekit (client)
37.41 KB
@ sentry/node
143.4 KB
@ sentry/node - without tracing
96.49 KB
@ sentry/aws-serverless
120.81 KB
-
9.14.0 - 2025-04-23
-
9.13.0 - 2025-04-16
-
9.12.0 - 2025-04-08
-
9.11.0 - 2025-04-03
-
9.10.1 - 2025-03-28
-
9.10.0 - 2025-03-27
from @sentry/browser GitHub release notes@ fastify/otel(#15542)Bundle size 📦
Bundle size 📦
Important changes
Add a new plugin
makeConfigInjectorPluginwithin our existing vite plugin that updates the global vite config with sentry optionsThis PR implements consistent sampling across traces as outlined in (#15754)
This PR introduces a new
instrumentDurableObjectWithSentrymethod to the SDK, which instruments durable objects. We capture both traces and errors automatically.Prisma integration is enabled by default, it should work for both ESM and CJS.
Adds client-side instrumentation for react router's
HydratedRouter. To enable it, simply replacebrowserTracingIntegration()withreactRouterTracingIntegration()in your client-side init call.When running your application in ESM mode, there have been scenarios that resulted in the
http/httpsemitting duplicate spans for incoming requests. This was apparently caused by us double-wrapping the modules for incoming request isolation.In order to solve this problem, the modules are no longer monkey patched by us for request isolation. Instead, we register diagnosticschannel hooks to handle request isolation now.
While this is generally not expected to break anything, there is one tiny change that _may affect you if you have been relying on very specific functionality:
The
ignoreOutgoingRequestsoption ofhttpIntegrationreceives theRequestOptionsas second argument. This type is not changed, however due to how the wrapping now works, we no longer pass through the full RequestOptions, but re-construct this partially based on the generated request. For the vast majority of cases, this should be fine, but for the sake of completeness, these are the only fields that may be available there going forward - other fields that may have existed before may no longer be set:Other changes
SENTRY_RELEASEfromenv(#16201)http.serverspans with 404 status by default (#16205)removeFromDom()from throwing (#16030)Bundle size 📦
Important Changes
wrapMcpServerWithSentryfrom server packages (#16127)Exports the wrapMcpServerWithSentry which is our MCP server instrumentation from all the server packages.
Adds a best effort mechanism to associate handler spans for
resource,toolandpromptwith the incoming message requests instead of the outgoing SSE response.Other Changes
aiESM patching (#16152)module.register(#16125)unstable_sentryVitePluginOptionscorrectly (#16156)Work in this release was contributed by @ AntoineDuComptoirDesPharmacies. Thank you for your contribution!
Bundle size 📦
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
Podsumowanie od Sourcery
Prace porządkowe:
Original summary in English
Summary by Sourcery
Chores: