search

blackspherefollower / NogasmChart

A Nogasm session recording tool
BSD 3-Clause "New" or "Revised" License
18 stars 5 forks source link

build(deps): Bump Sentry from 3.13.0 to 3.16.0 in /NogasmChart #53

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps Sentry from 3.13.0 to 3.16.0.

Release notes

Sourced from Sentry's releases.

3.16.0

Features

  • Use a default value of 60 seconds if a Retry-After header is not present. (#1537)
  • Add new Protocol definitions for DebugImages and AddressMode (#1513)
  • Add HttpTransport extensibility and synchronous serialization support (#1560)
  • Add UseAsyncFileIO to Sentry options (enabled by default) (#1564)

Fixes

  • Fix event dropped by bad attachment when no logger is set. (#1557)
  • Ignore zero properties for MemoryInfo (#1531)
  • Cleanup diagnostic source (#1529)
  • Remove confusing message Successfully sent cached envelope (#1542)
  • Fix infinite loop in SentryDatabaseLogging.UseBreadcrumbs (#1543)
  • GetFromRuntimeInformation() in try-catch (#1554)
  • Make Contexts properties more thread-safe (#1571)
  • Fix PlatformNotSupportedException exception on net6.0-maccatalyst targets (#1567)
  • In ASP.Net Core, make sure that SentrySdk.LastEventId is accessible from exception handler pages (#1573)

3.15.0

Features

  • Expose ConfigureAppFrame as a public static function. (#1493)

Fixes

  • Make SentryDiagnosticSubscriber._disposableListeners thread safe (#1506)
  • Adjust database span names by replacing _ to .. db.query_compiler becomes db.query.compile. (#1502)

3.14.1

Fixes

  • Fix caching transport with attachments (#1489)
  • Revert Sentry in implicit usings (#1490)

3.14.0

Features

  • Add the delegate TransactionNameProvider to allow the name definition from Unknown transactions on ASP.NET Core (#1421)
  • SentrySDK.WithScope is now obsolete in favour of overloads of CaptureEvent, CaptureMessage, CaptureException (#1412)
  • Add Sentry to global usings when ImplicitUsings is enabled (<ImplicitUsings>true</ImplicitUsings>) (#1398)
  • The implementation of the background worker can now be changed (#1450)
  • Map reg key 528449 to net48 (#1465)
  • Improve logging for failed JSON serialization (#1473)

Fixes

  • Handle exception from crashedLastRun callback (#1328)
  • Reduced the logger noise from EF when not using Performance Monitoring (#1441)

... (truncated)

Changelog

Sourced from Sentry's changelog.

3.16.0

Features

  • Use a default value of 60 seconds if a Retry-After header is not present. (#1537)
  • Add new Protocol definitions for DebugImages and AddressMode (#1513)
  • Add HttpTransport extensibility and synchronous serialization support (#1560)
  • Add UseAsyncFileIO to Sentry options (enabled by default) (#1564)

Fixes

  • Fix event dropped by bad attachment when no logger is set. (#1557)
  • Ignore zero properties for MemoryInfo (#1531)
  • Cleanup diagnostic source (#1529)
  • Remove confusing message Successfully sent cached envelope (#1542)
  • Fix infinite loop in SentryDatabaseLogging.UseBreadcrumbs (#1543)
  • GetFromRuntimeInformation() in try-catch (#1554)
  • Make Contexts properties more thread-safe (#1571)
  • Fix PlatformNotSupportedException exception on net6.0-maccatalyst targets (#1567)
  • In ASP.Net Core, make sure that SentrySdk.LastEventId is accessible from exception handler pages (#1573)

3.15.0

Features

  • Expose ConfigureAppFrame as a public static function. (#1493)

Fixes

  • Make SentryDiagnosticSubscriber._disposableListeners thread safe (#1506)
  • Adjust database span names by replacing _ to .. db.query_compiler becomes db.query.compile. (#1502)

3.14.1

Fixes

  • Fix caching transport with attachments (#1489)
  • Revert Sentry in implicit usings (#1490)

3.14.0

Features

  • Add the delegate TransactionNameProvider to allow the name definition from Unknown transactions on ASP.NET Core (#1421)
  • SentrySDK.WithScope is now obsolete in favour of overloads of CaptureEvent, CaptureMessage, CaptureException (#1412)
  • Add Sentry to global usings when ImplicitUsings is enabled (<ImplicitUsings>true</ImplicitUsings>) (#1398)
  • The implementation of the background worker can now be changed (#1450)
  • Map reg key 528449 to net48 (#1465)
  • Improve logging for failed JSON serialization (#1473)

... (truncated)

Commits


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 2 years ago

Superseded by #55.