[main] Update dependencies from dotnet/runtime #24583
Conversation
![dotnet-maestro[bot]](https://avatars.githubusercontent.com/in/16706?s=60&v=4){kind=small}
…0405.1 Microsoft.Extensions.Logging , Microsoft.Extensions.HostFactoryResolver.Sources , Microsoft.Extensions.Caching.Memory , Microsoft.Extensions.Configuration , Microsoft.Extensions.Configuration.Abstractions , Microsoft.Extensions.Configuration.EnvironmentVariables , Microsoft.Extensions.Configuration.Json , Microsoft.Extensions.DependencyInjection , Microsoft.Extensions.DependencyModel , System.Diagnostics.DiagnosticSource , System.Collections.Immutable , System.ComponentModel.Annotations From Version 6.0.0-preview.4.21178.6 -> To Version 6.0.0-preview.4.21205.1
ghost
added
|
@ajcvickers @smitpatel I'm seeing failures with the |
|
Based on my tiny research It seems that dotnet/runtime#50463 introduced a (breaking) change that once scope is disposed it cannot be used again which this particular test does. Either test should be updated or removed. |
|
Thanks @smitpatel! I've created #24590 and skipped the test (0dcc9be) for now. Could I please get a PR approval if that looks good to you? |
|
Hello @TanayParikh! 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 (
|
|
Apologies, while this PR appears ready to be merged, I've been configured to only merge when all checks have explicitly passed. The following integrations have not reported any progress on their checks and are blocking auto-merge:
These integrations are possibly never going to report a check, and unblocking auto-merge likely requires a human being to update my configuration to exempt these integrations from requiring a passing check. Give feedback on thisFrom the bot dev teamWe've tried to tune the bot such that it posts a comment like this only when auto-merge is blocked for exceptional, non-intuitive reasons. When the bot's auto-merge capability is properly configured, auto-merge should operate as you would intuitively expect and you should not see any spurious comments. Please reach out to us at [email protected] to provide feedback if you believe you're seeing this comment appear spuriously. Please note that we usually are unable to update your bot configuration on your team's behalf, but we're happy to help you identify your bot admin. |
ghost
merged commit 
This pull request updates the following dependencies
From https://github.com/dotnet/runtime