search

omkelderman / osu

rhythm is just a *click* away!
https://osu.ppy.sh
MIT License
0 stars 0 forks source link

Bump Sentry from 3.9.4 to 3.14.1 #102

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps Sentry from 3.9.4 to 3.14.1.

Release notes

Sourced from Sentry's releases.

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)
  • Create CachingTransport directories in constructor to avoid DirectoryNotFoundException (#1432)
  • UnobservedTaskException is now considered as Unhandled (#1447)
  • Avoid calls the Thread.CurrentThread where possible (#1466)
  • Rename thread pool protocol keys to snake case (#1472)
  • Treat IOException as a network issue (#1476)
  • Fix incorrect sdk name in envelope header (#1474)
  • Use Trace.WriteLine for TraceDiagnosticLogger (#1475)
  • Remove Exception filters to work around Unity bug on 2019.4.35f IL2CPP (#1486)

3.13.0

Features

  • Add CaptureLastError as an extension method to the Server class on ASP.NET (#1411)
  • Add IsDynamicCode* to events (#1418)

Fixes

  • Dispose of client should only flush (#1354)

3.12.3

Fixes

  • Events no longer get dropped because of non-serializable contexts or attachments (#1401)
  • Add MemoryInfo to sentry event (#1337)

3.12.2

Fixes

  • log through serialization (#1388)
  • Attaching byte arrays to the scope no longer leads to ObjectDisposedException (#1384)
  • Operation cancel while flushing cache no longer logs an errors (#1352)
  • Dont fail for attachment read error (#1378)

... (truncated)

Changelog

Sourced from Sentry's changelog.

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)
  • Create CachingTransport directories in constructor to avoid DirectoryNotFoundException (#1432)
  • UnobservedTaskException is now considered as Unhandled (#1447)
  • Avoid calls the Thread.CurrentThread where possible (#1466)
  • Rename thread pool protocol keys to snake case (#1472)
  • Treat IOException as a network issue (#1476)
  • Fix incorrect sdk name in envelope header (#1474)
  • Use Trace.WriteLine for TraceDiagnosticLogger (#1475)
  • Remove Exception filters to work around Unity bug on 2019.4.35f IL2CPP (#1486)

3.13.0

Features

  • Add CaptureLastError as an extension method to the Server class on ASP.NET (#1411)
  • Add IsDynamicCode* to events (#1418)

Fixes

  • Dispose of client should only flush (#1354)

3.12.3

Fixes

  • Events no longer get dropped because of non-serializable contexts or attachments (#1401)
  • Add MemoryInfo to sentry event (#1337)
  • Report ThreadPool stats (#1399)

... (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 #119.