Ricochet-Exchange / ricochet-frontend

Enter the world of real-time investing
https://www.ricochet.exchange/
Other
46 stars 78 forks source link

⬆️ deps: Bump @sentry/tracing from 6.19.7 to 7.57.0 #935

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps @sentry/tracing from 6.19.7 to 7.57.0.

Release notes

Sourced from @​sentry/tracing's releases.

7.57.0

Important Changes

  • build: Update typescript from 3.8.3 to 4.9.5 (#8255)

This release version bumps the internally used typescript version from 3.8.x to 4.9.x. We use ds-downlevel to generate two versions of our types, one for >=3.8, one for >=4.9. This means that this change should be fully backwards compatible and not have any noticable user impact, but if you still encounter issues please let us know.

  • feat(types): Add tracePropagationTargets to top level options (#8395)

Instead of passing tracePropagationTargets to the BrowserTracing integration, you can now define them on the top level:

Sentry.init({
  tracePropagationTargets: ['api.site.com'],
});
  • fix(angular): Filter out TryCatch integration by default (#8367)

The Angular and Angular-ivy SDKs will not install the TryCatch integration anymore by default. This integration conflicted with the SentryErrorHander, sometimes leading to duplicated errors and/or missing data on events.

  • feat(browser): Better event name handling for non-Error objects (#8374)

When capturing non-errors via Sentry.captureException(), e.g. Sentry.captureException({ prop: "custom object" }), we now generate a more helpful value for the synthetic exception. Instead of e.g. Non-Error exception captured with keys: currentTarget, isTrusted, target, type, you'll now get messages like:

Object captured as exception with keys: prop1, prop2
Event `MouseEvent` (type=click) captured as exception
Event `ErrorEvent` captured as exception with message `Script error.`

Other Changes

  • feat(browser): Send profiles in same envelope as transactions (#8375)
  • feat(profiling): Collect timings on profiler stop calls (#8409)
  • feat(replay): Do not capture replays < 5 seconds (GA) (#8277)
  • feat(tracing): Add experiment to capture http timings (#8371)
  • feat(tracing): Add http.response.status_code to span.data (#8366)
  • fix(angular): Stop routing spans on navigation cancel and error events (#8369)
  • fix(core): Only start spans in trace if tracing is enabled (#8357)
  • fix(nextjs): Inject init calls via loader instead of via entrypoints (#8368)
  • fix(replay): Mark ui.slowClickDetected clickCount as optional (#8376)
  • fix(serverless): Export autoDiscoverNodePerformanceMonitoringIntegrations from SDK (#8382)
  • fix(sveltekit): Check for cached requests in client-side fetch instrumentation (#8391)
  • fix(sveltekit): Only instrument SvelteKit fetch if the SDK client is valid (#8381)

... (truncated)

Changelog

Sourced from @​sentry/tracing's changelog.

7.57.0

Important Changes

  • build: Update typescript from 3.8.3 to 4.9.5 (#8255)

This release version bumps the internally used typescript version from 3.8.x to 4.9.x. We use ds-downlevel to generate two versions of our types, one for >=3.8, one for >=4.9. This means that this change should be fully backwards compatible and not have any noticable user impact, but if you still encounter issues please let us know.

  • feat(types): Add tracePropagationTargets to top level options (#8395)

Instead of passing tracePropagationTargets to the BrowserTracing integration, you can now define them on the top level:

Sentry.init({
  tracePropagationTargets: ['api.site.com'],
});
  • fix(angular): Filter out TryCatch integration by default (#8367)

The Angular and Angular-ivy SDKs will not install the TryCatch integration anymore by default. This integration conflicted with the SentryErrorHander, sometimes leading to duplicated errors and/or missing data on events.

  • feat(browser): Better event name handling for non-Error objects (#8374)

When capturing non-errors via Sentry.captureException(), e.g. Sentry.captureException({ prop: "custom object" }), we now generate a more helpful value for the synthetic exception. Instead of e.g. Non-Error exception captured with keys: currentTarget, isTrusted, target, type, you'll now get messages like:

Object captured as exception with keys: prop1, prop2
Event `MouseEvent` (type=click) captured as exception
Event `ErrorEvent` captured as exception with message `Script error.`

Other Changes

  • feat(browser): Send profiles in same envelope as transactions (#8375)
  • feat(profiling): Collect timings on profiler stop calls (#8409)
  • feat(replay): Do not capture replays < 5 seconds (GA) (#8277)
  • feat(tracing): Add experiment to capture http timings (#8371)
  • feat(tracing): Add http.response.status_code to span.data (#8366)
  • fix(angular): Stop routing spans on navigation cancel and error events (#8369)
  • fix(core): Only start spans in trace if tracing is enabled (#8357)
  • fix(nextjs): Inject init calls via loader instead of via entrypoints (#8368)
  • fix(replay): Mark ui.slowClickDetected clickCount as optional (#8376)
  • fix(serverless): Export autoDiscoverNodePerformanceMonitoringIntegrations from SDK (#8382)
  • fix(sveltekit): Check for cached requests in client-side fetch instrumentation (#8391)

... (truncated)

Commits
  • 3f8fb19 release: 7.57.0
  • f874586 Merge pull request #8417 from getsentry/prepare-release/7.57.0
  • 4d87498 meta(changelog): Update changelog for 7.57.0
  • c89c54a build: Update typescript from 3.8.3 to 4.9.5 (#8255)
  • da295ff Add http.response.status_code to span.data (#8366)
  • b3ee89e feat(tracing): Add experiment to capture http timings (#8371)
  • 88eb034 feat: collect timings on profiler stop calls (#8409)
  • ac435dd feat(tracing): Favour client options tracePropagationTargets (#8399)
  • 0c19446 test(remix): Add Remix v2 future flags integration tests. (#8397)
  • 947db1b feat(browser): send profiles in same envelope as transactions (#8375)
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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[bot] commented 1 year ago

Superseded by #937.