meta(changelog): Update changelog for 7.61.0 #8682
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
…8649) Noticed that when running `yarn test:run` it sometimes hang forever. Solved this with two steps: 1. Make sure we actually output the shell stuff, as otherwise it is super hard to debug what's going on. 2. The problem was that sometimes `pnpm` prompts to re-create node_modules (??), and the prompt was obviously forever hanging. I couldn't find any option to disable this from pnpm side, sadly 😬 So I ended up adding a step to clean out all node_modules etc. before running the tests.
[Gitflow] Merge master into develop
A validation test for transaction trim end since I noticed this wasn't being tested. Trying to sanity check why trimming is not working for some timestamps.
if we see that a `sentry-trace` header was already attached on the `requestOptions`, don't attach sentry trace and baggage headers again.
…VP for POTEL (#8609) This introduces a new package `@sentry/node-experimental`, which is an MVP implementation for Performance powered by OTEL (POTEL). This package provides a wrapper over `@sentry/node` (also using `@sentry/opentelemetry-node`) which uses opentelemetry for performance instrumentation under the hood. This is all abstracted away from the user, they only need to do: ```js import * as Sentry from '@sentry/node-experimental'; Sentry.init({ dsn: 'my-dsn', tracesSampleRate: 0.1 }); ``` And it will set up all the necessary integrations etc. for the user, including the default integrations + any applying performance integrations. For this, I added all performance integrations that exist for node, minus undici (which will take some more work to get going), plus some new stuff: mysql, fastify, nest. Also, mongoose is it's own integration now, not handled via mongo anymore. Note that I've only manually tested express & http so far. All others still need to be verified etc. But this is really a POC, which may go somewhere or not - by publishing this, it becomes super easy to try this in various scenarios. I have tweaked the Http integration to create more or less the same output as we're used to for Sentry. I also made small tweaks to `@sentry/opentelemetry-node` to allow us to communicate with this a bit better. There are two main use cases I've identified there: * Tell the span processor to drop a span (=not send it to Sentry). For this, I added dedicated hooks. * Add some specific data/context/tags/metadata to an otel span, that should be added to the resulting sentry span. For this, I added utils which keep a map of data to be added in `spanEnd`. --------- Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
…ack frames (#8670) Adds a new browser integration - `ContextLines`. It can be used to add source code lines to and around stack frames that point towards JS in html files (e.g. in `<script>` tags or `onclick` handlers). The integration **does not** apply these context lines to frames pointing to actual script files as these cannot be accessed within the browser.
AbhiPrasad
approved these changes
Jul 31, 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.
Changelog for 7.61.0.
Please somebody also double check that the setup for releasing node-experimental is fine - I checked the pre-release checklist, but to be sure...!