[release/7.0] Update Roslyn Versions

[TanayParikh]

Update Roslyn Versions

Summary of the changes

Update the Roslyn version referenced by Razor to 4.4.0-3.22472.13.

Description

This is a routine change we complete every release to update the Roslyn version used by the Razor Runtime Compilation NuGet package. This PR uses the Roslyn version provided by @jaredpar.

The Razor Runtime Compilation NuGet package needs to reference a version of Roslyn that ships as a NuGet package. However, as Roslyn doesn't follow the runtime ship schedule, ASP.NET Core manually updates this package version.

Fixes: #39387

Customer Impact

This change ensures the version of Roslyn used by the Razor Runtime Compilation NuGet package is synchronized with the version of Roslyn used by the Razor Compiler (which ships as part of the SDK). Without synchronized Roslyn versions, we could have undefined behavior in our published packages.

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Routine version bump.

Verification

• Manual (required)
• Automated

Due to the nature of this update, CI validation is sufficient.

Packaging changes reviewed?

• Yes
• No
• N/A

References:

• Update compiler version to 3.8.0 #28125
• Update to stable Roslyn versions (#37663) #37764
• Update Roslyn versions #44072

[TanayParikh]

@dougbu do we need to do manual validation for this (beyond automated CI) given this goes through tactics? If so, how would that be done?

[dougbu]

@dougbu do we need to do manual validation for this (beyond automated CI) given this goes through tactics? If so, how would that be done?

No idea. We've made changes like this in the past and you could check git blame for them to find who did them. But I bet the answer is we relied on the CI.

[TanayParikh]

@jaredpar @mmitche @JamesNK in case you have any suggestions here

[mmitche]

CI validation seems reasonable.

[ghost]

Hi @TanayParikh. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge.

To learn more about how to prepare a servicing PR click here.

[dougbu]

@TanayParikh removed the Servicing-consider label

What's happening here❔

[ghost]

Hi @TanayParikh. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge.

To learn more about how to prepare a servicing PR click here.

[TanayParikh]

@TanayParikh removed the Servicing-consider label

What's happening here❔

Was just updating the description, so removed the label temporarily.

[TanayParikh]

We do not expect this to have any tooling related impact.