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.57.0
->^7.60.0
^7.57.0
->^7.60.0
^7.57.0
->^7.60.0
^1.0.7
->^1.1.2
^7.57.0
->^7.60.0
^7.57.0
->^7.60.0
Release Notes
getsentry/sentry-javascript (@sentry/core)
v7.60.0
Compare Source
Important Changes
We will not send replays that are <5s long anymore. Additionally, we also added further safeguards to avoid overly long (>1h) replays.
You can optionally configure the min. replay duration (defaults to 5s):
Other Changes
v7.59.3
Compare Source
v7.59.2
Compare Source
No changes. This release was published to fix publishing issues with 7.59.0 and 7.59.1.
Please see 7.59.0 for the changes in that release.
v7.59.1
Compare Source
No changes. This release was published to fix a publishing issue with 7.59.0.
Please see 7.59.0 for the changes in that release.
v7.58.1
Compare Source
v7.58.0
Compare Source
Important Changes
This release adds support for distributed tracing without requiring performance monitoring to be active on the JavaScript SDKs (browser and node). This means even if there is no sampled transaction/span, the SDK will still propagate traces to downstream services. Distributed Tracing can be configured with the
tracePropagationTargets
option, which controls what requests to attach thesentry-trace
andbaggage
HTTP headers to (which is what propagates tracing information).feat(tracing): Add tracing without performance to browser and client Sveltekit (#8458)
feat(node): Add tracing without performance to Node http integration (#8450)
feat(node): Add tracing without performance to Node Undici (#8449)
feat(node): Populate propagation context using env variables (#8422)
feat(core): Support
AggregateErrors
inLinkedErrors
integration (#8463)This release adds support for
AggregateErrors
. AggregateErrors are considered as Exception Groups by Sentry, and will be visualized and grouped differently. See the Exception Groups Changelog Post for more details.Exception Group support requires Self-Hosted Sentry version 23.5.1 or newer.
networkDetailDenyUrls
(#8439)This release adds a new option
networkDetailDenyUrls
to theReplay
integration. This option allows you to specify a list of URLs that should not be captured by theReplay
integration, which can be used alongside the existingnetworkDetailAllowUrls
for finely grained control of which URLs should have network details captured.Other Changes
getModule
for Electron SDK (#8488)user.id
to be a number (#8330)crossorigin
attribute on report dialog (#8424)tunnelRoute
when doing static exports (#8471)basePath
option fortunnelRoute
(#8454)basename
option ofcreateBrowserRouter
(#8457)@sentry/node
exports. (#8509)redirect
andcatch
responses (#8467)Work in this release contributed by @mrdulin, @donaldxdonald & @ziyad-elabid-nw. Thank you for your contributions!
getsentry/profiling-node (@sentry/profiling-node)
v1.1.2
Compare Source
Various fixes & improvements
v1.1.1
Compare Source
Various fixes & improvements
34874a6
) by @JonasBav1.1.0
Compare Source
Various fixes & improvements
v1.0.9
Compare Source
Various fixes & improvements
v1.0.8
Compare Source
Various fixes & improvements
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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.