fix(deps): update sentry-javascript monorepo to v10#36
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #36 +/- ##
=======================================
Coverage 51.00% 51.00%
=======================================
Files 51 51
Lines 896 896
Branches 202 202
=======================================
Hits 457 457
Misses 435 435
Partials 4 4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
9c19d24 to
277b72d
Compare
|
Edited/Blocked NotificationRenovate 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. |
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Not approving: CI failed (Build & Typecheck, Lint & Format, Unit Tests, Autofix code) and this is a major Sentry v10 bump that needs manual review. Renovate also failed to refresh pnpm-lock.yaml. RedStar071 is already assigned for human review.
Sent by Cursor Approval Agent: Pull Request Approver
2 participants
This PR contains the following updates:
^8.55.2→^10.58.0Release Notes
getsentry/sentry-javascript (@sentry/node)
v10.58.0Compare Source
Important Changes
feat(hono): Add support for the Deno runtime (#21450)
@sentry/hononow supports the Deno runtime via a new@sentry/hono/denoentry point.Install
@sentry/denoas a peer dependency and initialize Sentry through thesentry()middleware:feat(core): Extract objects as structured logs in
consoleLoggingIntegration(#21385)The
consoleLoggingIntegrationnow extracts structured log attributes when the first argument is a plain object.feat(react-router): Stabilize the instrumentation API (#21470)
React Router's instrumentation API is now stable — the
@experimentalmarkers have been removed fromcreateSentryServerInstrumentation,createSentryClientInstrumentation, and the related helpers and types.The manual server wrappers
wrapServerLoaderandwrapServerActionare now deprecated in favor of it. Exportinstrumentations = [Sentry.createSentryServerInstrumentation()]from yourentry.server.tsxto instrument all loaders and actions without wrapping them individually.Other Changes
useInstrumentationAPI(#21432)__sentry_wrapped__inherited fromFunction.prototype(#21506)safeJoinside-effect-free for DOM elements (#21356)moduleandtypesfields inpackage.json(#21449)okinstead ofinternal_error(#21521)defaultexports condition (#21472)Work in this release was contributed by @archievi, @AyaanFaisal21, @itosa-kazu, and @bkchr. Thank you for your contributions!
Internal Changes
22.7.5(#21527)SENTRY_BUILD_PRESERVE_MODULESenv check from rollup configs (#21487)Bundle size 📦
v10.57.0Compare Source
Important Changes
feat(angular): Add support for Angular 22 (#21330)
@sentry/angularnow officially supports Angular 22.ref(core): Deprecate
sendDefaultPiiin favor ofdataCollection(#21277)sendDefaultPiiis deprecated and will be removed in v11. The newdataCollectionoption lets you control each category of collected data.sendDefaultPii: truestill works and maps to enabling alldataCollectioncategories.dataCollection.userInfodefaults totruewhendataCollectionis provided, meaning auto-populateduser.*fields (e.g. IP address from a request) are collected by default.Data you set explicitly (like via
Sentry.setUser()) is always sent regardless.When
dataCollectionis not set at all, the legacysendDefaultPiibehavior applies (userInfo: falseby default) to preserve backward compatibility.Note that an empty
dataCollection: {}falls back to more permissive defaults thansendDefaultPii: false, so replicate the old behavior by opting out explicitly:Other Changes
dataCollection.frameContextLinesfor ContextLines integration (#21323)dataCollection.userInfototrue(#21348)dataCollection.httpBodiesto all valid body types (#21352)faviconetc) (#21365)safeDateNowcalls fornew Date()reads (#21351)pinoIntegrationon edge runtime (#21347)__SENTRY_SERVER_MODULES__lazily so Turbopack injection is honored (#21339)react.componentStackevent context (#21183)sentry._internal.replay_is_bufferingfor spans (#21297)Internal Changes
sendDefaultPiitodataCollectionoption (#21288)Work in this release was contributed by @zhongrenfei1-hub. Thank you for your contribution!
Bundle size 📦
v10.56.0Compare Source
Important Changes
feat(deno): Redis diagnostics channel based integration for Deno (#21087)
Adds Redis integration support for Deno, covering both
redisandioredisclients.Other Changes
@sentry/nodewas imported instead of@sentry/hono/node(#21240)consistentTraceSamplingis enabled (#21281)instrumentDurableObjectWithSentrybreaking Cloudflare Agents (#21101)WeakReffor Span-Scope circular references (#21242)InstrumentationNodeModuleFileto fix Bun--bytecodecrash (#21262)Internal Changes
hrTimeutilities from@opentelemetry/core(#21191)http.route(#21193)TraceStateimplementation (#21192)dataCollection(#21282)Bundle size 📦
v10.55.0Compare Source
Important Changes
feat(hono): Promote
@sentry/honoto stable and deprecatehonoIntegration(#21208)The
@sentry/honoSDK is now stable. See the Sentry Hono SDK docs to get started.docs(tanstackstart-react): Promote SDK status to beta (#21175)
This release promotes the
@sentry/tanstackstart-reactSDK to beta. For details on how to use it, check out theSentry TanStack Start SDK docs. Please reach out on
GitHub if you have any feedback or concerns.
feat(hono): Add
shouldHandleErroroption tosentry()middleware (#21205)The
sentry()middleware now accepts ashouldHandleErrorcallback to control which errors are captured and sent to Sentry. By default, 3xx/4xx HTTP errors are ignored and 5xx errors and plainErrorobjects are captured. Returntruefrom the callback to capture an error,falseto suppress it.test(tanstackstart-react): Move initialization to client entry point (#21161)
Change the recommended setup for the SDK to do
Sentry.init()in the client entry file to capture telemetry that is emitted ahead of page hydration.feat(tanstackstart-react): Add distributed tracing (#21144)
Server and client traces are now automatically connected, allowing you to see the full request lifecycle from server-side rendering through client-side hydration in a single trace.
feat(tanstackstart-react): Add server-side route parametrization (#21147)
Server transaction names are now parametrized automatically (e.g.,
GET /users/123becomesGET /users/$userId), improving transaction grouping in Sentry.feat(tanstackstart-react): Show readable server function names in traces (#21190)
Server function spans now show human-readable names (e.g.,
GET /_serverFn/greetinstead ofGET /_serverFn/a10e70b3...). Thetanstackstart.function.hash.sha256span attribute has been renamed totanstackstart.function.id.Other Changes
dataCollection(#21071)dataCollectioninstead ofsendDefaultPii(#21078)Elysiaapp type to support Elysia options (#21164)Internal Changes
beforeSend*callbacks (#21186)astro-6e2e test build by relaxing astro version range (#21211)normalizecode out of core (#21172)registerSpanErrorInstrumentation()on server (#21169)v10.54.0Compare Source
Important Changes
feat(core): Support array attributes for spans, logs, and metrics (#20427)
Arrays of primitive values (
string,number,boolean) are now accepted as attribute values. Arrays containing non-primitive elements will be dropped and won't show up in Sentry. Array attributes on logs and metrics were previously stringified and will now be sent as actual arrays instead. If you have custom rules that process attribute values in anybeforeSend*callbacks (e.g., data scrubbing), you may need to update them to correctly handle array values.For instance, here's how you can update a
beforeSendLogcallback to handle arrays:feat(browser): Add
fetchStreamPerformanceIntegrationfor streamed response tracking (#20778)A new integration that tracks the performance of streamed fetch responses. Use this to measure time-to-first-byte and streaming duration for APIs that return chunked/streamed data. This replaces the now deprecated
trackFetchStreamPerformanceoption.feat(core): Add
dataCollectionclient option (#20965)Adds a new
dataCollectionclient option for controlling what data the SDK collects and sends to Sentry. This provides a centralized way to configure data collection behavior across different SDK features. In the future, this option will be used for fine-granular data filtering, while the simplesendDefaultPiiboolean option will be deprecated and removed in a future release.feat(hono): Add
hono.requestspans for internal.request()calls (#20843)The Hono SDK now creates spans for internal
.request()calls, providing better visibility into request handling within Hono applications.Other Changes
sentry.sdk.integrationson streamed segment spans (#20428)dataCollection(#21080)dataCollection(#21085)dataCollection(#21072)node:httpon versions that support it (#21009)browserTracingIntegration(#20702)dataCollection(#21073)<head>inside attribute values (#21089)attachStacktraceis true (#19988)Deno.serveinstrumentation on Deno 2.8 (#21155)projectoption type tostring | string[](#21067)http.clientdouble-wrap message (#20705)sentry.replay_idattribute on streamed spans (#20897)replay_idon DSC after buffer-to-session conversion (#20686)types-hoisttotypes(#20979)Internal Changes
sendDefaultPii(#20967)@opentelemetry/instrumentation-httpdependency (#21113)@fastify/otel(#21099)@opentelemetry/instrumentation-pg(#21102)@opentelemetry/sql-common(#21140)@prisma/instrumentation(#21098)Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.