meta: Update changelog for 8.11.0 #12591
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
I noticed that this was not actually working, maybe the check here was wrong 🤔 According to here: https://stackoverflow.com/questions/61886993/in-github-actions-how-to-get-the-type-of-a-trigger-event-as-a-variable this should work!
…2543) We want to support v7 with critical bug fixes until EOY 2024. So we're explicitly stating this in the readme, and I also fixed/updated some other small things.
[Gitflow] Merge master into develop
ref #12513 This PR upgrades release detection for Node and Vercel Edge SDKs. This change adds release name detection for: - GitLab CI - AppVeyor - AWS Amplify - Azure Pipelines - Bitrise - Buddy CI - Cirrus CI - Codefresh - Codemagic - Semaphore CI - Travis CI - CloudBees CodeShip - Coolify - Jenkins - TeamCity - Woodpecker CI Based on getsentry/sentry-javascript-bundler-plugins#549 Supercedes #12507
We need to import from `@sentry/core` instead of a relative import otherwise the types break.
With this PR, you can now pass a `parentSpan` optionally to `startSpan*`
APIs to create a span as a child of a specific span:
```js
const span = Sentry.startInactiveSpan({ name: 'xxx', parentSpan: parent });
Sentry.startSpan({ name: 'xxx', parentSpan: parent }, () => {});
Sentry.startSpanManual({ name: 'xxx', parentSpan: parent }, () => {});
```
With this, it should be easier to understand how you can manually work
with spans in v8.
Closes #12539
ref #12566, which I
noticed while working on this. For now I just cast the span which should
be fine, but is not ideal.
See: https://github.com/getsentry/sentry-javascript/blob/fn/contributing-docs/CONTRIBUTING.md --------- Co-authored-by: Andrei <168741329+andreiborza@users.noreply.github.com>
Aligns (and sorts) explicit exports from `@sentry/node` in Astro / Remix / Sveltekit SDKs. NextJS SDK does not seem to have explicit exports.
AbhiPrasad
requested review from
chargome,
nicohrubec,
mydea and
lforst
and removed request for
a team
andreiborza
approved these changes
Jun 20, 2024
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.
Need to release fix for #12564 asap.