[release/8.0] Update Roslyn Versions for .NET 8

[TanayParikh]

This is a routine change we complete every release to update the Roslyn version used by the Razor Runtime Compilation NuGet package. This issue tracks making this update ahead of the .NET 8 release.

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.

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.

---

References:

• Update the Razor / Roslyn version used by runtime compilation package  #39387
• Update Roslyn versions #44072 (comment)
• [release/7.0] Update Roslyn Versions #44148
• Update compiler version to 3.8.0 #28125
• Update to stable Roslyn versions (#37663) #37764
• Update Roslyn versions #44072

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[TanayParikh]

@mkArtakMSFT I believe we'll want to hold off on this till the 8.0 RCs. If you agree, should we reset the milestone to something else?

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.