Repository navigation
Emit dotnet-version from GitHubActionsAttribute (SetupDotNetVersions) - #699
Draft
ChrisonSimtian wants to merge 2 commits into
Draft
ChrisonSimtian wants to merge 2 commits into
ChrisonSimtian wants to merge 2 commits into
Conversation
Add SetupDotNetVersions to GitHubActionsAttribute and GitHubActionsRunStep. When non-empty the generated step writes dotnet-version (one value inline, several as a block) instead of global-json-file. Empty keeps the existing output unchanged. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
ChrisonSimtian
force-pushed
the
hotfix/v10.4.1-setup-dotnet-version
branch
from
October 5, 2026 00:58
957ab75 to
fc63964
Compare
This branch has not been deployed
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
1 participant
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.
What
GitHubActionsAttributegets aSetupDotNetVersions(string[]) property. When non-empty, the generatedactions/setup-dotnetstep emitsdotnet-version(one value inline, several as a|block) and noglobal-json-file. Empty (the default) leaves the output byte for byte as before.Why
The step always emitted
global-json-file: global.json, resolved from the repo root. Repos withglobal.jsonin a subfolder either fail or need a root copy just for Fallout. Pinning an exact SDK also stops self-hosted runners that share one dotnet directory from racing to install every new patch at once ("file already exists" mid-extract on concurrent jobs).Tests
Two new generation specs (
setup-dotnet-version,setup-dotnet-versions). The existing verified workflows are untouched and still pass, which covers the unchanged default. Docs: new "Pinning the .NET SDK" section indocs/website/05-cicd/github-actions.md.Branch
Targets
develop. The branch was cut frommain, so it carries only these two commits; it can be cherry-picked onto the 10.4.x line for the patch release.