-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
meta(changelog): Update changelog for 7.81.0 #9596
Merged
Merged
Conversation
This file contains 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
…eam packages (#9158) Instead, users should import this from `@sentry/utils`. This was also re-exported from all downstream packages (e.g. `@sentry/browser`, `@sentry/node`). I don't think this is something users need to import from there...? If you need this, installing `@sentry/utils` is probably fine.
Co-authored-by: Catherine Lee <55311782+c298lee@users.noreply.github.com> Co-authored-by: Billy Vong <billyvg@users.noreply.github.com>
codeql: use extended query pack
…ilding Next.js apps (#9382)
While debugging something, figured it is good to have a test covering that this works as expected! See also: getsentry/sentry-docs#8495
We got somewhat closer to figuring out the problem there. Based on this comment: #9339 (comment) > The requests are now showing with the request body, but the response body is "undefined" It seems that the problem is with parsing the response body for a XHR request. I added some more logging there, to be able to debug this further.
#9533) Also adds a browser integration test as well
I missed some packages when doing #9269
Adds support for the `unmount` hook added in Vue 3. The `destroy` hook no longer works in Vue 2. See PR and issue for more details.
Lms24
approved these changes
Nov 20, 2023
mydea
reviewed
Nov 20, 2023
mydea
reviewed
Nov 20, 2023
|
||
### Other Changes | ||
|
||
- docs(feedback): Example docs on `sendFeedback` (#9560) |
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.
Suggested change
- docs(feedback): Example docs on `sendFeedback` (#9560) |
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.
Thought I'd leave it in because maybe people become inspired and look at the examples 🤷
lforst
force-pushed
the
prepare-release/7.81.0
branch
from
November 20, 2023 09:47
a389fde
to
4ff96ec
Compare
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.