New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to latest 6.0 .Net Runtime/SDK #10229
Conversation
Thank you |
"sdk": { | ||
"version": "6.0.401", | ||
"rollForward": "feature" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The update script should be updated to fix the formatting, to decrease noise in the changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See https://stackoverflow.com/questions/33145377/how-to-change-tab-width-when-converting-to-json-in-powershell. I didn't want to add another dependancy like Newtonsoft module and the hack with string manipulation feels too hacky. The json is valid and frankly managed by script. Why I didn't do that.
Should we cherry-pick this to the release/4.0 branch, too? |
(cherry picked from commit 1cc4173)
Done, thank you for the reminder. |
PowerShell handling of JSON is... imperfect.
|
Proposed changes
.\scripts\Update-DotnetVersion.ps1
git diff -U0 -w --no-color --ignore-blank-lines | git apply --cached --ignore-whitespace --unidiff-zero --
to stage non whitespace changes. This time I also staged whitespace on the global.json file to make it not have much of a diff in the future. This prevents staging the blank line removal in the RepoLayout.props file that this script generates.Test methodology
Test environment(s)
Merge strategy
I agree that the maintainer squash merge this PR (if the commit message is clear).
✒️ I contribute this code under The Developer Certificate of Origin.