Bump up dotnet version to fix CG alerts #9096
Conversation
|
Hello! I noticed that you're targeting one of our servicing branches. Please consider updating the version. |
| @@ -3,7 +3,7 @@ | |||
| "allowPrerelease": true | |||
| }, | |||
| "tools": { | |||
| "dotnet": "7.0.304", | |||
| "dotnet": "7.0.306", | |||
There was a problem hiding this comment.
Puting a comment here to block possible auto-merge.
All is good - I just do not know if we can merge to 17.7 without any tag/tell/approval process (it's just an infra stuff, so probably not a problem - but just for sure).
Taging @rainersigwald - is this considered servicing? Or can we generaly just go ahead with infra-only changes?
There was a problem hiding this comment.
Required infra for servicing is generally ok, the approval for the subsequent servicing bug includes "and the changes you are required to make to get it to build and ship" unless they're huge--and bumping to a new released SDK is not a problem. I think this is fine.
| @@ -3,7 +3,7 @@ | |||
| "allowPrerelease": true | |||
| }, | |||
| "tools": { | |||
| "dotnet": "7.0.304", | |||
| "dotnet": "7.0.306", | |||
There was a problem hiding this comment.
Required infra for servicing is generally ok, the approval for the subsequent servicing bug includes "and the changes you are required to make to get it to build and ship" unless they're huge--and bumping to a new released SDK is not a problem. I think this is fine.
Fixes #
N/A
Context
CG alerts for vs17.7 recommends the following upgrade from 7.0.7 to 7.0.9.
Changes Made
Bump up dotnet version to 7.0.306 that has runtime 7.0.9.
Testing
Notes