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.48.0
->^7.50.0
^7.48.0
->^7.50.0
^7.48.0
->^7.50.0
^7.48.0
->^7.50.0
^7.48.0
->^7.50.0
1.20.0
->1.20.1
Release Notes
getsentry/sentry-javascript
v7.50.0
Compare Source
Important Changes
sentryHandle
to a factory function (#7975)With this release, the Sveltekit SDK (@sentry/sveltekit) is promoted to Beta.
This means that we do not expect any more breaking changes.
The final breaking change is that
sentryHandle
is now a function.So in order to update to 7.50.0, you have to update your
hooks.server.js
file:You can now capture request/response bodies & headers of network requests in Replay.
You have to define an allowlist of URLs you want to capture additional information for:
By default, we will capture request/response bodies, as well as the request/response headers
content-type
,content-length
andaccept
.You can configure this with some additional configuration:
Note that bodies will be truncated to a max length of ~150k characters.
- feat(replay): Changes of sampling behavior & public API
flush()
API to record current event buffer (#7743)stop()
to flush and remove current session (#7741)We have changed the behavior of error-based sampling, as well as adding & adjusting APIs a bit to be more aligned with expectations.
See Sampling for details.
We've also revamped some public APIs in order to be better aligned with expectations. See Stoping & Starting Replays manually for details.
We added a new transport to support multiplexing.
With this, you can configure Sentry to send events to different DSNs, depending on a logic of your choosing:
Additional Features and Fixes
disableLogger
option that automatically tree shakes logger statements (#7908)db.system
span data to DB spans (#7952)Work in this release contributed by @Jack-Works. Thank you for your contribution!
v7.49.0
Compare Source
Important Changes
svelte.config.js
(#7863)Our source maps upload plugin is now able to read
svelte.config.js
. This is necessary to automatically find the output directory that users can specify when setting up the Node adapter.This release fixes a potential problem with how Replay captures console logs.
Any objects logged will now be cut off after a maximum depth of 10, as well as cutting off any properties after the 1000th.
This should ensure we do not accidentally capture massive console logs, where a stringified object could reach 100MB or more.
We used to normalize references to HTML elements as POJOs.
This is both not very easily understandable, as well as potentially large, as HTML elements may have properties attached to them.
With this change, we now normalize them to e.g.
[HTMLElement: HTMLInputElement]
.Additional Features and Fixes
import
forgatsby-browser.js
instead ofrequire
(#7889)handleError
wrapper (#7898)sentry.properties
file when uploading source maps (#7890)timestampWithMs
(#7878)getsentry/sentry-webpack-plugin
v1.20.1
Compare Source
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.