-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Revert Arcade update & Workload Manifest change #71110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This reverts commit cd19e8b.
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @dotnet/runtime-infrastructure |
@danmoseley @ericstj @carlossanlop runtime will have to take an arcade update, a llvm-project update, and Jacques' change next month, plus a fix to the publish stage invoked here: runtime/eng/pipelines/official/jobs/prepare-signed-artifacts.yml Lines 48 to 57 in cd19e8b
blobArtifacts , but there are now .msi's with duplicate names. From @joeloff:
Wanted to make sure this was on your radar. The failure happens during the AzDO artifact upload task that happens at the end of that step:
|
Could someone with perms merge this? We need it to unblock the July 6.0 build |
@joeloff @wtgodbe can one of you please file an issue with the details around what needs to be done to absorb the arcade breaking change here? Please be more specific than what's already been shared above - like what component in arcade changed, why it changed, and how we need to react in dotnet/runtime to absorb that. If this information has already been shared then please copy it into an issue in the repo and assign the right labels. Thanks! |
Just saw your request for more specificity, adding that now |
Reverts #71046 & #68871, but keeps the SDK update to 6.0.106. Needed to unblock 6.0