Update branding to 7.0.1

[vseanreesermsft]

No description provided.

[ghost]

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

---

null

Author:	vseanreesermsft
Assignees:	-
Labels:	area-Infrastructure-libraries
Milestone:	-

[ViktorHofer]

I don't know the specifics, but I assume that we don't want to merge this before we release 7.0?

[carlossanlop]

I don't know the specifics, but I assume that we don't want to merge this before we release 7.0?

Confirmed with Matt that we're ok merging this much earlier than usual, it was an explicit request. Also, he mentioned we normally put branding PRs out the week before release (mentioning it here for future reference).

[lewing]

@radical please take a look at the wbt failures.

[radical]

The fix for this is in #76939 , which was waiting on an updated installer with dotnet/sdk#28627 . I'm rebuilding that PR on CI.

[radical]

This needs two fixes:

1. [release/7.0][wasm] Fix Wasm.Build.Tests with stable 7.0.0 #76939, and that needs ..
2. SDK fix Return workload manifests in defined, controllable order sdk#28627, and it will be usable when the fix shows up in a new 7.0 installer.

But ..

3. the installer will be getting the fix from (2) in its release/7.0.2xx branch, IIUC
   • for which [release/7.0.2xx] Update dependencies from dotnet/sdk installer#14679 is open, and will bump to SDK's release/7.0.2xx branch
4. but the SDK PR to get the fix into release/7.0.2xx is still open - [automated] Merge branch 'release/7.0.1xx' => 'release/7.0.2xx' sdk#28668

So:

• (4) needs to merge
• then (3) needs to be updated, and merged
• then wait for a new installer (will that be on the same 7.0 channel for dotnet-install script?), and merge (1)
• Then this PR should be green

🤞

[radical]

update: I'm disabling the failing tests in #76939 , that way we won't have to wait to get a new installer build with the sdk fix, since that take some time to be available.

[carlossanlop]

update: I'm disabling the failing tests in #76939 , that way we won't have to wait to get a new installer build with the sdk fix, since that take some time to be available.

So does that mean I can consider this PR is unblocked and merge it?

[radical]

update: I'm disabling the failing tests in #76939 , that way we won't have to wait to get a new installer build with the sdk fix, since that take some time to be available.

So does that mean I can consider this PR is unblocked and merge it?

No, it still has some fixes that are needed here. So, once we merge that, this will be unblocked. The difference from earlier being that we won't have to wait to get a new installer build with the fix.

[radical]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[carlossanlop]

Merging as the CI failures look unrelated, and the timeouts are due to ongoing helix problems. We'll be monitoring the rollout builds.