Skip to content

Bump .NET SDK to 9.0.300 #4259

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.

Sign up for GitHub

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

Closed
KnapSac wants to merge 17 commits into from
Closed

Bump .NET SDK to 9.0.300 #4259

Show file tree
Hide file tree
Changes from 5 commits
Commits
Show all changes
17 commits
Select commit Hold shift + click to select a range
b2cb9ae
Bump .NET SDK to 9.0.204
KnapSac Jun 5, 2025
a75a064
Bumped to 9.0.300
jamescrosswell Jun 6, 2025
7588936
Bumped Java dependencies
jamescrosswell Jun 6, 2025
91117b2
Merge branch 'main' into pr/4259
jamescrosswell Jun 6, 2025
673baaf
Update CHANGELOG.md
jamescrosswell Jun 6, 2025
093b9c9
Update CHANGELOG.md
KnapSac Jun 6, 2025
557dc48
Bump to latest versions of Xunit and Verify
jamescrosswell Jun 10, 2025
efdf50b
Merge branch 'main' into feat/4255/bump-sdk-version
jamescrosswell Jun 10, 2025
c97b467
Merge branch 'main' into pr/4259
jamescrosswell Jun 10, 2025
613ebf2
Bump framework targets from net462 to net48
jamescrosswell Jun 10, 2025
2d07296
Added net48 target to Sentry.Extension.Logging
jamescrosswell Jun 10, 2025
f306014
Ensure MockApplication is created on the main thread on iOS
jamescrosswell Jun 11, 2025
28ffb06
Revert "Added net48 target to Sentry.Extension.Logging"
jamescrosswell Jun 11, 2025
88516fb
Revert "Bump framework targets from net462 to net48"
jamescrosswell Jun 11, 2025
40da347
Update MockApplication.cs
jamescrosswell Jun 11, 2025
fee498d
Only run .NET Framework tests on Windows
jamescrosswell Jun 11, 2025
2d69608
Update Sentry.Testing.csproj
jamescrosswell Jun 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/actions/environment/action.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ runs:
with:
dotnet-version: |
8.0.x
9.0.203
9.0.300

- name: Install .NET Workloads
shell: bash
Expand Down
8 changes: 8 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,13 @@
# Changelog

## Unreleased

### Dependencies

- Bump the version of the .NET SDK that we use from 9.0.203 to 9.0.300 ([#4259](https://github.com/getsentry/sentry-dotnet/pull/4259))
- Note that this also required we bump various Java depdendencies (since version 9.0.300 of the Android workload requires newer versions of the these)
- See https://docs.sentry.io/platforms/dotnet/troubleshooting/#detected-package-version-outside-of-dependency-constraint if you see NU1605, NU1608 and/or NU1107 warnings after upgrading

## 5.10.0

### Features
Expand Down
4 changes: 2 additions & 2 deletions global.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"sdk": {
"version": "9.0.203",
"workloadVersion": "9.0.203",
"version": "9.0.300",
Copy link
Member

@Flash0ver Flash0ver Jun 10, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

questions

  • Will we run into the same issue again once the next patch version of feature band 3 is released?
  • If so, is this an indicator that we should we keep bumping to the latest .NET SDK in the future?
    • Would this be automatable?
      • Perhaps partially (global.json, .github/**/*.yml and CHANGELOG.md)
      • Xamarin.AndroidX.* may be not as straightforward

Copy link
Collaborator

@jamescrosswell jamescrosswell Jun 10, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will we run into the same issue again once the next patch version of feature band 3 is released?

We frequently run into issues when new versions of .NET are released. They are, thus far, each unique... some easier than others to fix. This is why we pin the version of .NET and the workloads in the repo (it means we can still make PRs and do other work while we're trying to work out how to upgrade to the latest set of "surprises").

Would this be automatable?

We definitely don't want to turn on roll forward (automatic updates) in the global.json file. Before we were pinning the workload/sdk version in global.json, I was spending 1-2 days per week, consistently, fluffing around with this stuff.

Potentially we could try to automatically create a PR that bumps to the latest version of .NET, like we do with other dependencies. That would give us a way to upgrade regularly but without breaking the main branch and halting all other work. It could be a massive time sink though. It's hard to say whether we're better off making smaller bumps once every 6-8 weeks or having long periods of focus (where we're working on the SDK instead) and then taking all the pain in one hit occasionally (like now).

I'm inclined to stick to what we're doing for the time being - there's just so much other stuff on the backlog without adding what seems to be very meta work around automating something like this.

"workloadVersion": "9.0.300",
"rollForward": "disable",
"allowPrerelease": false
}
Expand Down
11 changes: 5 additions & 6 deletions src/Sentry.Bindings.Android/Sentry.Bindings.Android.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,14 +43,13 @@
</ItemGroup>

<!-- Dependencies for AndroidMavenLibrary references
Note: versions match what was shipped with net9.0-android35.0 in:
https://www.nuget.org/packages/Microsoft.Maui.Core/9.0.0#dependencies-body-tab
Matching what was shipped in the 9.0.300 workloads to avoid NU1608 warnings
-->
<ItemGroup Condition="$(TargetFramework.StartsWith('net9'))">
<PackageReference Include="Xamarin.AndroidX.Lifecycle.Process" Version="2.8.5.1" />
<PackageReference Include="Xamarin.AndroidX.Lifecycle.Common.Java8" Version="2.8.5.1" />
<!-- MAUI 9 references this version indirectly via Xamarin.AndroidX.SwipeRefreshLayout (>= 1.1.0.24) -->
<PackageReference Include="Xamarin.AndroidX.Core" Version="1.13.1.5" />
<PackageReference Include="Xamarin.AndroidX.Lifecycle.Process" Version="2.8.7.2" />
<PackageReference Include="Xamarin.AndroidX.Lifecycle.Common.Java8" Version="2.8.7.2" />
<!-- MAUI 9 references this version indirectly via Xamarin.AndroidX.SwipeRefreshLayout -->
<PackageReference Include="Xamarin.AndroidX.Core" Version="1.15.0.2" />
<!-- We need 1.9.24 but there's no NuGet package for that version... the lowest version we can use is 2.0.0 -->
<PackageReference Include="Xamarin.Kotlin.StdLib.Jdk8" Version="2.0.0" />
</ItemGroup>
Expand Down
Loading