fix(deps): update sentry packages to v7.57.0 (minor) #270
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.53.1
->7.57.0
7.53.1
->7.57.0
Release Notes
getsentry/sentry-javascript (@sentry/react)
v7.57.0
Compare Source
Important Changes
This release version bumps the internally used typescript version from 3.8.x to 4.9.x.
We use ds-downlevel to generate two versions of our types, one for >=3.8, one for >=4.9.
This means that this change should be fully backwards compatible and not have any noticable user impact,
but if you still encounter issues please let us know.
Instead of passing
tracePropagationTargets
to theBrowserTracing
integration, you can now define them on the top level:TryCatch
integration by default (#8367)The Angular and Angular-ivy SDKs will not install the TryCatch integration anymore by default.
This integration conflicted with the
SentryErrorHander
, sometimes leading to duplicated errors and/or missing data on events.When capturing non-errors via
Sentry.captureException()
, e.g.Sentry.captureException({ prop: "custom object" })
,we now generate a more helpful value for the synthetic exception. Instead of e.g.
Non-Error exception captured with keys: currentTarget, isTrusted, target, type
, you'll now get messages like:Other Changes
http.response.status_code
tospan.data
(#8366)trace
if tracing is enabled (#8357)clickCount
as optional (#8376)autoDiscoverNodePerformanceMonitoringIntegrations
from SDK (#8382)fetch
if the SDK client is valid (#8381)sessionStorage
check (#8394)v7.56.0
Compare Source
window.open
for slow clicks (#8308)debug_meta
before sending (#8347)next
in Vue router 4 instrumentation (#8351)v7.55.2
Compare Source
EventType
from@sentry-internal/rrweb
(#8334)v7.55.1
Compare Source
@sentry-internal/rrweb
(#8329)v7.55.0
Compare Source
v7.54.0
Compare Source
Important Changes
feat(core): Add default entries to
ignoreTransactions
for Healthchecks #8191All SDKs now filter out health check transactions by default.
These are transactions where the transaction name matches typical API health check calls, such as
/^.*healthy.*$/
or/^. *heartbeat.*$/
. Take a look at this list to learn which regexes we currently use to match transaction names.We believe that these transactions do not provide value in most cases and we want to save you some of your quota by filtering them out by default.
These filters are implemented as default values for the top level
ignoreTransactions
option.You can disable this filtering by manually specifiying the
InboundFilters
integration and setting thedisableTransactionDefaults
option:feat(replay): Add
mutationBreadcrumbLimit
andmutationLimit
to Replay Options (#8228)The previously experimental options
mutationBreadcumbLimit
andmutationLimit
have been promoted to regular Replay integration options.A high number of DOM mutations (in a single event loop) can cause performance regressions in end-users' browsers.
Use
mutationBreadcrumbLimit
to send a breadcrumb along with your recording if the mutation limit was reached.Use
mutationLimit
to stop recording if the mutation limit was reached.feat(sveltekit): Add source maps support for Vercel (lambda) (#8256)
The SvelteKit SDK can now be used if you deploy your SvelteKit app to Vercel.
By default, the SDK's Vite plugin will detect the used adapter and adjust the source map uploading config as necessary.
If you want to override the default adapter detection, you can specify the
adapter
option in thesentrySvelteKit
options:Currently, the Vite plugin will configure itself correctly for
@sveltejs/adapter-auto
,@sveltejs/adapter-vercel
and@sveltejs/adapter-node
.Important: The SvelteKit SDK is not yet compatible with Vercel's edge runtime.
It will only work for lambda functions.
Other Changes
loadContext
through wrapped document request function (#8268)magicast
to supportsatisfied
keyword (#8254)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 10pm every weekday,before 5am every weekday,every weekend" (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 these updates again.
This PR has been generated by Mend Renovate. View repository job log here.