You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
aspnetcore-runtimepackagestore is forcibly updated and gets a package fix version, e.g. 2.1.0.20180531
dotnetcore-windowshosting is also forcibly updated and gets the same package fix version, e.g. 2.1.0.20180531
dotnetcore-windowshosting AU script runs au_GetLatest from aspnetcore-runtimepackagestore to determine the appropriate dependency version to use
au_GetLatest from aspnetcore-runtimepackagestore correctly returns 2.1.0, because that is the actual latest released software version
result: dotnetcore-windowshosting 2.1.0.20180531 depends on aspnetcore-runtimepackagestore 2.1.0 instead of 2.1.0.20180531
I believe the correct way to handle this would be to:
in UpdateAll.ps1, ensure aspnetcore-runtimepackagestore is processed earlier than dotnetcore-windowshosting,
in dotnetcore-windowshosting AU script, obtain the latest aspnetcore-runtimepackagestore version from the aspnetcore-runtimepackagestore stream json state file instead of invoking au_GetLatest from that package.
The text was updated successfully, but these errors were encountered:
Scenario:
2.1.0.20180531
2.1.0.20180531
2.1.0
, because that is the actual latest released software version2.1.0.20180531
depends on aspnetcore-runtimepackagestore2.1.0
instead of2.1.0.20180531
I believe the correct way to handle this would be to:
The text was updated successfully, but these errors were encountered: