Update SDK

[MackinnonBuck]

No description provided.

[ghost]

Hey @dotnet/aspnet-build, looks like this PR is something you want to take a look at.

[mthalman]

It's because the SDK being used for the build still points to the old 8.0 P7 version in its BundledVersions.props file causing this version to be loaded for net8.0. For now, this can be added to https://github.com/dotnet/aspnetcore/blob/main/eng/SourceBuildPrebuiltBaseline.xml as an allowed prebuilt.

[RussKie]

Thank you @mthalman for the suggestion.

[eerhardt]

@MackinnonBuck @javiercn @mkArtakMSFT - It looks like the test failures are in the Components E2E tests. Can someone from the Blazor team take a look?

[eerhardt]

@SteveSandersonMS @halter73 - any chance one of you could look at the failing tests here?

[MackinnonBuck]

It looks like at least part of the problem is that interactively-rendered <script> elements no longer execute. Some of our tests were depending on that working. I haven't been able to track down the reason just yet.

[MackinnonBuck]

Alright, hopefully this works :)

[SteveSandersonMS]

@MackinnonBuck I was expecting changes in release/8.0 to flow into main automatically. Do you know if that's incorrect? If so there are a lot of 8.0 changes that need to get ported to main.

[MackinnonBuck]

I was expecting changes in release/8.0 to flow into main automatically

@SteveSandersonMS I believe that's correct. I just opted to cherry-pick one of your commits from #51059 in order to unblock this SDK update without waiting for the next merge PR. However, I do see that there hasn't been an active release/8.0 => main merge PR in two weeks...

@wtgodbe, do you know why this is the case?

[wtgodbe]

I disabled automatic merges from 8.0 to main after RC2 locked down, I sent a couple emails to the team about it. I'm doing periodic mop-up merges between now and RTM to get any changes that got missed.