meta(changelog): Update changelog for 9.14.0 #16115
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
Noticed this flaking sometimes, not 100% sure if this is due to the timeout, but it does not hurt I guess..
Oops, the change I made seems to not work (https://github.com/getsentry/sentry-javascript/actions/runs/14487310833/job/40635465597#step:3:159). This should hopefully fix this by splitting this into two steps.
Another try, hopefully that was it then...
OK I looked for the error in the wrong place, it was in the JSON 🤦 I verified that it works now...
[Gitflow] Merge master into develop
OK, general label adding works now, but the additional labels had a typo, oops...
…ests/test-applications/cloudflare-astro (#16087)
Check whether the baggage data is propagated correctly in connected traces.
Ref: #15436 Summary: - Ports https://github.com/supabase-community/sentry-integration-js into `@sentry/core` - Adds support for `auth` and `auth.admin` operations - Adds browser integration tests - Adds E2E tests running on NextJS --------- Co-authored-by: Sigrid Huemer <32902192+s1gr1d@users.noreply.github.com> Co-authored-by: Luca Forstner <luca.forstner@sentry.io>
Logging the tracing meta tags makes debugging [things like this](#16039) easier.
- Adds new util function `getMetaTagTransformer` for injecting trace meta tags to the html `<head>` - Adds helper function `createSentryHandleRequest` which is a complete Sentry-instrumented handleRequest implementation that handles both route parametrization and trace meta tag injection. -> this is for users that do not need any modifications in their `handleRequest` function - Renames `sentryHandleRequest` to `wrapSentryHandleRequest` to avoid confusion closes #15515
We used to swallow most things when we try to capture request bodies of incoming requests in node. This can make it hard to debug this. This PR adds some log messages here: 1. Logs when we successfully patched `request.on` 2. Logs the errors that happen during patching ref #16090
…sts/test-applications/node-fastify-5 (#16097)
I have a hunch that not all frameworks call `req.on('end')` but may only
do `req.on('close')` or whatever else and this is why we are not
reliably capturing bodies.
It should be safe to attach a `req.on('end')` handler, as that doesn't
change any semantics AFAIK.
Fixes #16090
---------
Co-authored-by: Francesco Gringl-Novy <francesco.novy@sentry.io>
This gets rid of the internal `utils-hoist` barrel file and blanket re-export from it in core.
size-limit report 📦
|
AbhiPrasad
approved these changes
Apr 23, 2025
s1gr1d
approved these changes
Apr 23, 2025
Lms24
approved these changes
Apr 23, 2025
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.