Repository navigation
Fix casing for TargetFrameworks property in Build.Publish.cs - #9360
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the NUKE build publish target to use the correct .NET target framework moniker casing when passing TargetFrameworks into MSBuild during AOT publishing.
Changes:
- Change
TargetFrameworksproperty value fromNET10.0tonet10.0in.build/Build.Publish.cs.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This was referenced May 1, 2026
Open
This was referenced May 9, 2026
This was referenced May 16, 2026
This was referenced May 18, 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
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 of the changes (Less than 80 chars)
Build.Publish.cs.