Update dependency @sentry/browser to v7.69.0 #318
Merged
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:
7.68.0
->7.69.0
Release Notes
getsentry/sentry-javascript (@sentry/browser)
v7.69.0
Compare Source
Important Changes
This release introduces a new set of top level APIs for the Performance Monitoring SDKs. These aim to simplify creating spans and reduce the boilerplate needed for performance instrumentation. The three new methods introduced are
Sentry.startSpan
,Sentry.startInactiveSpan
, andSentry.startSpanManual
. These methods are available in the browser and node SDKs.Sentry.startSpan
wraps a callback in a span. The span is automatically finished when the callback returns. This is the recommended way to create spans.If you don't want the span to finish when the callback returns, use
Sentry.startSpanManual
to control when the span is finished. This is useful for event emitters or similar.Sentry.startSpan
andSentry.startSpanManual
create a span and make it active for the duration of the callback. Any spans created while this active span is running will be added as a child span to it. If you want to create a span without making it active, useSentry.startInactiveSpan
. This is useful for creating parallel spans that are not related to each other.Other Changes
BeforeFinishCallback
type (#8999)LinkedErrors
integration runs before all event processors (#8956)org
,project
andurl
as args to upload script (#8985)ignoreErrors
(#8986)pg
spans (#8993)useRoutes
(#8998)glob
to Remix SDK dependencies. (#8963)handleRecordingEmit
aborts when event is not added (#8938)Work in this release contributed by @Duncanxyz and @malay44. Thank you for your contributions!
Configuration
📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.