-
Notifications
You must be signed in to change notification settings - Fork 10k
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/5.0] Update dependencies from dotnet/efcore dotnet/runtime #28087
[release/5.0] Update dependencies from dotnet/efcore dotnet/runtime #28087
Conversation
…1122.4 Microsoft.NETCore.App.Internal , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.BrowserDebugHost.Transport From Version 5.0.1-servicing.20570.12 -> To Version 5.0.1-servicing.20572.4
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.
Auto-approving dependency update.
…123.5 Microsoft.EntityFrameworkCore.Tools , dotnet-ef , Microsoft.EntityFrameworkCore , Microsoft.EntityFrameworkCore.Design , Microsoft.EntityFrameworkCore.InMemory , Microsoft.EntityFrameworkCore.Relational , Microsoft.EntityFrameworkCore.Sqlite , Microsoft.EntityFrameworkCore.SqlServer From Version 5.0.1 -> To Version 5.0.1
…1124.5 System.IO.Pipelines , Microsoft.NETCore.App.Internal , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.BrowserDebugHost.Transport From Version 5.0.0 -> To Version 5.0.1
…1124.8 System.IO.Pipelines , Microsoft.NETCore.App.Internal , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.BrowserDebugHost.Transport From Version 5.0.0 -> To Version 5.0.1
…124.5 Microsoft.EntityFrameworkCore.Tools , dotnet-ef , Microsoft.EntityFrameworkCore , Microsoft.EntityFrameworkCore.Design , Microsoft.EntityFrameworkCore.InMemory , Microsoft.EntityFrameworkCore.Relational , Microsoft.EntityFrameworkCore.Sqlite , Microsoft.EntityFrameworkCore.SqlServer From Version 5.0.1 -> To Version 5.0.1
…1124.11 System.IO.Pipelines , System.Security.Cryptography.Pkcs , Microsoft.NETCore.App.Internal , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.BrowserDebugHost.Transport From Version 5.0.1 -> To Version 5.0.1
…1124.14 System.IO.Pipelines , System.Security.Cryptography.Pkcs , Microsoft.NETCore.App.Internal , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.BrowserDebugHost.Transport From Version 5.0.1 -> To Version 5.0.1
…1125.2 System.IO.Pipelines , System.Security.Cryptography.Pkcs , Microsoft.NETCore.App.Internal , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.BrowserDebugHost.Transport From Version 5.0.1 -> To Version 5.0.1
…125.2 Microsoft.EntityFrameworkCore.Tools , dotnet-ef , Microsoft.EntityFrameworkCore , Microsoft.EntityFrameworkCore.Design , Microsoft.EntityFrameworkCore.InMemory , Microsoft.EntityFrameworkCore.Relational , Microsoft.EntityFrameworkCore.Sqlite , Microsoft.EntityFrameworkCore.SqlServer From Version 5.0.1 -> To Version 5.0.1
…1125.9 System.IO.Pipelines , Microsoft.NETCore.App.Internal , Microsoft.Extensions.DependencyInjection , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.BrowserDebugHost.Transport , System.Security.Cryptography.Pkcs From Version 5.0.0 -> To Version 5.0.1
src/Framework/test/SharedFxTests.cs
Outdated
@@ -175,6 +175,15 @@ public void SharedFrameworkAssembliesHaveExpectedAssemblyVersions() | |||
var reader = peReader.GetMetadataReader(MetadataReaderOptions.Default); | |||
var assemblyDefinition = reader.GetAssemblyDefinition(); | |||
|
|||
if (assemblyDefinition.GetAssemblyName().Name is |
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.
@JunTaoLuo when you return, could you have a look at this change? Some of these runtime versions have been updated. It's not super clear if that's problematic (I would think not?)
I tried debugging the build failure for a bit but I'm not 100% sure what a resolution would look like. The shared runtime gets a version of M.E.DependencyInjection from the @JunTaoLuo could you look in to this? |
…125.6 Microsoft.EntityFrameworkCore.Tools , dotnet-ef , Microsoft.EntityFrameworkCore , Microsoft.EntityFrameworkCore.Design , Microsoft.EntityFrameworkCore.InMemory , Microsoft.EntityFrameworkCore.Relational , Microsoft.EntityFrameworkCore.Sqlite , Microsoft.EntityFrameworkCore.SqlServer From Version 5.0.1 -> To Version 5.0.1
…1125.12 System.IO.Pipelines , Microsoft.NETCore.App.Internal , Microsoft.Extensions.DependencyInjection , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.BrowserDebugHost.Transport , System.Security.Cryptography.Pkcs From Version 5.0.0 -> To Version 5.0.1
…1125.16 System.IO.Pipelines , Microsoft.NETCore.App.Internal , Microsoft.Extensions.DependencyInjection , Microsoft.NETCore.App.Runtime.win-x64 , Microsoft.NETCore.BrowserDebugHost.Transport , System.Security.Cryptography.Pkcs From Version 5.0.0 -> To Version 5.0.1
@pranavkm @ericstj @Pilchie the apparent issue here is likely due to assembly version changes in servicing, combined with the assemblies previously in dotnet/extensions releasing independently. dotnet/aspnetcore definitely does not "expect" the second. Background: Microsoft.AspNetCore.App.Runtime.csproj uses reference resolution to determine the transitive closure of all assemblies required in the Microsoft.AspNetCore.App shared framework. It does some tricks to avoid compilation-only references and to exclude assemblies already available in the Microsoft.NETCore.App shared framework. The first part of that isn't working completely because eng/targets/ResolveReferences.targets adds a compilation-only reference to Microsoft.Extensions.Internal.Transport.nupkg. Rather than adding more direct dependencies, suggest removing that implicit reference. I'll try that but am unlikely to pay attention… |
- Microsoft.AspNetCore.App.Runtime project does not expect compilation-only references
- slight change to 49cc13c workaround
- avoid problems with e.g. System.Extensions.DependencyInjection in 5.0.1
- assemblies with non-0.0 versions end up in Microsoft.AspNetCore.App - future-proofs these tests because more dotnet/runtime versions may change
FYI primary non-Windows error is
Likely restored |
- need the RTM-versioned packages on all platforms - we only target `net472` on Windows
This pull request updates the following dependencies
From https://github.com/dotnet/runtime
From https://github.com/dotnet/efcore