-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[release/3.0] Update dependencies from dotnet/arcade #1955
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
[release/3.0] Update dependencies from dotnet/arcade #1955
Conversation
…924.3 - Microsoft.DotNet.ApiCompat - 1.0.0-beta.19474.3 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19474.3 - Microsoft.DotNet.CodeAnalysis - 1.0.0-beta.19474.3 - Microsoft.DotNet.GenAPI - 1.0.0-beta.19474.3 - Microsoft.DotNet.Helix.Sdk - 2.0.0-beta.19474.3
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" /> | ||
<add key="dotnet-wd" value="https://dotnetfeed.blob.core.windows.net/dotnet-windowsdesktop/index.json" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need this feed, this contains WPF/WinForms transport packages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are also now automatically pushed to an azdo feed, and so should be able to be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be clear, the goal is to get down to:
- nuget.org
- Azdo feeds
I'm speculatively poking at some of this as I update these feeds now to get a head start.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah ok, sorry I was misunderstanding before and I saw the build error looking for WinForms.
I'm making similar changes in our test repo, so I'll wait on this for a final version before moving it there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the mapping between these feeds and the AzDo transport feeds? For eg, which AzDo feed gets packages from the dotnet-windowsdesktop feed?
I like the idea of human understandable NuGet.config...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- All dotnet 3 transport packages go to dotnet3-transport
- All dotnet 3 non-transport (shipping) packages go to dotnet3
- All dotnet 3.1 transport packages go to dotnet3.1-transport
- All dotnet 3.1 non-transport (shipping) packages go to dotnet3.1
- All dotnet 5 transport packages go to dotnet5-transport
- All dotnet 5 non-transport (shipping) packages go to dotnet5
- Arcade's tools go to dotnet-tools
There's no segregation between the various repos. That was largely a result of the scalability issues with the blob feed push.
@rladuca I added a subscription to the wpf test repo and updated the dependency |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
@vatsan-madhavan I think I got most necessary updates done here, but can you take a look at the remaining failures? |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Don't merge this while we are shutting down 3.0.1 |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
block until 3.0.1 finishes
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
…119.2 - Microsoft.DotNet.ApiCompat - 1.0.0-beta.19569.2 - Microsoft.DotNet.Arcade.Sdk - 1.0.0-beta.19569.2 - Microsoft.DotNet.CodeAnalysis - 1.0.0-beta.19569.2 - Microsoft.DotNet.GenAPI - 1.0.0-beta.19569.2 - Microsoft.DotNet.Helix.Sdk - 2.0.0-beta.19569.2
This reverts commit 6506e43.
@rladuca Your changes now verifying here |
This will fail again in packaging. I need to merge some more fixups. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Just push directly onto this branch as needed |
.NET Core 3.1 SDK hasn't consumed the fix for NuGet/Home#8467 yet. Suppress these warnings temporarily
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Locally "build -ci -pack" succeeds, should be good to go. |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Yay! |
Auto-Merge StatusThis pull request has not been merged because Maestro++ is waiting on the following merge policies.
|
Hello @vatsan-madhavan! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
This pull request updates the following dependencies
From https://github.com/dotnet/arcade