Update dependency @sentry/ember to v9.16.1 #11127
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:
9.15.0
->9.16.1
Release Notes
getsentry/sentry-javascript (@sentry/ember)
v9.16.1
Compare Source
v9.16.0
Compare Source
Important changes
Add a new plugin
makeConfigInjectorPlugin
within our existing vite plugin that updates the global vite config with sentry optionsThis PR implements consistent sampling across traces as outlined in (#15754)
This PR introduces a new
instrumentDurableObjectWithSentry
method to the SDK, which instruments durable objects. We capture both traces and errors automatically.Prisma integration is enabled by default, it should work for both ESM and CJS.
Adds client-side instrumentation for react router's
HydratedRouter
. To enable it, simply replacebrowserTracingIntegration()
withreactRouterTracingIntegration()
in your client-side init call.When running your application in ESM mode, there have been scenarios that resulted in the
http
/https
emitting duplicate spans for incoming requests. This was apparently caused by us double-wrapping the modules for incoming request isolation.In order to solve this problem, the modules are no longer monkey patched by us for request isolation. Instead, we register diagnosticschannel hooks to handle request isolation now.
While this is generally not expected to break anything, there is one tiny change that _may affect you if you have been relying on very specific functionality:
The
ignoreOutgoingRequests
option ofhttpIntegration
receives theRequestOptions
as second argument. This type is not changed, however due to how the wrapping now works, we no longer pass through the full RequestOptions, but re-construct this partially based on the generated request. For the vast majority of cases, this should be fine, but for the sake of completeness, these are the only fields that may be available there going forward - other fields that may have existed before may no longer be set:Other changes
SENTRY_RELEASE
fromenv
(#16201)http.server
spans with 404 status by default (#16205)removeFromDom()
from throwing (#16030)Bundle size 📦
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 was generated by Mend Renovate. View the repository job log.