Skip to content

chore(deps): update Dotnet SDK to v4.10.0 #51

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

Merged
merged 1 commit into from
Aug 15, 2024

Conversation

github-actions[bot]
Copy link
Contributor

Bumps dependencies/Sentry.properties from 4.9.0 to 4.10.0.

Auto-generated by a dependency updater.

Changelog

4.10.0

Features

  • Users can now automatically create releases and associated commits via sentry-cli and MSBuild properties (#3462)
  • Sentry.AspNetCore.Blazor.WebAssembly now targets .NET 8 specifically, allowing for proper dependency resolution (#3501)

Fixes

  • When targeting WPF, WinForms or Avalonia with PublishAot enabled, the SDK no longers throws a DllNotFoundException trying to initialize sentry-native (#3411)
    Unable to load DLL sentry-native or one of its dependencies
  • On mobile devices, the SDK no longer throws a FormatException when trying to report native events (#3485)
  • Race condition in SentryMessageHandler (#3477)
  • Decrease runtime diagnostics circular buffer when profiling, reducing memory usage (#3491)
  • The InstallationId is now resolved only once per application execution and any issues are logged as warnings instead of errors (#3529)
  • DisplayInfo now captured correctly on iOS and Mac Catalyst on non-UI threads (#3521)

Dependencies

@bruno-garcia bruno-garcia force-pushed the deps/dependencies/Sentry.properties branch from bda4669 to 782ed46 Compare August 15, 2024 03:01
@vaind vaind merged commit 968a8ae into main Aug 15, 2024
13 checks passed
@vaind vaind deleted the deps/dependencies/Sentry.properties branch August 15, 2024 07:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants