Update all samples to use the latest TFMs

[jamescrosswell]

Resolves #4584

• https://github.com/getsentry/sentry-dotnet/issues/4584

---

#skip-changelog

[codecov[bot]]

Codecov Report

:white_check_mark: All modified and coverable lines are covered by tests. :white_check_mark: Project coverage is 73.87%. Comparing base (d6d4cde) to head (3931889). :warning: Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4782      +/-   ##
==========================================
- Coverage   73.90%   73.87%   -0.03%     
==========================================
  Files         485      485              
  Lines       17682    17682              
  Branches     3494     3494              
==========================================
- Hits        13067    13063       -4     
- Misses       3758     3760       +2     
- Partials      857      859       +2     

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:rocket: New features to boost your workflow:

• :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jamescrosswell]

The error we're seeing now in CI is:

/usr/share/dotnet/packs/Microsoft.NET.Runtime.WebAssembly.Sdk/10.0.0/Sdk/WasmApp.Common.targets(853,5): error : /usr/share/dotnet/packs/Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.linux-musl-arm64/10.0.0/tools/bin/clang: line 25: /usr/share/dotnet/packs/Microsoft.NET.Runtime.Emscripten.3.1.56.Sdk.linux-musl-arm64/10.0.0/tools/bin/clang-19: not found [took 0.65s] [/__w/sentry-dotnet/sentry-dotnet/samples/Sentry.Samples.AspNetCore.Blazor.Wasm/Sentry.Samples.AspNetCore.Blazor.Wasm.csproj]

This may be related to:

• https://github.com/dotnet/runtime/issues/121975

@Flash0ver potentially we revert to net9 for the WASM sample until this is a bit more stable in .net 10?

[jamescrosswell]

Inexplicably, this commit seems to have broken the unit tests on linux-musl-x64. They don't fail... they just never complete and we can't get at the logs to work out why. 😞

Possibly the commit is entirely unrelated but, if so, I can't see any other differences between the environments between the successful and unsuccessful runs.

Commit https://github.com/getsentry/sentry-dotnet/pull/4782/commits/67226439d40a8c36e96be3fd1c307f829bbd62d8 confirms it's nothing to do with the change, but we do finally get some clues from the logs:

Error: System.IO.IOException : No space left on device : '/tmp/1d608ce7-dee1-427a-8947-daac2bd3a2b1'