This PR reminded me of a hack we've had in release/6.0 for a while. Is the following still needed (or was the right Arcade fix backported)❔
https://github.com/dotnet/aspnetcore/blob/release/6.0/eng/helix/helix.proj#L59-L74

This PR reminded me of a hack we've had in release/6.0 for a while. Is the following still needed (or was the right Arcade fix backported)❔ https://github.com/dotnet/aspnetcore/blob/release/6.0/eng/helix/helix.proj#L59-L74

Probably not required for main, but should be backported so that we don't need to make the same change again when we branch for 8.0.

but should be backported so that we don't need to make the same change again

The underlying problem was not fixed in Arcade❔ I thought it was and believe we would have hit problems during the stabilization exercise if that were not the case. (The hack is present only in our release/6.0 branch.)

My question was therefore about backporting the Arcade fix to the Arcade release/6.0 branch and removing this hack. After hunting a bit, I see the only difference between FindDotNetCliPackage in release/6.0 and release/7.0 is the default feeds, everything from release/6.0 on checks both "dotnetcli" and "dotnetbuilds" feeds. I think we'd be 🆗 w/o the hack and will try an internal build removing it soon.

I'm not sure...maybe it got fixed in arcade? @MattGal does this ring a bell? https://github.com/dotnet/aspnetcore/blob/release/6.0/eng/helix/helix.proj#L59-L74

Hi @mmitche. It looks like you just commented on a closed PR. The team will most probably miss it. If you'd like to bring something important up to their attention, consider filing a new issue and add enough details to build context.

/fyi @chcosta fixed Arcade in dotnet/arcade@36d37f1 then dotnet/arcade@2580afb

Yeah, I should have looked closely at Arcade first. Sorry.