GitHub Actions fail on `master` for Windows and Linux builds

[mikkelbu]

The builds are failing on master as our global.json expects version "8.0.100" for the SDK and the build agents - for Windows and Linux - now install 8.0.101. I guess we would like to update the global.json at some point, but I'm unsure if we can expect all contributors to be updating immediately when a new version comes out, so perhaps we should initially just supply a more specific version than 8.0.x in setup-dotnet and then bump the global.json and the CI agents later ?

[SeanKilleen]

@mikkelbu can we use rollForward in the global.json?.https://learn.microsoft.com/en-us/dotnet/core/tools/global-json

[manfred-brands]

We could use rollForward to latest patch only and change the .net install to 8.0.1xx. That way we use bugfixes but not new possibly incompatible features.

[OsirisTerje]

I agree , Roll forward for patches should do it.

[OsirisTerje]

@mikkelbu The global.json still points to 8.0.100, and I see the latest builds are all green https://github.com/nunit/nunit/actions/runs/7616486979
Where do you see they're red ?

[manfred-brands]

@OsirisTerje You merged the PR that uses global.json to download that particular version, so the issue is sort of addressed with my caveat that we now assume github pre-installs .NET 6.0

[OsirisTerje]

@manfred-brands Yes, we do. It is not ideal, but when it breaks we will know. When we bind it to the global.json we will only have one, right. So the question is if that is ok or not. I am in doubt here.