ci: Fix build for the dotnet SDK and macOS runner image #636
+11
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR
This pull request contains several updates aimed at improving build reliability and compatibility across different environments. The most important changes include updating the .NET SDK version, adjusting the build configuration for .NET Framework 4.6.2, and updating the macOS runner for CI workflows.
Build and SDK configuration improvements:
global.jsonfrom9.0.300to9.0.306and setrollForwardto"disable"to ensure the build uses the specified SDK version exactly, improving build reproducibility.build/Common.propsto suppress target framework support warnings when building for .NET Framework 4.6.2, working around build failures due to certain warnings.CI workflow updates:
.github/workflows/aot-compatibility.ymlfrommacos-13tomacos-15-intelto ensure compatibility with current GitHub-hosted runners.Notes
We were getting errors in the latest 9.0.x.
9.0.112 -> https://github.com/open-feature/dotnet-sdk/actions/runs/19275629307
10.0.100 -> https://github.com/open-feature/dotnet-sdk/actions/runs/19275919896
9.0.111 -> https://github.com/open-feature/dotnet-sdk/actions/runs/19276071981
This attempts to lock it to the version 9.0.111 until we fully migrate to the SDK 10.0