Skip to content
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/aspnetcore #5520

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

dotnet-maestro[bot]
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Oct 15, 2024

Coherency update: Failed to perform coherency update for one or more dependencies. Please review the GitHub checks or run darc update-dependencies --coherency-only locally against darc-main-03eb2329-688a-4bf6-9b43-c1d0e34ca703 for more information.

…0241014.7

Microsoft.AspNetCore.App.Ref , Microsoft.AspNetCore.App.Runtime.win-x64 , Microsoft.AspNetCore.Mvc.Testing , Microsoft.AspNetCore.TestHost , Microsoft.Extensions.Caching.SqlServer , Microsoft.Extensions.Caching.StackExchangeRedis , Microsoft.Extensions.Diagnostics.HealthChecks , Microsoft.Extensions.Http.Polly , Microsoft.Extensions.ObjectPool
 From Version 9.0.0-rc.2.24474.3 -> To Version 9.0.0-rtm.24514.7
@dotnet-maestro dotnet-maestro bot requested a review from a team as a code owner October 15, 2024 12:45
@BrennanConroy
Copy link
Member

@joperezr I suspect 92ae19e messed up dependency updates. I believe CoherentParentDependency should cause Microsoft.Extensions.* etc. dependencies to be updated as part of this PR, but maybe the internal uri is messing things up?

@joperezr
Copy link
Member

You are correct that this should be updating both aspnetcore and runtime dependencies but don't see why that would be broken here. darc is able to reason about intarnal vs public uri mappings, so not sure, we may have to ping core eng for help. In the meantime we can just make the updates manually, but since RC's and GA builds are flowing internally anyway then perhaps it's not worth our time to try to fix these as we'll have to manually flow the bits internally anyway

…0241015.19

Microsoft.AspNetCore.App.Ref , Microsoft.AspNetCore.App.Runtime.win-x64 , Microsoft.AspNetCore.Mvc.Testing , Microsoft.AspNetCore.TestHost , Microsoft.Extensions.Caching.SqlServer , Microsoft.Extensions.Caching.StackExchangeRedis , Microsoft.Extensions.Diagnostics.HealthChecks , Microsoft.Extensions.Http.Polly , Microsoft.Extensions.ObjectPool
 From Version 9.0.0-rtm.24514.7 -> To Version 9.0.0
…0241016.19

Microsoft.AspNetCore.App.Ref , Microsoft.AspNetCore.App.Runtime.win-x64 , Microsoft.AspNetCore.Mvc.Testing , Microsoft.AspNetCore.TestHost , Microsoft.Extensions.Caching.SqlServer , Microsoft.Extensions.Caching.StackExchangeRedis , Microsoft.Extensions.Diagnostics.HealthChecks , Microsoft.Extensions.Http.Polly , Microsoft.Extensions.ObjectPool
 From Version 9.0.0 -> To Version 9.0.0
…0241017.3

Microsoft.AspNetCore.App.Ref , Microsoft.AspNetCore.App.Runtime.win-x64 , Microsoft.AspNetCore.Mvc.Testing , Microsoft.AspNetCore.TestHost , Microsoft.Extensions.Caching.SqlServer , Microsoft.Extensions.Caching.StackExchangeRedis , Microsoft.Extensions.Diagnostics.HealthChecks , Microsoft.Extensions.Http.Polly , Microsoft.Extensions.ObjectPool
 From Version 9.0.0 -> To Version 9.0.0
@captainsafia
Copy link
Member

@joperezr @BrennanConroy I just hopped onto my build-ops rotation. What's the recommended action here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants