Use global.json for SDK version in CI workflows#193
Draft
dkropachev wants to merge 1 commit into
Draft
Conversation
CI jobs were using a runner-preinstalled .NET SDK 10.0.x instead of the intended 9.0.x because the setup-dotnet action only installed the target framework runtime without the SDK version specified in global.json. This caused build race conditions (MSB4018 GenerateDepsFile IOException) due to behavioral differences in the newer SDK. Switch all workflows to use global-json-file parameter so the SDK version is always read from global.json, keeping a single source of truth.
sylwiaszunejko
requested changes
Feb 23, 2026
sylwiaszunejko
left a comment
There was a problem hiding this comment.
CI fails due to no global.json file
Collaborator
Author
Sorry, should not have tagged you, it is not ready yet. |
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
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
setup-dotnetonly installed the target framework runtime without matching the SDK version fromglobal.jsonMSB4018 GenerateDepsFile IOExceptiononScyllaDB.deps.json) due to parallel build race conditions in the newer SDKsetup-dotnetsteps acrossmain.ymlandpublish.ymlto useglobal-json-file: global.json, keeping a single source of truth for SDK versionTest plan
integration-tests (PRIOR, net6, 6.0.x)job that was failing)