octochangelog-webapp
octochangelog-webapp copied to clipboard
Update dependency @sentry/nextjs to v9
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| @sentry/nextjs (source) | 8.55.0 -> 9.14.0 |
Release Notes
getsentry/sentry-javascript (@sentry/nextjs)
v9.14.0
Important Changes
- feat: Add Supabase Integration (#15719)
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.
- feat(nestjs): Gracefully handle RPC scenarios in
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 in SentryGlobalFilter to improve reliability in hybrid applications.
- feat(react-router): Trace propagation (#16070)
This PR adds trace propagation to @sentry/react-router by 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
- feat(deps): Bump @prisma/instrumentation from 6.5.0 to 6.6.0 (#16102)
- feat(nextjs): Improve server component data (#15996)
- feat(nuxt): Log when adding HTML trace meta tags (#16044)
- fix(node): Make body capturing more robust (#16105)
- ref(node): Log when incoming request bodies are being captured (#16104)
Bundle size 📦
| Path | Size |
|---|---|
| @sentry/browser | 23.28 KB |
| @sentry/browser - with treeshaking flags | 23.12 KB |
| @sentry/browser (incl. Tracing) | 36.99 KB |
| @sentry/browser (incl. Tracing, Replay) | 74.17 KB |
| @sentry/browser (incl. Tracing, Replay) - with treeshaking flags | 67.55 KB |
| @sentry/browser (incl. Tracing, Replay with Canvas) | 78.83 KB |
| @sentry/browser (incl. Tracing, Replay, Feedback) | 90.65 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.91 KB |
| @sentry/vue | 27.51 KB |
| @sentry/vue (incl. Tracing) | 38.71 KB |
| @sentry/svelte | 23.32 KB |
| CDN Bundle | 24.5 KB |
| CDN Bundle (incl. Tracing) | 36.98 KB |
| CDN Bundle (incl. Tracing, Replay) | 72 KB |
| CDN Bundle (incl. Tracing, Replay, Feedback) | 77.16 KB |
| CDN Bundle - uncompressed | 71.49 KB |
| CDN Bundle (incl. Tracing) - uncompressed | 109.34 KB |
| CDN Bundle (incl. Tracing, Replay) - uncompressed | 220.63 KB |
| CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed | 233.16 KB |
| @sentry/nextjs (client) | 40.54 KB |
| @sentry/sveltekit (client) | 37.44 KB |
| @sentry/node | 143.37 KB |
| @sentry/node - without tracing | 96.51 KB |
| @sentry/aws-serverless | 120.83 KB |
v9.13.0
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.const winston = require('winston'); const Transport = require('winston-transport'); const transport = Sentry.createSentryWinstonTransport(Transport); const logger = winston.createLogger({ transports: [transport], }); -
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.import { McpServer } from '@​modelcontextprotocol/sdk/server/mcp.js'; // Create an MCP server const server = new McpServer({ name: 'Demo', version: '1.0.0', }); // Use the instrumented server in your application const instrumentedServer = Sentry.wrapMcpServerWithSentry(server); -
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
- feat(browser): Warn on duplicate
browserTracingIntegration(#16042) - feat(core): Allow delayed sending with offline transport (#15937)
- feat(deps): Bump @sentry/webpack-plugin from 3.2.4 to 3.3.1 (#16057)
- feat(vue): Apply stateTransformer to attachments in Pinia Plugin (#16034)
- fix(core): Run
beforeSendLogafter we process log (#16019) - fix(nextjs): Don't show turbopack warning for newer Next.js canaries (#16065)
- fix(nextjs): Include patch version 0 for min supported 15.3.0 (#16026)
- fix(node): Ensure late init works with all integrations (#16016)
- fix(react-router): Pass
unstable_sentryVitePluginOptionsto cli instance (#16033) - fix(serverless-aws): Overwrite root span name with GraphQL if set (#16010)
v9.12.0
v9.11.0
- feat(browser): Add
http.redirect_countattribute tobrowser.redirectspan (#15943) - feat(core): Add
consoleLoggingIntegrationfor logs (#15955) - feat(core): Don't truncate error messages (#15818)
- feat(nextjs): Add release injection in Turbopack (#15958)
- feat(nextjs): Record
turbopackas tag (#15928) - feat(nuxt): Base decision on source maps upload only on Nuxt source map settings (#15859)
- feat(react-router): Add
sentryHandleRequest(#15787) - fix(node): Use
moduleinstead ofrequirefor CJS check (#15927) - fix(remix): Remove mentions of deprecated
ErrorBoundarywrapper (#15930) - ref(browser): Temporarily add
sentry.previous_tracespan attribute (#15957) - ref(browser/core): Move all log flushing logic into clients (#15831)
- ref(core): Improve URL parsing utilities (#15882)
Bundle size 📦
| Path | Size |
|---|---|
| @sentry/browser | 23.2 KB |
| @sentry/browser - with treeshaking flags | 23.02 KB |
| @sentry/browser (incl. Tracing) | 36.83 KB |
| @sentry/browser (incl. Tracing, Replay) | 73.99 KB |
| @sentry/browser (incl. Tracing, Replay) - with treeshaking flags | 67.39 KB |
| @sentry/browser (incl. Tracing, Replay with Canvas) | 78.66 KB |
| @sentry/browser (incl. Tracing, Replay, Feedback) | 91.22 KB |
| @sentry/browser (incl. Feedback) | 40.33 KB |
| @sentry/browser (incl. sendFeedback) | 27.83 KB |
| @sentry/browser (incl. FeedbackAsync) | 32.63 KB |
| @sentry/react | 25 KB |
| @sentry/react (incl. Tracing) | 38.75 KB |
| @sentry/vue | 27.41 KB |
| @sentry/vue (incl. Tracing) | 38.55 KB |
| @sentry/svelte | 23.23 KB |
| CDN Bundle | 24.44 KB |
| CDN Bundle (incl. Tracing) | 36.85 KB |
| CDN Bundle (incl. Tracing, Replay) | 71.87 KB |
| CDN Bundle (incl. Tracing, Replay, Feedback) | 77.07 KB |
| CDN Bundle - uncompressed | 71.24 KB |
| CDN Bundle (incl. Tracing) - uncompressed | 108.94 KB |
| CDN Bundle (incl. Tracing, Replay) - uncompressed | 220.23 KB |
| CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed | 232.8 KB |
| @sentry/nextjs (client) | 40.06 KB |
| @sentry/sveltekit (client) | 37.26 KB |
| @sentry/node | 142.88 KB |
| @sentry/node - without tracing | 96.08 KB |
| @sentry/aws-serverless | 120.43 KB |
v9.10.1
- fix: Correct @sentry-internal/feedback docs to match the code (#15874)
- deps: Bump bundler plugins to version
3.2.4(#15909)
v9.10.0
Important Changes
-
feat: Add support for logs
- feat(node): Add logging public APIs to Node SDKs (#15764)
- feat(core): Add support for
beforeSendLog(#15814) - feat(core): Add support for parameterizing logs (#15812)
- fix: Remove critical log severity level (#15824)
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.Sentry.init({ dsn: 'PUBLIC_DSN', // `enableLogs` must 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 `fmt` helper function. When you use `fmt`, the string template and parameters are sent separately so they can be queried independently in Sentry. info(fmt(`Updated profile for user ${userId}`)); warn(fmt(`Rate limit approaching for endpoint ${endpoint}. Requests: ${requests}, Limit: ${limit}`));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.const { info, warn } = Sentry.logger; 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.const result = await Sentry.diagnoseSdkConnectivity();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
- feat: Stop using
dropUndefinedKeys(#15796) - feat(node): Only add span listeners for instrumentation when used (#15802)
- ref: Avoid
dropUndefinedKeysforspanToJSONcalls (#15792) - ref: Avoid using
SentryErrorfor PromiseBuffer control flow (#15822) - ref: Stop using
dropUndefinedKeysin SpanExporter (#15794) - ref(core): Avoid using
SentryErrorfor event processing control flow (#15823) - ref(node): Avoid
dropUndefinedKeysin Node SDK init (#15797) - ref(opentelemetry): Avoid sampling work for non-root spans (#15820)
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. - feat: Stop using
Other Changes
- chore(deps): Bump
rrwebto2.35.0(#15825) - deps: Bump bundler plugins to
3.2.3(#15829) - 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)
v9.9.0
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 yoursentry.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():Sentry.init({ dsn: 'your-dsn-here' integrations: [ Sentry.browserTracingIntegration({ // Available settings: // - 'in-memory' (default): Stores previous trace information in memory // - 'session-storage': Stores previous trace information in the browser's `sessionStorage` // - 'off': Disable storing and sending previous trace information linkPreviousTrace: 'in-memory', }), ], }); -
feat(browser): Add
logger.Xmethods to browser SDK (#15763)For Sentry's upcoming logging product, the SDK now supports sending logs via dedicated methods.
Sentry.init({ 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 documentationPlease note that the logs product is still in early access. See the link above for more information.
Other Changes
- feat(browser): Attach host as part of error message to "Failed to fetch" errors (#15729)
- feat(core): Add
parseStringToURLmethod (#15768) - feat(core): Optimize
dropUndefinedKeys(#15760) - feat(node): Add fastify
shouldHandleError(#15771) - fix(nuxt): Delete no longer needed Nitro 'close' hook (#15790)
- perf(nestjs): Remove usage of
addNonEnumerableProperty(#15766) - ref: Avoid some usage of
dropUndefinedKeys()(#15757) - ref: Remove some usages of
dropUndefinedKeys()(#15781) - ref(nextjs): Fix Next.js vercel-edge runtime package information (#15789)
v9.8.0
- feat(node): Implement new continuous profiling API spec (#15635)
- feat(profiling): Add platform to chunk envelope (#15758)
- feat(react): Export captureReactException method (#15746)
- fix(node): Check for
res.endbefore passing to Proxy (#15776) - perf(core): Add short-circuits to
eventFiltersintegration (#15752) - perf(node): Short circuit flushing on Vercel only for Vercel (#15734)
v9.7.0
- feat(core): Add
captureLogmethod (#15717) - feat(remix/cloudflare): Export
sentryHandleError(#15726) - fix(node): Always flush on Vercel before Lambda freeze (#15602)
- fix(node): Ensure incoming traces are propagated without HttpInstrumentation (#15732)
- fix(node): Use
fatallevel for unhandled rejections instrictmode (#15720) - fix(nuxt): Delete Nuxt server template injection (#15749)
v9.6.1
- feat(deps): bump @prisma/instrumentation from 6.4.1 to 6.5.0 (#15714)
- feat(deps): bump @sentry/cli from 2.42.2 to 2.42.3 (#15711)
- fix(nextjs): Re-patch router if it is overridden by Next.js (#15721)
- fix(nuxt): Add Nitro Rollup plugin to inject Sentry server config (#15710)
- chore(deps): Bump rollup to 4.35.0 (#15651)
v9.6.0
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 may be subject to breaking changes in non-major package updates.
Other Changes
- feat(astro): Accept all vite-plugin options (#15638)
- feat(deps): bump @sentry/webpack-plugin from 3.2.1 to 3.2.2 (#15627)
- feat(tanstackstart): Refine initial API (#15574)
- fix(core): Ensure
fillonly patches functions (#15632) - fix(nextjs): Consider
pageExtensionswhen looking for instrumentation file (#15701) - fix(remix): Null-check
options(#15610) - fix(sveltekit): Correctly parse angle bracket type assertions for auto instrumentation (#15578)
- fix(sveltekit): Guard process variable (#15605)
Work in this release was contributed by @angelikatyborska and @nwalters512. Thank you for your contributions!
v9.5.0
Important Changes
We found some issues with the new feedback screenshot annotation where screenshots are not being generated properly. Due to this issue, we are reverting the feature.
Other Changes
- Add cloudflare adapter detection and path generation (#15603)
- deps(nextjs): Bump rollup to
4.34.9(#15589) - feat(bun): Automatically add performance integrations (#15586)
- feat(replay): Bump rrweb to 2.34.0 (#15580)
- fix(browser): Call original function on early return from patched history API (#15576)
- fix(nestjs): Copy metadata in custom decorators (#15598)
- fix(react-router): Fix config type import (#15583)
- fix(remix): Use correct types export for
@sentry/remix/cloudflare(#15599) - fix(vue): Attach Pinia state only once per event (#15588)
Work in this release was contributed by @msurdi-a8c, @namoscato, and @rileyg98. Thank you for your contributions!
v9.4.0
- feat(core): Add types for logs protocol and envelope (#15530)
- feat(deps): Bump
@sentry/clifrom 2.41.1 to 2.42.2 (#15510) - feat(deps): Bump
@sentry/webpack-pluginfrom 3.1.2 to 3.2.1 (#15512) - feat(feedback) Allowing annotation via highlighting & masking (#15484)
- feat(nextjs): Add
use clientdirective to client SDK entrypoints (#15575) - feat(nextjs): Allow silencing of instrumentation warning (#15555)
- feat(sveltekit): Ensure
AsyncLocalStorageasync context strategy is used in Cloudflare Pages (#15557) - fix(cloudflare): Make
@cloudflare/workers-typesan optional peer dependency (#15554) - fix(core): Don't reverse values in event filters (#15584)
- fix(core): Handle normalization of null prototypes correctly (#15556)
- fix(nextjs): Only warn on missing
onRequestErrorin version 15 (#15553) - fix(node): Allow for
undefinedtransport to be passed in (#15560) - fix(wasm): Fix wasm integration stacktrace parsing for filename (#15572)
- perf(node): Store normalized request for processing (#15570)
v9.3.0
Important Changes
With this release we're publishing two new SDKs in experimental alpha stage:
- feat(tanstackstart): Add TanStack Start SDK (#15523)
For details please refer to the README
- feat(react-router): Add React Router SDK (#15524)
For details please refer to the README
- feat(remix): Add support for Hydrogen (#15450)
This PR adds support for Shopify Hydrogen applications running on MiniOxygen runtime.
Other Changes
- feat(core): Add
forceTransactionto trpc middleware options (#15519) - feat(core): Default filter unactionable error (#15527)
- feat(core): Rename
inboundFiltersIntegrationtoeventFiltersIntegration(#15434) - feat(deps): bump @prisma/instrumentation from 6.2.1 to 6.4.1 (#15480)
- feat(react-router): Add build-time config (#15406)
- feat(replay): Bump rrweb to 2.33.0 (#15514)
- fix(core): Fix
allowUrlsanddenyUrlsfor linked and aggregate exceptions (#15521) - fix(nextjs): Don't capture devmode server-action redirect errors (#15485)
- fix(nextjs): warn about missing onRequestError handler #15488)
- fix(nextjs): Prevent wrong culprit from showing up for clientside error events #15475)
- fix(nuxt): Ignore 300-400 status codes on app errors in Nuxt (#15473)
- fix(react): Add support for cross-usage of React Router instrumentations (#15283)
- fix(sveltekit): Guard
processcheck when flushing events (#15516)
Work in this release was contributed by @GerryWilko and @leoambio. Thank you for your contributions!
v9.2.0
Important Changes
- feat(node): Support Express v5 (#15380)
This release adds full tracing support for Express v5, and improves tracing support for Nest.js 11 (which uses Express v5) in the Nest.js SDK.
- feat(sveltekit): Add Support for Cloudflare (#14672)
This release adds support for deploying SvelteKit applications to Cloudflare Pages. A docs update with updated instructions will follow shortly. Until then, you can give this a try by setting up the SvelteKit SDK as usual and then following the instructions outlined in the PR.
Thank you @SG60 for contributing this feature!
Other Changes
- feat(core): Add
addLink(s)to Sentry span (#15452) - feat(core): Add links to span options (#15453)
- feat(deps): Bump @sentry/webpack-plugin from 2.22.7 to 3.1.2 (#15328)
- feat(feedback): Disable Feedback submit & cancel buttons while submitting (#15408)
- feat(nextjs): Add experimental flag to not strip origin information from different origin stack frames (#15418)
- feat(nuxt): Add
enableNitroErrorHandlerto server options (#15444) - feat(opentelemetry): Add
addLink(s)to span (#15387) - feat(opentelemetry): Add
linksto span options (#15403) - feat(replay): Expose rrweb recordCrossOriginIframes under _experiments (#14916)
- fix(browser): Ensure that
performance.measurespans have a positive duration (#15415) - fix(bun): Includes correct sdk metadata (#15459)
- fix(core): Add Google
gmoerror to Inbound Filters (#15432) - fix(core): Ensure
http.clientspan descriptions don't contain query params or fragments (#15404) - fix(core): Filter out unactionable Facebook Mobile browser error (#15430)
- fix(nestjs): Pin dependency on
@opentelemetry/instrumentation(#15419) - fix(nuxt): Only use filename with file extension from command (#15445)
- fix(nuxt): Use
SentryNuxtServerOptionstype for server init (#15441) - fix(sveltekit): Avoid loading vite config to determine source maps setting (#15440)
- ref(profiling-node): Bump chunk interval to 60s (#15361)
Work in this release was contributed by @6farer, @dgavranic and @SG60. Thank you for your contributions!
v9.1.0
- feat(browser): Add
graphqlClientIntegration(#13783) - feat(core): Allow for nested trpc context (#15379)
- feat(core): Create types and utilities for span links (#15375)
- feat(deps): bump @opentelemetry/instrumentation-pg from 0.50.0 to 0.51.0 (#15273)
- feat(node): Extract Sentry-specific node-fetch instrumentation (#15231)
- feat(vue): Support Pinia v3 (#15383)
- fix(sveltekit): Avoid request body double read errors (#15368)
- fix(sveltekit): Avoid top-level
viteimport (#15371)
Work in this release was contributed by @Zen-cronic and @filips-alpe. Thank you for your contribution!
v9.0.1
- ref(flags): rename unleash integration param (#15343)
v9.0.0
Version 9.0.0 marks a release of the Sentry JavaScript SDKs that contains breaking changes.
The goal of this release is to trim down on unused and potentially confusing APIs, prepare the SDKs for future framework versions to build deeper instrumentation, and remove old polyfills to reduce the packages' size.
How To Upgrade
Please carefully read through the migration guide in the Sentry docs on how to upgrade from version 8 to version 9. Make sure to select your specific platform/framework in the top left corner: https://docs.sentry.io/platforms/javascript/migration/v8-to-v9/
A comprehensive migration guide outlining all changes for all the frameworks can be found within the Sentry JavaScript SDK Repository: https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md
Breaking Changes
- doc(deno)!: Make Deno v2 the minimum supported version (#15085)
- feat!: Bump typescript to
~5.0.0(#14758) - feat!: Drop
nitro-utilspackage (#14998) - feat!: Only collect ip addresses with
sendDefaultPii: true(#15084) - feat!: Remove
autoSessionTrackingoption (#14802) - feat!: Remove
enableTracing(#15078) - feat!: Remove
getCurrentHub(),Hub, andgetCurrentHubShim()(#15122) - feat!: Remove
spanIdfrom propagation context (#14733) - feat!: Remove deprecated and unused code (#15077)
- feat!: Remove metrics API from the JS SDK (#14745)
- feat!: Require Node
>=18as minimum supported version (#14749) - feat(astro)!: Respect user-specified source map setting (#14941)
- feat(browser)!: Remove
captureUserFeedbackmethod (#14820) - feat(build)!: Drop pre-ES2020 polyfills (#14882)
- feat(core)!: Add
normalizedRequesttosamplingContext(#14902) - feat(core)!: Always use session from isolation scope (#14860)
- feat(core)!: Pass root spans to
beforeSendSpanand disallow returningnull(#14831) - feat(core)!: Remove
BAGGAGE_HEADER_NAMEexport (#14785) - feat(core)!: Remove
TransactionNamingSchemetype (#14865) - feat(core)!: Remove
addOpenTelemetryInstrumentationmethod (#14792) - feat(core)!: Remove
arrayifymethod (#14782) - feat(core)!: Remove
debugIntegrationandsessionTimingIntegration(#14747) - feat(core)!: Remove
flattenmethod (#14784) - feat(core)!: Remove
getDomElementmethod (#14797) - feat(core)!: Remove
makeFifoCachemethod (#14786) - feat(core)!: Remove
memoBuilderexport &WeakSetfallback (#14859) - feat(core)!: Remove
transactionContextfromsamplingContext(#14904) - feat(core)!: Remove
urlEncodemethod (#14783) - feat(core)!: Remove deprecated
Requesttype (#14858) - feat(core)!: Remove deprecated request data methods (#14896)
- feat(core)!: Remove standalone
Clientinterface & deprecateBaseClient(#14800) - feat(core)!: Remove validSeverityLevels export (#14765)
- feat(core)!: Stop accepting
eventas argument forrecordDroppedEvent(#14999) - feat(core)!: Stop setting user in
requestDataIntegration(#14898) - feat(core)!: Type sdkProcessingMetadata more strictly (#14855)
- feat(core)!: Update
hasTracingEnabledto consider empty trace config (#14857) - feat(core)!: Update
requestDataIntegrationhandling (#14806) - feat(deno)!: Remove deno prepack (#14829)
- feat(ember)!: Officially drop support for ember
<=3.x(#15032) - feat(nestjs)!: Move
nestIntegrationinto nest sdk and removesetupNestErrorHandler(#14751) - feat(nestjs)!: Remove
@WithSentrydecorator (#14762) - feat(nestjs)!: Remove
SentryService(#14759) - feat(nextjs)!: Don't rely on Next.js Build ID for release names (#14939)
- feat(nextjs)!: Remove
experimental_captureRequestError(#14607) - feat(nextjs)!: Respect user-provided source map generation settings (#14956)
- feat(node)!: Add support for Prisma v6 and drop v5 support (#15120)
- feat(node)!: Avoid http spans by default for custom OTEL setups (#14678)
- feat(node)!: Collect request sessions via HTTP instrumentation (#14658)
- feat(node)!: Remove
processThreadBreadcrumbIntegration(#14666) - feat(node)!: Remove fine grained
registerEsmLoaderHooks(#15002) - feat(opentelemetry)!: Exclusively pass root spans through sampling pipeline (#14951)
- feat(pinia)!: Include state of all stores in breadcrumb (#15312)
- feat(react)!: Raise minimum supported TanStack Router version to
1.63.0(#15030) - feat(react)!: Remove deprecated
getNumberOfUrlSegmentsmethod (#14744) - feat(react)!: Remove deprecated react router methods (#14743)
- feat(react)!: Update
ErrorBoundarycomponentStacktype (#14742) - feat(remix)!: Drop support for Remix v1 (#14988)
- feat(remix)!: Remove
autoInstrumentRemixoption (#15074) - feat(solidstart)!: Default to
--importsetup and addautoInjectServerSentry(#14862) - feat(solidstart)!: No longer export
sentrySolidStartVite(#15143) - feat(solidstart)!: Respect user-provided source map setting (#14979)
- feat(svelte)!: Disable component update tracking by default (#15265)
- feat(sveltekit)!: Drop support for SvelteKit @1.x (#15037)
- feat(sveltekit)!: Remove
fetchProxyScriptNonceoption (#15123) - feat(sveltekit)!: Respect user-provided source map generation settings (#14886)
- feat(utils)!: Remove
@sentry/utilspackage (#14830) - feat(vue)!: Remove configuring Vue tracing options anywhere else other than through the
vueIntegration'stracingOptionsoption (#14856) - feat(vue/nuxt)!: No longer create
"update"spans for component tracking by default (#14602) - fix(node)!: Fix name of
vercelAIIntegrationtoVercelAI(#15298) - fix(vue)!: Remove
logErrorfromvueIntegration(#14958) - ref!: Don't polyfill optional chaining and nullish coalescing (#14603)
- ref(core)!: Cleanup internal types, including
ReportDialogOptions(#14861) - ref(core)!: Mark exceptions from
captureConsoleIntegrationashandled: trueby default (#14734) - ref(core)!: Move
shutdownTimeoutoption type from core to node (#15217) - ref(core)!: Remove
Scopetype interface in favor of usingScopeclass (#14721) - ref(core)!: Remove backwards compatible SentryCarrier type (#14697)
Other Changes
- chore(browser): Export ipAddress helpers for use in other SDKs (#15079)
- deps(node): Bump
import-in-the-middleto1.12.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| octochangelog | Preview | Comment | Sep 2, 2025 6:44am |
Codecov Report
Attention: Patch coverage is 2.11268% with 139 lines in your changes missing coverage. Please review.
Project coverage is 6.23%. Comparing base (
0b1a8fd) to head (50e4c29). Report is 193 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #2768 +/- ##
========================================
+ Coverage 5.47% 6.23% +0.76%
========================================
Files 56 60 +4
Lines 2504 2551 +47
Branches 109 113 +4
========================================
+ Hits 137 159 +22
- Misses 2313 2354 +41
+ Partials 54 38 -16
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
- :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠️ Warning: custom changes will be lost.