meta(changelog): Update changelog for 9.20.0 #16312
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…16279) This PR fixes two things about our idle spans emitted from `browserTracingIntegration`: 1. The navigation name was sometimes incorrect. This is because we look at `window.location.pathname` at the time when the `popstate` event is emitted - but at this point, this may not be updated yet. So a `navigation` transaction would possibly have the pathname of the previous page as transaction name. 2. The request data is also possibly incorrect - this is set by `HttpContext` integration at event processing time. However, at this time the `window.location` data is also usually already of the following navigation, so the pageload would often have wrong request data associated to it. Now, we store this on the current scope at span creation time to ensure it is actually correct.
[Gitflow] Merge master into develop
- Adds a regex for `GET /__manifest` requests to to the low quality tx filter - Moves the integration into the integration folder
resolves #16237 The SDK automatically instruments the `performance.measure` API, but doesn't support `detail`, which is the way you can attach arbitrary data to `performance.measure`. Given you can see `details` in browser dev-tools, we should probably support it in the same way in Sentry. https://developer.mozilla.org/en-US/docs/Web/API/Performance/measure detail docs: https://developer.mozilla.org/en-US/docs/Web/API/PerformanceMeasure/detail Detail is completely arbitrary, so we have to take care before parsing it. I have added tests accordingly.
fixes #16247 By adjusting the generic, we'll make sure that we don't erase static fields with the `instrumentDurableObjectWithSentry` function. See an example below: ```js class MyDurableObjectBase extends DurableObject { public static readonly VERSION = '1.0.0'; } const MyDurableObject = instrumentDurableObjectWithSentry( () => ({ dsn: 'https://example.com/sentry', tracesSampleRate: 1.0, }), MyDurableObjectBase, ); console.log(MyDurableObject.VERSION); // This will now work correctly ``` By moving the `DurableObjectClass` into it's own generic (`new (state: DurableObjectState, env: E) => T`), which we named `C`, it helps preserve the exact constructor type of the input class, including all its static properties and methods. This was previously being lost by not aligning the `DurableObjectClass` with the function return value.
Forgot to bump this here.
Adds `maxIncomingRequestBodySize` to the Node `httpIntegration`. The setting controls the maximum size of HTTP request bodies attached to events. There is the option `maxRequestBodySize` ([docs](https://develop.sentry.dev/sdk/expected-features/#attaching-request-body-in-server-sdks)) in other SDKs, but to be more specific, this is named with `incoming`. Available options: - 'none': No request bodies will be attached - 'small': Request bodies up to 1,000 bytes will be attached - 'medium': Request bodies up to 10,000 bytes will be attached (default) - 'always': Request bodies will always be attached (up to 1 MB) closes #16179
…-scope-forking feat(node): Fork isolation scope in tRPC middleware
andreiborza
requested review from
mydea,
AbhiPrasad,
chargome,
s1gr1d and
RulaKhaled
andreiborza
force-pushed
the
prepare-release/9.20.0
branch
from
c6d39b9 to
3fefae6
Compare
size-limit report 📦
|
chargome
approved these changes
May 16, 2025
andreiborza
force-pushed
the
prepare-release/9.20.0
branch
from
3fefae6 to
6139041
Compare
The utilities around wrapping are no longer in use since the switch to diagnostics channels in #16177.
andreiborza
force-pushed
the
prepare-release/9.20.0
branch
from
6139041 to
6da8816
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.