Update global.json to 10.0 sdk

[BrennanConroy]

No description provided.

[wtgodbe]

Looks like we need to add the new prebuilt until https://github.com/dotnet/sdk/blob/c2257cb5b1617ddf9b2654547fa221f91b00c4e0/src/Installer/redist-installer/targets/GenerateBundledVersions.targets#L88-L90 gets updated

[BrennanConroy]

How do we do that

[wtgodbe]

Just need to add Microsoft.NETCore.App.Ref.9.0.0-preview.7.24405.7 to https://github.com/dotnet/aspnetcore/blob/main/eng/SourceBuildPrebuiltBaseline.xml, there's a link to the docs next to the failure in the build logs. SourceBuild uploads a generated new manifest to the build artifacts as a convenience

[MackinnonBuck]

Components E2E failures were due to the M.A.C.CustomElements project including the JS initializer module too late in the build process. This should now be fixed.

[halter73]

Does this indicate there was a breaking change in the SDK? Could this break other targets currently configured to run before ResolveJSModuleStaticWebAssets like GenerateUnoWasmAssets, because they're now run too late? That's all I found using grep.app, but that only indexes a small fraction of Blazor code.

[MackinnonBuck]

Does this indicate there was a breaking change in the SDK?

Yeah, it's possible. I looked through the most recent changes to the StaticWebAssets SDK and didn't see anything that should impact the build order. Maybe we got lucky in the past that this target ran in time, and something else was recently introduced that indirectly changed the target execution order.

[MackinnonBuck]

cc @javiercn in case you have any thoughts or ideas about this

[javiercn]

@MackinnonBuck I don't remember why the integration for this package was done this way.

Normally we tell people to depend on AssignTargetPaths which runs before our pipeline.

[BrennanConroy]

Can we merge this then?