[Snyk] Upgrade @sentry/browser from 9.9.0 to 9.10.0 #341
Conversation
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
Snyk has created this PR to upgrade @sentry/browser from 9.9.0 to 9.10.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
Current Aviator status
This PR was merged manually (without Aviator). Merging manually can negatively impact the performance of the queue. Consider using Aviator next time.
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.
|
|
Aviator Changeset actions:
|
|
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 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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) |
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files
|
Przewodnik Recenzenta od SourceryTo żądanie pull aktualizuje pakiet Diagram sekwencji wysyłania wiadomości logu do SentrysequenceDiagram
participant App
participant Sentry
participant Sentry Server
App->>Sentry: Sentry.logger.info("Log message", { userId: 123 })
activate Sentry
Sentry->>Sentry Server: Capture log message with context
activate Sentry Server
Sentry Server-->>Sentry: Ack
deactivate Sentry Server
deactivate Sentry
Diagram sekwencji diagnozowania łączności SDKsequenceDiagram
participant App
participant Sentry
participant Sentry Server
App->>Sentry: Sentry.diagnoseSdkConnectivity()
activate Sentry
Sentry->>Sentry Server: Check connectivity
activate Sentry Server
Sentry Server-->>Sentry: Connectivity status
deactivate Sentry Server
Sentry-->>App: Result (e.g., 'sentry-unreachable')
deactivate Sentry
Zaktualizowany diagram klas dla loggera SentryclassDiagram
class Sentry {
+static logger: Logger
+static init(options: SentryOptions): void
+static diagnoseSdkConnectivity(): Promise<object>
}
class Logger {
+trace(message: string, ...args: any[]): void
+debug(message: string, ...args: any[]): void
+info(message: string, ...args: any[]): void
+warn(message: string, ...args: any[]): void
+error(message: string, ...args: any[]): void
+fatal(message: string, ...args: any[]): void
+fmt(template: string, ...args: any[]): string
}
Sentry -- Logger: has a
note for Logger "The Logger class now supports structured logging and dedicated methods for different log levels."
Zmiany na Poziomie Plików
Porady i poleceniaInterakcja z Sourcery
Dostosowywanie Twojego DoświadczeniaUzyskaj dostęp do swojego panelu, aby:
Uzyskiwanie Pomocy
Original review guide in EnglishReviewer's Guide by SourceryThis pull request upgrades the Sequence diagram for sending a log message to SentrysequenceDiagram
participant App
participant Sentry
participant Sentry Server
App->>Sentry: Sentry.logger.info("Log message", { userId: 123 })
activate Sentry
Sentry->>Sentry Server: Capture log message with context
activate Sentry Server
Sentry Server-->>Sentry: Ack
deactivate Sentry Server
deactivate Sentry
Sequence diagram for diagnosing SDK connectivitysequenceDiagram
participant App
participant Sentry
participant Sentry Server
App->>Sentry: Sentry.diagnoseSdkConnectivity()
activate Sentry
Sentry->>Sentry Server: Check connectivity
activate Sentry Server
Sentry Server-->>Sentry: Connectivity status
deactivate Sentry Server
Sentry-->>App: Result (e.g., 'sentry-unreachable')
deactivate Sentry
Updated class diagram for Sentry loggerclassDiagram
class Sentry {
+static logger: Logger
+static init(options: SentryOptions): void
+static diagnoseSdkConnectivity(): Promise<object>
}
class Logger {
+trace(message: string, ...args: any[]): void
+debug(message: string, ...args: any[]): void
+info(message: string, ...args: any[]): void
+warn(message: string, ...args: any[]): void
+error(message: string, ...args: any[]): void
+fatal(message: string, ...args: any[]): void
+fmt(template: string, ...args: any[]): string
}
Sentry -- Logger: has a
note for Logger "The Logger class now supports structured logging and dedicated methods for different log levels."
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
Skipping bot pull request creation because the queue is empty and this pull request is up to date with |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pominęliśmy przeglądanie tego żądaniaPull Request. Wygląda na to, że zostało ono utworzone przez bota (w tytule znaleziono '[Snyk]'). Zakładamy, że wie, co robi!
Original comment in English
We have skipped reviewing this pull request. It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
|
|
Here's the code health analysis summary for commits Analysis Summary
|
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
|
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.
Sweep Summary
Adds user registration functionality with email uniqueness validation and password encoding to the HulajDusza service.
UserRegistrationDtowith validation annotations for email, password, and name fields.isEmailInUsemethod toUserServiceto check if an email is already registered.registerUsermethod inUserServiceImplthat creates a new user with encoded password./api/users/registerendpoint inUserControllerthat handles user registration requests and returns appropriate HTTP responses.Ask Sweep AI questions about this PR
Snyk has created this PR to upgrade @sentry/browser from 9.9.0 to 9.10.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 1 version ahead of your current version.
The recommended version was released 22 days ago.
Release notes
Package name: @sentry/browser
-
9.10.0 - 2025-03-27
-
- feat(node): Add logging public APIs to Node SDKs (#15764)
- feat(core): Add support for
- feat(core): Add support for parameterizing logs (#15812)
- fix: Remove critical log severity level (#15824)
Sentry.init({
const { info, warn } = Sentry.logger;
-
-
- feat: Stop using
- feat(node): Only add span listeners for instrumentation when used (#15802)
- ref: Avoid
- ref: Avoid using
- ref: Stop using
- ref(core): Avoid using
- ref(node): Avoid
- ref(opentelemetry): Avoid sampling work for non-root spans (#15820)
- chore(deps): Bump
- deps: Bump bundler plugins to
- feat: Always truncate stored breadcrumb messages to 2kb (#15819)
- feat(nextjs): Disable server webpack-handling for static builds (#15751)
- fix(nuxt): Don't override Nuxt options if undefined (#15795)
Path
Size
@ sentry/browser
23.08 KB
@ sentry/browser - with treeshaking flags
22.88 KB
@ sentry/browser (incl. Tracing)
36.49 KB
@ sentry/browser (incl. Tracing, Replay)
73.65 KB
@ sentry/browser (incl. Tracing, Replay) - with treeshaking flags
67 KB
@ sentry/browser (incl. Tracing, Replay with Canvas)
78.3 KB
@ sentry/browser (incl. Tracing, Replay, Feedback)
90.87 KB
@ sentry/browser (incl. Feedback)
40.21 KB
@ sentry/browser (incl. sendFeedback)
27.71 KB
@ sentry/browser (incl. FeedbackAsync)
32.5 KB
@ sentry/react
24.86 KB
@ sentry/react (incl. Tracing)
38.39 KB
@ sentry/vue
27.3 KB
@ sentry/vue (incl. Tracing)
38.18 KB
@ sentry/svelte
23.12 KB
CDN Bundle
24.33 KB
CDN Bundle (incl. Tracing)
36.51 KB
CDN Bundle (incl. Tracing, Replay)
71.53 KB
CDN Bundle (incl. Tracing, Replay, Feedback)
76.71 KB
CDN Bundle - uncompressed
70.93 KB
CDN Bundle (incl. Tracing) - uncompressed
108.11 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed
219.4 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed
231.97 KB
@ sentry/nextjs (client)
39.68 KB
@ sentry/sveltekit (client)
36.92 KB
@ sentry/node
142.91 KB
@ sentry/node - without tracing
96.12 KB
@ sentry/aws-serverless
120.46 KB
-
9.9.0 - 2025-03-24
-
-
-
Sentry.init({
- feat(browser): Attach host as part of error message to "Failed to fetch" errors (#15729)
- feat(core): Add
- feat(core): Optimize
- feat(node): Add fastify
- fix(nuxt): Delete no longer needed Nitro 'close' hook (#15790)
- perf(nestjs): Remove usage of
- ref: Avoid some usage of
- ref: Remove some usages of
- ref(nextjs): Fix Next.js vercel-edge runtime package information (#15789)
Path
Size
@ sentry/browser
23.21 KB
@ sentry/browser - with treeshaking flags
23.01 KB
@ sentry/browser (incl. Tracing)
36.62 KB
@ sentry/browser (incl. Tracing, Replay)
73.79 KB
@ sentry/browser (incl. Tracing, Replay) - with treeshaking flags
67.12 KB
@ sentry/browser (incl. Tracing, Replay with Canvas)
78.42 KB
@ sentry/browser (incl. Tracing, Replay, Feedback)
91 KB
@ sentry/browser (incl. Feedback)
40.34 KB
@ sentry/browser (incl. sendFeedback)
27.85 KB
@ sentry/browser (incl. FeedbackAsync)
32.63 KB
@ sentry/react
25 KB
@ sentry/react (incl. Tracing)
38.52 KB
@ sentry/vue
27.44 KB
@ sentry/vue (incl. Tracing)
38.3 KB
@ sentry/svelte
23.25 KB
CDN Bundle
24.43 KB
CDN Bundle (incl. Tracing)
36.63 KB
CDN Bundle (incl. Tracing, Replay)
71.62 KB
CDN Bundle (incl. Tracing, Replay, Feedback)
76.83 KB
CDN Bundle - uncompressed
71.39 KB
CDN Bundle (incl. Tracing) - uncompressed
108.59 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed
219.84 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed
232.41 KB
@ sentry/nextjs (client)
39.81 KB
@ sentry/sveltekit (client)
37.03 KB
@ sentry/node
142.61 KB
@ sentry/node - without tracing
96 KB
@ sentry/aws-serverless
120.36 KB
from @sentry/browser GitHub release notesImportant Changes
feat: Add support for logs
beforeSendLog(#15814)All JavaScript SDKs other than
@ sentry/cloudflareand@ sentry/denonow support sending logs via dedicated methods as part of Sentry's upcoming logging product.Logging is gated by an experimental option,
_experiments.enableLogs.dsn: 'PUBLIC_DSN',
//
enableLogsmust be set to true to use the logging features_experiments: { enableLogs: true },
});
const { trace, debug, info, warn, error, fatal, fmt } = Sentry.logger;
trace('Starting database connection', { database: 'users' });
debug('Cache miss for user', { userId: 123 });
error('Failed to process payment', { orderId: 'order_123', amount: 99.99 });
fatal('Database connection pool exhausted', { database: 'users', activeConnections: 100 });
// Structured logging via the
fmthelper function. When you usefmt, the string template and parameters are sent separately so they can be queried independently in Sentry.info(fmt(
Updated profile for user <span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">userId</span><span class="pl-kos">}</span></span>));warn(fmt(
Rate limit approaching for endpoint <span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">endpoint</span><span class="pl-kos">}</span></span>. Requests: <span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">requests</span><span class="pl-kos">}</span></span>, Limit: <span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">limit</span><span class="pl-kos">}</span></span>));With server-side SDKs like
@ sentry/node,@ sentry/bunor server-side of@ sentry/nextjsor@ sentry/sveltekit, you can do structured logging without needing thefmthelper function.info('User %s logged in successfully', [123]);
warn('Failed to load user %s data', [123], { errorCode: 404 });
To filter logs, or update them before they are sent to Sentry, you can use the
_experiments.beforeSendLogoption.feat(browser): Add
diagnoseSdkConnectivity()function to programmatically detect possible connectivity issues (#15821)The
diagnoseSdkConnectivity()function can be used to programmatically detect possible connectivity issues with the Sentry SDK.The result will be an object with the following properties:
"no-client-active": There was no active client when the function was called. This possibly means that the SDK was not initialized yet."sentry-unreachable": The Sentry SaaS servers were not reachable. This likely means that there is an ad blocker active on the page or that there are other connection issues.undefined: The SDK is working as expected.SDK Tracing Performance Improvements for Node SDKs
dropUndefinedKeys(#15796)dropUndefinedKeysforspanToJSONcalls (#15792)SentryErrorfor PromiseBuffer control flow (#15822)dropUndefinedKeysin SpanExporter (#15794)SentryErrorfor event processing control flow (#15823)dropUndefinedKeysin Node SDK init (#15797)We've been hard at work making performance improvements to the Sentry Node SDKs (
@ sentry/node,@ sentry/aws-serverless,@ sentry/nestjs, etc.). We've seen that upgrading from9.7.0to9.10.0leads to 30-40% improvement in request latency for HTTP web-server applications that use tracing with high sample rates. Non web-server applications and non-tracing applications will see smaller improvements.Other Changes
rrwebto2.35.0(#15825)3.2.3(#15829)Bundle size 📦
Important Changes
feat(nextjs): Support
instrumentation-client.ts(#15705)Next.js recently added a feature to support client-side (browser) instrumentation via the
experimental.clientInstrumentationHookflag and theinstrumentation-client.tsfile.To be forwards compatible, the Sentry Next.js SDK will now pick up
instrumentation-client.tsfiles even on older Next.js versions and add them to your client bundles.It is suggested that you either rename your
sentry.client.config.tsfile toinstrumentation-client.ts, or if you already happen to have ainstrumentation-client.tsfile move the contents ofsentry.client.config.tstoinstrumentation-client.ts.feat(browser): Add
previous_tracespan links (#15569)The
@ sentry/browserSDK and SDKs based on@ sentry/browsernow emits a link from the first root span of a newly started trace to the root span of a previously started trace. You can control this feature via an option inbrowserTracingIntegration():feat(browser): Add
logger.Xmethods to browser SDK (#15763)For Sentry's upcoming logging product, the SDK now supports sending logs via dedicated
dsn: 'your-dsn-here',
_experiments: {
enableLogs: true, // This is required to use the logging features
},
});
Sentry.logger.info('This is a trace message', { userId: 123 });
// See PR for better documentation
Please note that the logs product is still in early access. See the link above for more information.
Other Changes
parseStringToURLmethod (#15768)dropUndefinedKeys(#15760)shouldHandleError(#15771)addNonEnumerableProperty(#15766)dropUndefinedKeys()(#15757)dropUndefinedKeys()(#15781)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 wygenerowane przez Sourcery
Aktualizacja @sentry/browser z wersji 9.9.0 do 9.10.0, zawierająca nowe funkcje i poprawki wydajności.
Nowe funkcje:
Ulepszenia:
Original summary in English
Summary by Sourcery
Upgrade @sentry/browser from version 9.9.0 to 9.10.0, incorporating new features and performance improvements
New Features:
Enhancements: