chore(deps): bump @sentry/profiling-node from 7.111.0 to 8.11.0

[dependabot]

Bumps @sentry/profiling-node from 7.111.0 to 8.11.0.

Release notes

Sourced from @​sentry/profiling-node's releases.

8.11.0

Important Changes

• feat(core): Add parentSpan option to startSpan* APIs (#12567)

We've made it easier to create a span as a child of a specific span via the startSpan* APIs. This should allow you to explicitly manage the parent-child relationship of your spans better.

Sentry.startSpan({ name: 'root' }, parent => {
  const span = Sentry.startInactiveSpan({ name: 'xxx', parentSpan: parent });
Sentry.startSpan({ name: 'xxx', parentSpan: parent }, () => {});
Sentry.startSpanManual({ name: 'xxx', parentSpan: parent }, () => {});
});

Other Changes

• feat(node): Detect release from more providers (#12529)
• fix(profiling-node): Use correct getGlobalScope import (#12564)
• fix(profiling-node) sample timestamps need to be in seconds (#12563)
• ref: Align @sentry/node exports from framework SDKs. (#12589)

Bundle size 📦

Path	Size
@​sentry/browser	22.22 KB
@​sentry/browser (incl. Tracing)	33.31 KB
@​sentry/browser (incl. Tracing, Replay)	69.09 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags	62.41 KB
@​sentry/browser (incl. Tracing, Replay with Canvas)	73.14 KB
@​sentry/browser (incl. Tracing, Replay, Feedback)	85.31 KB
@​sentry/browser (incl. Tracing, Replay, Feedback, metrics)	87.17 KB
@​sentry/browser (incl. metrics)	26.5 KB
@​sentry/browser (incl. Feedback)	38.42 KB
@​sentry/browser (incl. sendFeedback)	26.85 KB
@​sentry/browser (incl. FeedbackAsync)	31.42 KB
@​sentry/react	24.96 KB
@​sentry/react (incl. Tracing)	36.35 KB
@​sentry/vue	26.32 KB
@​sentry/vue (incl. Tracing)	35.16 KB
@​sentry/svelte	22.35 KB
CDN Bundle	23.41 KB
CDN Bundle (incl. Tracing)	35.04 KB
CDN Bundle (incl. Tracing, Replay)	69.17 KB
CDN Bundle (incl. Tracing, Replay, Feedback)	74.34 KB
CDN Bundle - uncompressed	68.76 KB

... (truncated)

Changelog

Sourced from @​sentry/profiling-node's changelog.

8.11.0

Important Changes

• feat(core): Add parentSpan option to startSpan* APIs (#12567)

We've made it easier to create a span as a child of a specific span via the startSpan* APIs. This should allow you to explicitly manage the parent-child relationship of your spans better.

Sentry.startSpan({ name: 'root' }, parent => {
  const span = Sentry.startInactiveSpan({ name: 'xxx', parentSpan: parent });
Sentry.startSpan({ name: 'xxx', parentSpan: parent }, () => {});
Sentry.startSpanManual({ name: 'xxx', parentSpan: parent }, () => {});
});

Other Changes

• feat(node): Detect release from more providers (#12529)
• fix(profiling-node): Use correct getGlobalScope import (#12564)
• fix(profiling-node) sample timestamps need to be in seconds (#12563)
• ref: Align @sentry/node exports from framework SDKs. (#12589)

8.10.0

Important Changes

• feat(remix): Migrate to opentelemetry-instrumentation-remix. (#12110)

You can now simplify your remix instrumentation by opting-in like this:

const Sentry = require('@sentry/remix');
Sentry.init({
dsn: YOUR_DSN
// opt-in to new auto instrumentation
autoInstrumentRemix: true,
});

With this setup, you do not need to add e.g. wrapExpressCreateRequestHandler anymore. Additionally, the quality of the captured data improves. The old way to use @sentry/remix continues to work, but it is encouraged to use the new setup.

Other Changes

• feat(browser): Export thirdPartyErrorFilterIntegration from @sentry/browser (#12512)

... (truncated)

Commits

• dd0830b release: 8.11.0
• 11090b8 Merge pull request #12591 from getsentry/prepare-release/8.11.0
• 2331958 meta: Update changelog for 8.11.0
• dfa863a ref: Align @sentry/node exports from framework SDKs. (#12589)
• 00ee962 test: Update profiling e2e test to use typescript (#12565)
• 31700c9 docs: Improve contributing docs (#12541)
• 0019309 feat(core): Add parentSpan option to startSpan* APIs (#12567)
• 424937f fix(profiling) sample timestamps need to be in seconds (#12563)
• 847c05a fix(profiling-node): Use correct getGlobalScope import (#12564)
• fc165e5 feat(node): Detect release from more providers (#12529)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pull-request-checklist-buddy]

👨‍💻 Dev Branch checks

• All Code checks are successfully?
• No sensetive data leaked?
• Code works as expected?
• Debug Code removed?
• Code Review approved?

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@sentry/[email protected]	environment, filesystem, shell Transitive: network, unsafe	+95	28.7 MB	sentry-bot

🚮 Removed packages: npm/@sentry/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Shell access	npm/@opentelemetry/[email protected]	Module: child_process Location: Package overview	package-lock.json package.json	🚫
Shell access	npm/@opentelemetry/[email protected]	Module: child_process Location: Package overview	package-lock.json package.json	🚫

View full report↗︎

Next steps

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/@opentelemetry/[email protected]

[dependabot]

Superseded by #2033.