global.json: relax rollForward policy to fix CI #783
Merged
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.
Recent fix [1] for our scheduled CI build didn't last long. Suddenly the "Restore tools" step (
dotnet tool restore) started failing in Linux because the GithubActions agent's dotnet version was apparently upgraded from 9.0.306 to 9.0.307. Given this, the most sensible approach to fix this is revisit our RollForward policy, which was disabled in a recent PR [2] because of apparent issues when upgrading our docs generation.That issue seems to not be happenning anymore because our CIs are green even when we upgraded to a .NET version newer than 9.0.300 (maybe thanks to our Fornax dependency upgrade?), so it seems safe to restore to a "Minor" setting here.
[1] #780
[2] #736