meta(changelog): Update changelog for 7.46.0 #7666
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
No need to depend on @sentry/browser as devDependency, which Nx complains about. I copied the TestClient from Replay, where we had the same issue.
…unctions (#7609) Adjust the span ops of `load` functions to distinguish between spans of server-only and universal `load` functions (`+page.ts` vs `+page.server.ts`):
… loads (#7603) Co-authored-by: Abhijeet Prasad <[email protected]>
Apparently, the `%sveltekit.head%` placeholder isn't present in the html that's passed to `transformPageChunk`. Hence our `<meta>` tag injection logic introduced in #7574 didn't find the anchor point where to inject the tags. This PR fixes the injection, by simply appending it to an open `<head>` tag. It's not pretty but it should do the trick 🤞 (we can revisit if this breaks folks).
…#7613) Add a few more properties to `resource` performance entries (e.g. script, img, etc). * Adds `responseStatus` which is new in Chrome 109 for status code * Adds `decodedBodySize` so that we can tell user if their resource was compressed or not.
Add a small test to check if the SDK parses a rate limit response that has no category but a scope: `60::organization`. This came up in Slack and in getsentry/ops#6446 (comment).
This works similar to `ignoreErrors`, but matches transaction names.
Previously, we always created a new domain when entering the `sentryHandle` function. This caused "nested" SvelteKit Server calls to create new transaction whenever a new domain was created in the `sentryHandle` function because the active span is bound to the domain. This fix introduces a check if there is an active transaction, in which case we just execute the handler and don't create a new domain, as we are already in this active domain. As a result, nested SK server calls become a span of the parent server call instead of a new transaction.
Fix Node SDK exports not being available in prod builds. For example, calling `Sentry.withScope(...)` throws an error because `withScope` is not defined on the top-level namespace. This is because for CJS, Vite puts wildcard-exported properties into the `default` property rather than onto the namespace in production builds.
Split up the previously generic `handleLoadWithSentry` wrapper function into two functions on the server side: * `handleLoadWithSentry` to wrap universal load on server and client * `handleServerLoadWithSentry` to wrap server load on the server (duh) It further adjusts types on the client as well as on the server side to return a generic. The very liberal typing of the functions' generic is on purpose because any type that's more narrowed down (e.g. `T extends Load`) would create a type error with the users' actual load types. These types (e.g. `PageData` or `ServerLayoutData`) are generated at build time per route/page. Hence, we cannot access them.
…upted by another (#7655)
…d` transaction active (#7614) Co-authored-by: Francesco Novy <[email protected]> Co-authored-by: Abhijeet Prasad <[email protected]>
Co-authored-by: Kamil Ogórek <[email protected]>
…7663) To make our Sentry SDK setup easier, we'll instruct users to init the SDK in the hooks files rather than in the dedicated sentry.client|server.config.js files (#7661). To support this change, this PR makes the injection of our `injectSentryInitPlugin` into the users' build config depend on the existence of said sentry config files. If they don't exist, there's no need to add the plugin or adjust the server config.
…p in README (#7661) Restructures SDK setup into client, server and build setup sections. Also moves init call from dedicated files to hooks.
mydea
reviewed
Mar 30, 2023
mydea
reviewed
Mar 30, 2023
Lms24
reviewed
Mar 30, 2023
Co-authored-by: Alden Quimby <[email protected]> Co-authored-by: Alden Quimby <[email protected]> Co-authored-by: Michi Hoffmann <[email protected]>
lforst
reviewed
Mar 30, 2023
Co-authored-by: Luca Forstner <[email protected]>
AbhiPrasad
force-pushed
the
prepare-release/7.46.0
branch
from
dca631b to
a3c8b9e
Compare
|
Rebased to include #7667, added heading items, and re-formatted content. |
AbhiPrasad
force-pushed
the
prepare-release/7.46.0
branch
2 times, most recently
from
a69ef59 to
0a62ebe
Compare
AbhiPrasad
force-pushed
the
prepare-release/7.46.0
branch
from
0a62ebe to
5e288f5
Compare
Lms24
approved these changes
Mar 30, 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.
No description provided.