When using global.json value of rollForward should be considered
See original GitHub issueHave not set the dotnet sdk version in the workflow and have the following global.json in my project
{
"sdk": {
"version": "3.1.410",
"allowPrerelease": false,
"rollForward": "latestFeature"
}
}
At the time I am writing this there is both 3.1.411 and 3.1.412 available, but the action always uses 3.1.410
Would like the action to either use the value specified in “rollforward” by default or be able to configure the action to use the value.
Justification: Do not want to have to maintain the SDK version in two places
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Exploring the new rollForward and allowPrerelease settings in ...
In this post I explore the new rollForward and allowPrerelease settings added to the global.json file in .NET Core 3.0 and how they...
Read more >global.json overview - .NET CLI - Microsoft Learn
A version must be specified with a rollForward value, unless you're setting it to latestMajor . The default roll forward behavior is determined ......
Read more >Should I use global.json? - Alessio Franceschelli
However, when the SDK is rolling forward, this will mean a potential greater patch version will be used.
Read more >Unable to locate the .NET SDK as specified by global.json ...
1. You can get a list of all installed SDKs by running dotnet --list-sdks. – CaringDev · When you create a project, are...
Read more >Specifying .NET versions - Compositional IT
300 installed. Running dotnet --version with the above global.json gives me 5.0.408 . If I change the rollForward property to ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just updated my workflows + global.json and everything works as expected
Thx for the effort.
No problem. Let’s just agree that the versioning scheme for runtime vs. SDK vs. global.json is neither straight forward nor uniform