meta(changelog): Update changelog for 7.52.0 #8118
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 fixes a helper function used in our implementation of `ignoreErrors` so that in the case of linked errors, it filters on the primary error (the one directly caught by `captureException`) rather than the error in the primary error's `cause` property[1]. See #8079 for screenshots and a more detailed explanation. Fixes #8079. [1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause
Co-authored-by: Abhijeet Prasad <[email protected]>
As mentioned by @ryan953 [here](https://github.com/getsentry/getsentry/pull/10418/files#r1183010062), we should check relative URLs properly as well for capturing network details.
…me-origin urls (#8114) We need to adjust our `tracePropagationTargets` default regex to account for protocol-relative URLs. These were previously classified as same-origin, relative URLs, causing tracing headers to be attached which in turn potentially caused CORS errors for users.
lforst
changed the title
AbhiPrasad
reviewed
May 15, 2023
CHANGELOG.md
Outdated
| - fix(tracing-internal): Avoid classifying protocol-relative URLs as same-origin urls (#8114) | ||
| - ref: Hoist `createCheckinEnvelope` to core package (#8082) | ||
|
|
||
| **Important Next.js SDK changes:** |
Member
There was a problem hiding this comment.
Let's just stick with the pattern we've used before? Also this section should go above the individual items above, like what we did with 7.51.0.
Suggested change
| **Important Next.js SDK changes:** | |
| ### Important Changes |
Lms24
reviewed
May 15, 2023
CHANGELOG.md
Outdated
| - fix(docs): Change to `addTracingExtensions` was not documented in MIGRATION.md (#8101) | ||
| - fix(replay): Check relative URLs correctly (#8024) | ||
| - fix(tracing-internal): Avoid classifying protocol-relative URLs as same-origin urls (#8114) | ||
| - ref: Hoist `createCheckinEnvelope` to core package (#8082) |
Member
There was a problem hiding this comment.
Does this need to be in the changelog?
Contributor
Author
There was a problem hiding this comment.
I'd rather have this than not
CHANGELOG.md
Outdated
| - fix(tracing-internal): Avoid classifying protocol-relative URLs as same-origin urls (#8114) | ||
| - ref: Hoist `createCheckinEnvelope` to core package (#8082) | ||
|
|
||
| **Important Next.js SDK changes:** |
Member
There was a problem hiding this comment.
Can we move this section to the top and have the other changes below? This way we're consistent with the changelog messages from the past releases.
AbhiPrasad
approved these changes
May 15, 2023
| - feat(nextjs): Add API method to wrap API routes with crons instrumentation (#8084) | ||
| - feat(nextjs): Add automatic monitors for Vercel Cron Jobs (#8088) | ||
|
|
||
| ### Other changes |
Member
There was a problem hiding this comment.
Suggested change
| ### Other changes | |
| ### Additional Features and Fixes |
Lms24
approved these changes
May 15, 2023
Contributor
size-limit report 📦
|
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.