[CI] Fix analyzer failures by restricting SDK rollForward policy#4457
Merged
[CI] Fix analyzer failures by restricting SDK rollForward policy#4457
Conversation
The GitHub runner image was updated to include .NET SDK 10.1.x, and latestMajor rollForward caused FSharp.Core 10.1.201 to be resolved instead of 10.0.x. This broke the fsharp-analyzers tool (which requires FSharp.Core = 10.0.101) causing silent crashes and missing SARIF reports. latestFeature stays within 10.0.x while still allowing feature band updates. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
latestFeature still rolled forward to SDK 10.0.201, which ships FSharp.Core 10.1.201 (decoupled from SDK version). latestPatch restricts to the 10.0.1xx band where FSharp.Core is 10.0.x. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
dbrattli
changed the title
ncave
approved these changes
Mar 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
"rollForward": "latestMajor"inglobal.json, the runtime used this newer SDK which ships FSharp.Core 10.1.201 (FSharp.Core version is decoupled from SDK version)fsharp-analyzerstool (v0.36.0) requiresFSharp.Core = 10.0.101, and the 10.0→10.1 jump causes it to silently crash at runtime (the MSBuild target hasContinueOnError=trueandIgnoreExitCode=true)upload-sarifstep fails withPath does not exist: src/reportsrollForwardfrom"latestMajor"to"latestPatch"— this stays within the 10.0.1xx feature band where FSharp.Core remains at 10.0.x. (latestFeaturewas also tried but still rolled forward to SDK 10.0.201 which ships FSharp.Core 10.1.201)Test plan
analyzersCI jobs pass on this PR🤖 Generated with Claude Code