fix(deps): update dependency @sentry/browser to v9 #2656
+37
−37
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
4 times, most recently
from
1eb1592 to
70a5ebe
Compare
renovate
bot
force-pushed
the
renovate/major-sentry-javascript-monorepo
branch
from
70a5ebe to
13c9359
Compare
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.
This PR contains the following updates:
8.55.0->9.19.0Release Notes
getsentry/sentry-javascript (@sentry/browser)
v9.19.0opentelemetry-instrumentation-remix(#16145)cancelledreason (#16277)@fastify/otelfork to direct url to allow installing without git (#16287)Work in this release was contributed by @sidx1024. Thank you for your contribution!
Bundle size 📦
v9.18.0Compare Source
Important changes
We now also publish profiling binaries for Node 24.
Other changes
import-in-the-middleto1.13.1(#16260)consoleLoggingIntegrationfrom vercel edge sdk (#16228)@fastify/oteldependency with pinned Otel v1 deps (#16256)Bundle size 📦
v9.17.0Compare Source
@fastify/otel(#15542)Bundle size 📦
v9.16.1Compare Source
v9.16.0Compare Source
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 📦
v9.15.0Compare Source
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 📦
v9.14.0Compare Source
Important Changes
This PR adds Supabase integration to
@sentry/core, allowing automatic instrumentation of Supabase client operations (database queries and authentication) for performance monitoring and error tracking.SentryGlobalFilter(#16066)This PR adds better RPC exception handling to
@sentry/nestjs, preventing application crashes while still capturing errors and warning users when a dedicated filter is needed. The implementation gracefully handles the 'rpc' context type inSentryGlobalFilterto improve reliability in hybrid applications.This PR adds trace propagation to
@sentry/react-routerby providing utilities to inject trace meta tags into HTML headers and offering a pre-built Sentry-instrumented request handler, improving distributed tracing capabilities across page loads.Other Changes
Bundle size 📦
v9.13.0Compare Source
Important Changes
feat(node): Add support for winston logger (#15983)
Sentry is adding support for structured logging. In this release we've added support for sending logs to Sentry via the winston logger to the Sentry Node SDK (and SDKs that use the Node SDK under the hood like
@sentry/nestjs). The Logging APIs in the Sentry SDK are still experimental and subject to change.feat(core): Add
wrapMcpServerWithSentryto instrument MCP servers from@modelcontextprotocol/sdk(#16032)The Sentry SDK now supports instrumenting MCP servers from the
@modelcontextprotocol/sdkpackage. Compatible with versions^1.9.0of the@modelcontextprotocol/sdkpackage.feat(core): Move console integration into core and add to cloudflare/vercel-edge (#16024)
Console instrumentation has been added to
@sentry/cloudflareand@sentry/nextjsEdge Runtime and is enabled by default. Now calls to the console object will be captured as breadcrumbs for those SDKs.feat(bun): Support new
Bun.serveAPIs (#16035)Bun
1.2.6and above have a newBun.serveAPI, which the Bun SDK now supports. The SDK instruments the new routes object that can be used to define routes for the server.Thanks to @Jarred-Sumner for helping us get this supported!
Other Changes
browserTracingIntegration(#16042)beforeSendLogafter we process log (#16019)unstable_sentryVitePluginOptionsto cli instance (#16033)v9.12.0Compare Source
v9.11.0Compare Source
http.redirect_countattribute tobrowser.redirectspan (#15943)consoleLoggingIntegrationfor logs (#15955)turbopackas tag (#15928)sentryHandleRequest(#15787)moduleinstead ofrequirefor CJS check (#15927)ErrorBoundarywrapper (#15930)sentry.previous_tracespan attribute (#15957)Bundle size 📦
v9.10.1Compare Source
3.2.4(#15909)v9.10.0Compare Source
Important 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.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.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)v9.9.0Compare Source
Important Changes
feat(nextjs): Support
instrumentation-client.ts(#15705)Next.js recently added a feature to support client-side (browser) instrumentation via a
instrumentation-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 methods.
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)v9.8.0Compare Source
res.endbefore passing to Proxy (#15776)eventFiltersintegration (#15752)v9.7.0Compare Source
captureLogmethod (#15717)sentryHandleError(#15726)fatallevel for unhandled rejections instrictmode (#15720)v9.6.1Compare Source
v9.6.0Compare Source
Important Changes
feat(tanstackstart): Add
@sentry/tanstackstart-reactpackage and make@sentry/tanstackstartpackage a utility package (#15629)Since TanStack Start is supposed to be a generic framework that supports libraries like React and Solid, the
@sentry/tanstackstartSDK package was renamed to@sentry/tanstackstart-reactto reflect that the SDK is specifically intended to be used for React TanStack Start applications.Note that the TanStack Start SDK is still in alpha status and m
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.