dnceng
dnceng copied to clipboard
dotnet
[main] Update dependencies from dotnet/dnceng-shared
This pull request updates the following dependencies
From https://github.com/dotnet/dnceng-shared
- Subscription: 98a111ea-ed14-41d6-b74b-08db570c450a
- Build: 20240516.1
- Date Produced: May 16, 2024 9:22:59 AM UTC
- Commit: dc6c31251059ce2d1621ddd8c7647f6d268c7045
- Branch: refs/heads/main
- Updates:
- Microsoft.DncEng.CommandLineLib: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
- Microsoft.DncEng.Configuration.Extensions: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
- Microsoft.DotNet.Authentication.Algorithms: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
- Microsoft.DotNet.GitHub.Authentication: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
- Microsoft.DotNet.Internal.DependencyInjection: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
- Microsoft.DotNet.Internal.DependencyInjection.Testing: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
- Microsoft.DotNet.Internal.Health: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
- Microsoft.DotNet.Internal.Testing.DependencyInjection.Abstractions: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
- Microsoft.DotNet.Internal.Testing.DependencyInjectionCodeGen: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
- Microsoft.DotNet.Internal.Testing.Utility: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
- Microsoft.DotNet.Kusto: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
- Microsoft.DotNet.ServiceFabric.ServiceHost: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
- Microsoft.DotNet.Services.Utility: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
- Microsoft.DotNet.Web.Authentication: from 1.1.0-beta.24224.1 to 1.1.0-beta.24266.1
![dotnet-maestro[bot] avatar](https://avatars.githubusercontent.com/in/16706?v=4 "Published by a pub.dev verified publisher"){kind=small}
can we hold a little bit on this pull request?
The changes included on this update are: https://github.com/dotnet/dnceng-shared/pull/66
This is going to be impactful for helix-services and arcade-services and we want to be super sure is not going to be impactful for this repository. @epananth is going to take a look on this pr before merging :)
