meta(changelog): Update changelog for v8.0.0-beta.6 #11883
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
This updates the versions of some dependencies for the Ember SDK: * `ember-auto-import` is bumped to `^2.4.3` * `ember-cli-babel` is bumped to `^8.2.0` * `ember-cli-typescript` is bumped to `^5.3.0` Closes #11730
Adds types for `geo` in the user object https://develop.sentry.dev/sdk/event-payloads/user/
They fail because a secret is missing, we can skip them for dependabot. See: https://github.com/orgs/community/discussions/26253
Defaults to having screenshots.
…ndle sizes (#11791) It's more aggressive to start with the async loading strategy in the CDN bundle, but could be safer because if we want to change from async->sync it would not really be a majr version change. Whereas going from sync->async would be more of a big feature, riskier, and could demand a version bump or something.
…render (#11859) This fixes the conditions for loading and rendering the screenshot integration.... also improves the conditions for not rendering it if we're on a mobile device. - We should check the local`options.showScreenshot` instead of the closed-over `showScreenshot` because the options might have changed for this instance of the widget - We should combine `options.showScreenshot` (the desire) with `isScreenshotSupported()` (the possibility) to set the right expectation
This adds a [Zod](https://github.com/colinhacks/zod) integration to sentry that adds better support for ZodError issues. Currently, the ZodError message is a formatted json string that gets truncated and the full list of issues are lost. - Adds the full list of issues to `extras['zoderror.issues']`. - Replaces the error message with a simple string. before   after    --------- Co-authored-by: Francesco Novy <[email protected]>
Turns out we were not correctly setting parametrized route names for react router v4/v5 😬 We had no proper test covering this. So I added a new E2E test `react-router-5` that actually checks that parametrization etc. works as expected. While at it, I also updated the react-router-6 E2E test to actually check these things as well - previously, we mostly only checked that _anything_ was sent to sentry, but didn't look at the content we sent. Fixes #11815
This updates the react router v6 E2E test to actually check what data we send.
ref #11782 --------- Co-authored-by: Francesco Novy <[email protected]>
Integration for Node `integrations: [Sentry.experimental_redisIntegration()]` --------- Co-authored-by: Francesco Novy <[email protected]>
This was brought up here #5578 (comment), our error handler implementation was too naive, and our tests not ideal - the tests only checked that stuff is sent to sentry (which it was!) but not that the page otherwise worked. Now, I updated the test to ensure this works as expected. With this PR, the signature for `Sentry.setupNestErrorHandler()` changes ( breaking change, but sadly required at this point). You have to pass in an exception filter, which we'll extend to _also_ send exceptions to Sentry: ```js import { BaseExceptionFilter, HttpAdapterHost } from '@nestjs/core'; const { httpAdapter } = app1.get(HttpAdapterHost); Sentry.setupNestErrorHandler(app1, new BaseExceptionFilter(httpAdapter)); ``` This is a bit more involved, but also allows you to use a custom filter if needed (we can extend _any_ exception filter).
Per the docs: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#codeowners-file-location > file called CODEOWNERS in the .github/, root, or docs/ directory of the repository, in the branch where you'd like to add the code owners. But also, in our case: > If CODEOWNERS files exist in more than one of those locations, GitHub will search for them in that order and use the first one it finds. So we just need the one file.
Port from v7: #11754 --------- Co-authored-by: Abhijeet Prasad <[email protected]> Co-authored-by: JonasBa <[email protected]>
This PR adds a new `captureFeedback` method which is exported from all SDKs. This method can be used to capture a (new) user feedback from any package. We follow the same semantics as for other capture methods like `captureException()` or `captureMessage()`: The method returns a string, which is the event id. We do not wait for sending to be successful or not, we just try to send it and return. You can both set an `associatedEventId` (which replaces the event_id of the "old" `captureUserFeedback`), and also pass attachments to send along (which for now are sent as a separate envelope). For usage in the modal UI, there is still `sendFeedback` which continues to return a promise that resolves with the event ID, or rejects with a meaningful error message if sending fails. This also deprecates `captureUserFeedback()`, which is only exported in browser. We cannot remove this yet because `captureFeedback` will only work on newer self-hosted instances, so not all users can easily update. We can/should remove this in v9. Includes #11626 Fixes 49946
This commit updates all tracing functionality to run outside the Angular zone. Before this change, it hindered server-side rendering and hydration, causing instability in the app. The app achieves stability when there are no micro/macro tasks running. As a result, the HTML can now be serialized and sent to the client.
Since there seem to be issues around this in the backend/UI today, we decided to not send these for now. We may revisit this later... I left the code to send this in for now, so we can revert this more easily if needed.
So we have a proper usage path without installing utils & core...
…ion (#11882) In theory it is possible that people still have files like `sentry.server.config.ts` and reference them from `instrumentation.ts`. In that case we do not want to show the warning about the old way.
lforst
approved these changes
May 3, 2024
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.
Last beta...?!