meta(changelog): Update changelog for 8.19.0 #12976
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
…acks (#12930) Add a second parameter (`request`) to the `httpIntegration`'s `ignoreIncomingRequests` and `ignoreOutgoingRequests` callbacks. This allows users to not only filter on the URL as previously but on the entire request objects.
This adds docs about how to resolve gitflow merge conflicts. --------- Co-authored-by: Andrei <[email protected]>
Unfortunately, we missed adding a contributor to the changelog https://github.com/getsentry/sentry-javascript/pull/12932/files#r1679943685
I noticed these while working on the cloudflare sdk. - update browser path to use new replay packages We were previously referencing `packages/replay`, which does not exist anymore. This updates us to use the correct paths. - add vercel-edge to nextjs The nextjs sdk depends on vercel-edge, so we should be running tests for it when that package changes. - remove browser from deno The deno sdk no longer relies on the browser sdk, this updates the paths accordingly - add bun section We can be smarter about CI time and only run bun tests when relevant package paths change.
Before: `Time: 2.621 s` After: `Duration 638ms (transform 343ms, setup 0ms, collect 1.61s, tests 22ms, environment 0ms, prepare 278ms)` ref #11084 Also removes `edge-runtime/jest-environment` which we weren't using anyway, removes a lot of unnecessary stuff in our `yarn.lock` (-151 lines!)
Before: `Time: 0.303 s` After: `Duration 271ms (transform 28ms, setup 0ms, collect 26ms, tests 3ms, environment 0ms, prepare 68ms)`
Before: `Time: 2.026 s` After: `Duration 960ms (transform 291ms, setup 0ms, collect 446ms, tests 5ms, environment 283ms, prepare 65ms)` Also: - removes unused `@babel/core` dev dep - removes unused eslintrc logic
SentryCron was missing from the nest readme
…st applications (#12948) Refactor of the existing nestjs test applications. Before we had one sample application testing everything nest-related. This PR splits them up into three applications to make it more readable and easier to understand what is being tested. It also allows for iterating a bit quicker in local development. No new functionality was added. Will add more tests in a follow-up. The three new services are: - nestjs-basic: Simple nestjs application with no submodules and tests for basic functionality of the SDK like error monitoring and span instrumentation. - nestjs-with-submodules: NestJS application that is bit more complex including a submodule (and potentially multiple in the future) to have a more realistic setup for more advanced testing. - nestjs-distributed-tracing: Includes tests for trace propagation with multiple services.
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #12973 --------- Co-authored-by: andreiborza <[email protected]> Co-authored-by: Andrei Borza <[email protected]>
…destroyed (#12786) Add cleanup logic to handle the removal of afterSendEvent, which is set up within the Angular error handler. This fixes memory leaks that occur when the event is still being handled after the root view is removed --------- Co-authored-by: Lukas Stracke <[email protected]>
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #12786 --------- Co-authored-by: Lms24 <[email protected]> Co-authored-by: Andrei Borza <[email protected]>
Lms24
approved these changes
Jul 18, 2024
andreiborza
force-pushed
the
prepare-release/8.19.0
branch
from
90fa8ac to
c7ff1a9
Compare
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.