-
Notifications
You must be signed in to change notification settings - Fork 447
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
[main] Update dependencies from dotnet/arcade-services #16069
[main] Update dependencies from dotnet/arcade-services #16069
Conversation
This is waiting on dotnet/arcade-services#2259 |
@MichaelSimons @mmitche this will bring in the new |
We will need to bump vstest in order for the source-build CI to pass. I expect vstest will fail as we saw earlier in #16005 (comment). |
…ild 20230410.1 Microsoft.DotNet.Darc , Microsoft.DotNet.DarcLib From Version 1.1.0-beta.23128.1 -> To Version 1.1.0-beta.23210.1
…ild 20230412.1 Microsoft.DotNet.Darc , Microsoft.DotNet.DarcLib From Version 1.1.0-beta.23128.1 -> To Version 1.1.0-beta.23212.1
10ef05b
to
6a3a2f9
Compare
@MichaelSimons I found out today that someone wrongly reverted code and reverted quite a few commits from the VMR tooling while I was away. This has been fixed and the build here is now passing. So I think we should merge this and we will be ready for the new versioning from vstest once it comes. |
If this new arcade-services version contains the versioning fix for vstest it can't be merged in without the corresponding vstest changes otherwise it will break the build. The two are coupled. If you want to break the coupling the version logic will have to be refactored to handle both vstest versioning patterns. |
I think it would only break when there would be some other But yeah, let's bump DarcLib once we are flowing the new |
We should trigger vstest into main (sdk) then, and then we can do update-dependencies on that PR. |
This pull request updates the following dependencies
From https://github.com/dotnet/arcade-services