chore(deps): bump @sentry/tracing to ^7.0.0 #47
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:
^6.13.3
->^7.0.0
Release Notes
getsentry/sentry-javascript (@sentry/tracing)
v7.105.0
Compare Source
Important Changes
withActiveSpan
is exported everywhere (#10877)You can use the
withActiveSpan
method to ensure a certain span is the active span in a given callback. This can beused to create a span as a child of a specific span with the
startSpan
API methods:Bundle size 📦
v7.104.0
Compare Source
Important Changes
This release adds support for the INP web vital. This is currently only supported for Saas Sentry, and product support
is released with the upcoming
24.3.0
release of self-hosted.To opt-in to this feature, you can use the
enableInp
option in thebrowserTracingIntegration
:Other Changes
nodeProfilingIntegration
(#10864)errorHandler
for replayCanvas integration (#10796)Bundle size 📦
v7.103.0
Compare Source
Important Changes
forceTransaction
tostartSpan()
APIs (#10819)You can now pass
forceTransaction: true
tostartSpan()
,startSpanManual()
andstartInactiveSpan()
. This allowsyou to start a span that you want to be a transaction, if possible. Under the hood, the SDK will connect this span to
the running active span (if there is one), but still send the new span as a transaction to the Sentry backend, if
possible, ensuring it shows up as a transaction throughout the system.
Please note that setting this to
true
does not guarantee that this will be sent as a transaction, but that the SDKwill try to do so. You can enable this flag if this span is important to you and you want to ensure that you can see it
in the Sentry UI.
Other Changes
Bundle size 📦
v7.102.1
Compare Source
window.location
(#10659)@remix-run/router
a dependency (v7) (#10779)Bundle size 📦
v7.102.0
Compare Source
captureContext
function (#10737)Bundle size 📦
v7.101.1
Compare Source
In version 7.101.0 the
@sentry/hub
package was missing due to a publishing issue. This release contains the packageagain.
webpack://
prefix more broadly from source mapsources
field (#10641)Bundle size 📦
v7.101.0
Compare Source
Hub
constructor (#10584)getReplay
utility function (#10510)exports
field topackage.json
(#10569)v7.100.1
Compare Source
This release contains build fixes for profiling-node.
Bundle size 📦
v7.100.0
Compare Source
Important Changes
Deprecations
This release includes some deprecations. For more details please look at our
migration guide.
The deprecation most likely to affect you is the one of
BrowserTracing
. Instead ofnew BrowserTracing()
, you shouldnow use
browserTracingIntegration()
, which will also handle framework-specific instrumentation out of the box foryou - no need to pass a custom
routingInstrumentation
anymore. For@sentry/react
, we expose dedicated integrationsfor the different react-router versions:
reactRouterV6BrowserTracingIntegration()
reactRouterV5BrowserTracingIntegration()
reactRouterV4BrowserTracingIntegration()
reactRouterV3BrowserTracingIntegration()
See the
migration guide
for details.
browserTracingIntegration()
(#10353)BrowserTracing
integration (#10493)browserProfilingIntegration
(#10438)bunServerIntegration()
(#10439)browserTracingIntegration
(#10397)reactRouterV3BrowserTracingIntegration
for react router v3 (#10489)reactRouterV4/V5BrowserTracingIntegration
for react router v4 & v5 (#10488)reactRouterV6BrowserTracingIntegration
for react router v6 & v6.4 (#10491)browserTracingIntegration
(#10442)WinterCGFetch
withwinterCGFetchIntegration
(#10436)continueTrace
(#10301)new VueIntegration()
(#10440)browserTracingIntegration()
(#10477)browserTracingIntegration()
(#10450)Profiling Node
@sentry/profiling-node
has been ported into the monorepo. Future development for it will happen here!Other Changes
setHttpStatus
from all packages (#10475)Sentry
namespace (#10452)name
&attributes
totracesSampler
(#10426)system-ui
to start of font family (#10464)rrweb
to 2.10.0 (#10445)propagationContextFromHeaders
(#10313)startSpan
,startSpanManual
andstartInactiveSpan
pick up the scopes at time of creation instead oftermination (#10492)
require
call to import Undici (#10388)v7.99.0
Compare Source
Important Changes
Deprecations
This release includes some deprecations for span related methods and integrations in our Deno SDK,
@sentry/deno
. Formore details please look at our
migration guide.
Span.setHttpStatus
in favor ofsetHttpStatus
(#10268)spanStatusfromHttpCode
in favour ofgetSpanStatusFromHttpCode
(#10361)StartSpanOptions.origin
in favour of passing attribute (#10274)Other Changes
@sentry/node
re-exports (#10396)afterAllSetup
hook for integrations (#10345)startSpan()
can handle spans that require parent (#10386)startSpan
APIs (#10300)@sentry/node
functions (#10385, #10391)@sentry/node
re-exports (#10390)@sentry/node
re-exports (#10392)browserTracingIntegration
(#10351)afterAllSetup
is called when usingaddIntegration()
(#10372)spanToTraceContext
function from span utils (#10364)FunctionToString
integration use SETUP_CLIENTS weakmap (#10358)Work in this release contributed by @AleshaOleg. Thank you for your contribution!
Bundle size 📦
v7.98.0
Compare Source
This release primarily fixes some type declaration errors:
IntegrationIndex
type (#10337)Bundle size 📦
v7.97.0
Compare Source
Note: The 7.96.0 release was incomplete. This release is partially encompassing changes from
7.96.0
.stripBasename
option for React Router 6 (#10314)Bundle size 📦
v7.95.0
Compare Source
Important Changes
Deprecations
This release includes some deprecations in preparation for v8.
Most notably, it deprecates the
Replay
&Feedback
classes in favor of a functional replacement:Span.origin
in favor ofsentry.origin
attribute (#10260)Span.parentSpanId
(#10244)isInitialized()
to replace checking viagetClient
(#10296)Replay
,ReplayCanvas
,Feedback
classes (#10270)Wasm
integration class (#10230)Other Changes
parameterize
function available through browser and node API (#10085)addOrUpdateIntegration
(#10263)Work in this release contributed by @AleshaOleg. Thank you for your contribution!
Bundle size 📦
v7.94.1
Compare Source
This release fixes a publishing issue.
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.
This PR has been generated by Mend Renovate. View repository job log here.