-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
meta(changelog): Update changelog for 7.70.0 #9052
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
[Gitflow] Merge master into develop
…#9014) Instead we can ensure this is called after all processing finished via a hook. This does not actually process an event, so this is much cleaner.
…seClient` (#8933) Since common server bahaviour has now moved to `ServerRuntimeClient`, the Node client can now extend that rather than the base client. This PR also moves the request session flusher to `ServerRuntimeClient` which leaves the Node client empty apart from a constructor wrapper to preserve backwards compatibilty.
The current version of cookies includes several performance improvements: https://github.com/jshttp/cookie/releases
This adds a new (optional) `processEvent` hook on the `Integration` interface, which allows to register an event processor **for the current client only**. This has actually correct semantics in that the processor will only be registered for the client that the integration is added for. This is done by adding a new `addEventProcessor` method on the client, which for now are called after all global & scope event processors. Previously, all integrations always registered a _global_ event processor, which is not really necessary. With this, we can be much more focused & also skip checking for existence of the integration on the client etc.
This refactors the code for keeping breadcrumbs on transactions in node-experimental to instead patch `startTransaction` on the hub.
…ns (#9031) This try-catches any monkeypatching we do on objects, to avoid us throwing e.g. if trying to patch a frozen object. Obv. the monkey patching will _not_ actually work then, but I guess it's better to not wrap stuff than to error out in userland. I also added some tests for this! Fixes #9030
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
…9034) Replay events also go through global event processors, so they should also go through this hook (replay events are not sent via the regular baseclient methods).
Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
…entry`'s generic type. (#9043) Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
This PR adds a `@sentry/vercel-edge` SDK that can be used by our Next.js or Sveltekit SDKs for edge runtime support.
Lms24
reviewed
Sep 20, 2023
Adds NPM target entry for vercel-edge package ref #8087
Switch to new vercel-edge package Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
`handleErrorWithSentry`, which is wrapper function, should be identity function (`f(x) => x`). Implementation is fine, just the type mismatch from implementation. Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
Apply suggestions from code review
94c2af9
to
bc2df49
Compare
Ready to go from my PoV, lmk if you wanna add more things to this release! |
Lms24
approved these changes
Sep 20, 2023
mydea
approved these changes
Sep 20, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lforst
approved these changes
Sep 20, 2023
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.
Needs #9051 and #9053 to merge first