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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update @sentry/integrations requirement from ^7.93.0 to ^7.104.0 in /src #1514

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 1, 2024

Updates the requirements on @sentry/integrations to permit the latest version.

Release notes

Sourced from @​sentry/integrations's releases.

7.104.0

Important Changes

  • feat(performance): create Interaction standalone spans on inp events (#10709)

This release adds support for the INP web vital. This is currently only supported for Saas Sentry, and product support is released with the upcoming 24.3.0 release of self-hosted.

To opt-in to this feature, you can use the enableInp option in the browserTracingIntegration:

Sentry.init({
  integrations: [
    Sentry.browserTracingIntegration({
      enableInp: true,
    });
  ]
})

Other Changes

  • feat(feedback): Flush replays when feedback form opens (#10567)
  • feat(profiling-node): Expose nodeProfilingIntegration (#10864)
  • fix(profiling-node): Fix dependencies to point to current versions (#10861)
  • fix(replay): Add errorHandler for replayCanvas integration (#10796)

Bundle size 📦

Path Size
@​sentry/browser (incl. Tracing, Replay, Feedback) - Webpack (gzipped) 78.71 KB
@​sentry/browser (incl. Tracing, Replay) - Webpack (gzipped) 69.87 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) - Webpack (gzipped) 73.83 KB
@​sentry/browser (incl. Tracing, Replay) - Webpack with treeshaking flags (gzipped) 63.48 KB
@​sentry/browser (incl. Tracing) - Webpack (gzipped) 33.84 KB
@​sentry/browser (incl. browserTracingIntegration) - Webpack (gzipped) 34.88 KB
@​sentry/browser (incl. Feedback) - Webpack (gzipped) 31.44 KB
@​sentry/browser (incl. sendFeedback) - Webpack (gzipped) 31.45 KB
@​sentry/browser - Webpack (gzipped) 22.68 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) - ES6 CDN Bundle (gzipped) 76.96 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (gzipped) 68.38 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (gzipped) 34.18 KB
@​sentry/browser - ES6 CDN Bundle (gzipped) 25.09 KB
@​sentry/browser (incl. Tracing, Replay) - ES6 CDN Bundle (minified & uncompressed) 215.47 KB
@​sentry/browser (incl. Tracing) - ES6 CDN Bundle (minified & uncompressed) 103.28 KB
@​sentry/browser - ES6 CDN Bundle (minified & uncompressed) 75.32 KB
@​sentry/browser (incl. Tracing) - ES5 CDN Bundle (gzipped) 37.35 KB
@​sentry/react (incl. Tracing, Replay) - Webpack (gzipped) 70.25 KB
@​sentry/react - Webpack (gzipped) 22.71 KB

... (truncated)

Changelog

Sourced from @​sentry/integrations's changelog.

7.104.0

Important Changes

  • feat(performance): create Interaction standalone spans on inp events (#10709)

This release adds support for the INP web vital. This is currently only supported for Saas Sentry, and product support is released with the upcoming 24.3.0 release of self-hosted.

To opt-in to this feature, you can use the enableInp option in the browserTracingIntegration:

Sentry.init({
  integrations: [
    Sentry.browserTracingIntegration({
      enableInp: true,
    });
  ]
})

Other Changes

  • feat(feedback): Flush replays when feedback form opens (#10567)
  • feat(profiling-node): Expose nodeProfilingIntegration (#10864)
  • fix(profiling-node): Fix dependencies to point to current versions (#10861)
  • fix(replay): Add errorHandler for replayCanvas integration (#10796)

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)

7.102.1

  • fix(performance): Fixes latest route name and source for interactions not updating properly on navigation (#10702)

... (truncated)

Commits
  • eadb6c8 release: 7.104.0
  • 9d2f623 Merge pull request #10875 from getsentry/abhi-7.104.0-release
  • 868a20e fix(feedback): Update typing for v7
  • 17744cd feat(feedback): Flush replays when feedback form opens (#10567)
  • 3770187 fix(replay): Add errorHandler for replayCanvas integration (#10796)
  • c9e8fa9 meta: CHANGELOG for 7.104.0
  • 763eb1f fix(processing): [v7] Only mark aggregate errors as exception groups (#10866)
  • 82eaed0 feat(performance): create Interaction standalone spans on inp events (#10709)
  • fc676fc use more primitive types
  • 226c543 interactionId
  • 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)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file JavaScript labels Mar 1, 2024
Updates the requirements on [@sentry/integrations](https://github.com/getsentry/sentry-javascript) to permit the latest version.
- [Release notes](https://github.com/getsentry/sentry-javascript/releases)
- [Changelog](https://github.com/getsentry/sentry-javascript/blob/7.104.0/CHANGELOG.md)
- [Commits](getsentry/sentry-javascript@7.93.0...7.104.0)

---
updated-dependencies:
- dependency-name: "@sentry/integrations"
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/src/sentry/integrations-tw-7.104.0 branch from 487aeb1 to c3f5c96 Compare March 1, 2024 08:59
Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 13, 2024

Superseded by #1519.

@dependabot dependabot bot closed this Mar 13, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/src/sentry/integrations-tw-7.104.0 branch March 13, 2024 12: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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants