Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump the sentry group with 2 updates #10595

Merged
merged 1 commit into from Feb 27, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 27, 2024

Bumps the sentry group with 2 updates: @sentry/integrations and @sentry/node.

Updates @sentry/integrations from 7.102.1 to 7.103.0

Release notes

Sourced from @鈥媠entry/integrations's releases.

7.103.0

Important Changes

  • feat(core): Allow to pass forceTransaction to startSpan() APIs (#10819)

You can now pass forceTransaction: true to startSpan(), startSpanManual() and startInactiveSpan(). This allows you to start a span that you want to be a transaction, if possible. Under the hood, the SDK will connect this span to the running active span (if there is one), but still send the new span as a transaction to the Sentry backend, if possible, ensuring it shows up as a transaction throughout the system.

Please note that setting this to true does not guarantee that this will be sent as a transaction, but that the SDK will try to do so. You can enable this flag if this span is important to you and you want to ensure that you can see it in the Sentry UI.

Other Changes

  • fix: Make breadcrumbs option optional in WinterCGFetch integration (#10792)

Bundle size 馃摝

Path Size
@鈥媠entry/browser (incl. Tracing, Replay, Feedback) - Webpack (gzipped) 78.54 KB
@鈥媠entry/browser (incl. Tracing, Replay) - Webpack (gzipped) 69.76 KB
@鈥媠entry/browser (incl. Tracing, Replay with Canvas) - Webpack (gzipped) 73.7 KB
@鈥媠entry/browser (incl. Tracing, Replay) - Webpack with treeshaking flags (gzipped) 63.38 KB
@鈥媠entry/browser (incl. Tracing) - Webpack (gzipped) 33.73 KB
@鈥媠entry/browser (incl. browserTracingIntegration) - Webpack (gzipped) 33.64 KB
@鈥媠entry/browser (incl. Feedback) - Webpack (gzipped) 31.38 KB
@鈥媠entry/browser (incl. sendFeedback) - Webpack (gzipped) 31.39 KB
@鈥媠entry/browser - Webpack (gzipped) 22.66 KB
@鈥媠entry/browser (incl. Tracing, Replay, Feedback) - ES6 CDN Bundle (gzipped) 76.78 KB
@鈥媠entry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped) 68.28 KB
@鈥媠entry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped) 34.08 KB
@鈥媠entry/browser - ES6 CDN Bundle (gzipped) 25.06 KB
@鈥媠entry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed) 215.17 KB
@鈥媠entry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed) 102.96 KB
@鈥媠entry/browser - ES6 CDN Bundle (minified & uncompressed) 75.27 KB
@鈥媠entry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped) 37.25 KB
@鈥媠entry/react (incl. Tracing, Replay) - Webpack (gzipped) 70.14 KB
@鈥媠entry/react - Webpack (gzipped) 22.69 KB
@鈥媠entry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped) 87.86 KB
@鈥媠entry/nextjs Client - Webpack (gzipped) 52.05 KB
@鈥媠entry-internal/feedback - Webpack (gzipped) 17.24 KB
Changelog

Sourced from @鈥媠entry/integrations's changelog.

7.103.0

Important Changes

  • feat(core): Allow to pass forceTransaction to startSpan() APIs (#10819)

You can now pass forceTransaction: true to startSpan(), startSpanManual() and startInactiveSpan(). This allows you to start a span that you want to be a transaction, if possible. Under the hood, the SDK will connect this span to the running active span (if there is one), but still send the new span as a transaction to the Sentry backend, if possible, ensuring it shows up as a transaction throughout the system.

Please note that setting this to true does not guarantee that this will be sent as a transaction, but that the SDK will try to do so. You can enable this flag if this span is important to you and you want to ensure that you can see it in the Sentry UI.

Other Changes

  • fix: Make breadcrumbs option optional in WinterCGFetch integration (#10792)
Commits
  • ef9315d release: 7.103.0
  • c631436 meta(changelog): Add changelog for v7.103.0 (#10820)
  • a10187d feat(core): Allow to pass forceTransaction to startSpan() APIs (backport)...
  • 38976f3 fix: Make breadcrumbs option optional in WinterCGFetch integration (#10792)
  • 6170765 Merge branch 'release/7.102.1' into v7
  • See full diff in compare view

Updates @sentry/node from 7.102.1 to 7.103.0

Release notes

Sourced from @鈥媠entry/node's releases.

7.103.0

Important Changes

  • feat(core): Allow to pass forceTransaction to startSpan() APIs (#10819)

You can now pass forceTransaction: true to startSpan(), startSpanManual() and startInactiveSpan(). This allows you to start a span that you want to be a transaction, if possible. Under the hood, the SDK will connect this span to the running active span (if there is one), but still send the new span as a transaction to the Sentry backend, if possible, ensuring it shows up as a transaction throughout the system.

Please note that setting this to true does not guarantee that this will be sent as a transaction, but that the SDK will try to do so. You can enable this flag if this span is important to you and you want to ensure that you can see it in the Sentry UI.

Other Changes

  • fix: Make breadcrumbs option optional in WinterCGFetch integration (#10792)

Bundle size 馃摝

Path Size
@鈥媠entry/browser (incl. Tracing, Replay, Feedback) - Webpack (gzipped) 78.54 KB
@鈥媠entry/browser (incl. Tracing, Replay) - Webpack (gzipped) 69.76 KB
@鈥媠entry/browser (incl. Tracing, Replay with Canvas) - Webpack (gzipped) 73.7 KB
@鈥媠entry/browser (incl. Tracing, Replay) - Webpack with treeshaking flags (gzipped) 63.38 KB
@鈥媠entry/browser (incl. Tracing) - Webpack (gzipped) 33.73 KB
@鈥媠entry/browser (incl. browserTracingIntegration) - Webpack (gzipped) 33.64 KB
@鈥媠entry/browser (incl. Feedback) - Webpack (gzipped) 31.38 KB
@鈥媠entry/browser (incl. sendFeedback) - Webpack (gzipped) 31.39 KB
@鈥媠entry/browser - Webpack (gzipped) 22.66 KB
@鈥媠entry/browser (incl. Tracing, Replay, Feedback) - ES6 CDN Bundle (gzipped) 76.78 KB
@鈥媠entry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped) 68.28 KB
@鈥媠entry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped) 34.08 KB
@鈥媠entry/browser - ES6 CDN Bundle (gzipped) 25.06 KB
@鈥媠entry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed) 215.17 KB
@鈥媠entry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed) 102.96 KB
@鈥媠entry/browser - ES6 CDN Bundle (minified & uncompressed) 75.27 KB
@鈥媠entry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped) 37.25 KB
@鈥媠entry/react (incl. Tracing, Replay) - Webpack (gzipped) 70.14 KB
@鈥媠entry/react - Webpack (gzipped) 22.69 KB
@鈥媠entry/nextjs Client (incl. Tracing, Replay) - Webpack (gzipped) 87.86 KB
@鈥媠entry/nextjs Client - Webpack (gzipped) 52.05 KB
@鈥媠entry-internal/feedback - Webpack (gzipped) 17.24 KB
Changelog

Sourced from @鈥媠entry/node's changelog.

7.103.0

Important Changes

  • feat(core): Allow to pass forceTransaction to startSpan() APIs (#10819)

You can now pass forceTransaction: true to startSpan(), startSpanManual() and startInactiveSpan(). This allows you to start a span that you want to be a transaction, if possible. Under the hood, the SDK will connect this span to the running active span (if there is one), but still send the new span as a transaction to the Sentry backend, if possible, ensuring it shows up as a transaction throughout the system.

Please note that setting this to true does not guarantee that this will be sent as a transaction, but that the SDK will try to do so. You can enable this flag if this span is important to you and you want to ensure that you can see it in the Sentry UI.

Other Changes

  • fix: Make breadcrumbs option optional in WinterCGFetch integration (#10792)
Commits
  • ef9315d release: 7.103.0
  • c631436 meta(changelog): Add changelog for v7.103.0 (#10820)
  • a10187d feat(core): Allow to pass forceTransaction to startSpan() APIs (backport)...
  • 38976f3 fix: Make breadcrumbs option optional in WinterCGFetch integration (#10792)
  • 6170765 Merge branch 'release/7.102.1' into v7
  • See full diff 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 will merge this PR once CI passes on it, as requested by @mdn-bot.


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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the sentry group with 2 updates: [@sentry/integrations](https://github.com/getsentry/sentry-javascript) and [@sentry/node](https://github.com/getsentry/sentry-javascript).


Updates `@sentry/integrations` from 7.102.1 to 7.103.0
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/7.103.0/CHANGELOG.md)
- [Commits](getsentry/sentry-javascript@7.102.1...7.103.0)

Updates `@sentry/node` from 7.102.1 to 7.103.0
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/7.103.0/CHANGELOG.md)
- [Commits](getsentry/sentry-javascript@7.102.1...7.103.0)

---
updated-dependencies:
- dependency-name: "@sentry/integrations"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: sentry
- dependency-name: "@sentry/node"
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: sentry
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot requested a review from mdn-bot as a code owner February 27, 2024 11:53
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Feb 27, 2024
@mdn-bot
Copy link
Collaborator

mdn-bot commented Feb 27, 2024

@dependabot squash and merge

@dependabot dependabot bot merged commit a2a1f1b into main Feb 27, 2024
12 checks passed
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/sentry-83f1e6f404 branch February 27, 2024 11:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant