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
Dotnet tool to push nuget packages and their dependencies in the correct order to avoid missing dependencies.
I personally have fallen foul to this issue several times, specifically when dealing with dotnet workloads.
My feature request / improvement would be to either re-design the dotnet nuget push command to allow specifying a single package and the a command line flag to indicate that dependencies should also be pushed, lets say --include-dependencies.
Or, alternatively, make a separate tool / command to handle this feature.
Pushing the packages in reverse order given a dependency tree would ensure that there are no published packages that have, as of yet, unpublished dependencies and can be used as expected.
The text was updated successfully, but these errors were encountered:
@KieranFoot This isn't something handled here. The NuGet teams owns that. Please file an issue in their repo: https://github.com/NuGet/Home
Note: I cannot transfer this issue because issue transfers only happen in the same org. This repo is in the dotnet org and NuGet is in the NuGet org. So, you have to make a new issue there. Sorry.
Dotnet tool to push nuget packages and their dependencies in the correct order to avoid missing dependencies.
I personally have fallen foul to this issue several times, specifically when dealing with dotnet workloads.
My feature request / improvement would be to either re-design the
dotnet nuget push
command to allow specifying a single package and the a command line flag to indicate that dependencies should also be pushed, lets say--include-dependencies
.Or, alternatively, make a separate tool / command to handle this feature.
Pushing the packages in reverse order given a dependency tree would ensure that there are no published packages that have, as of yet, unpublished dependencies and can be used as expected.
The text was updated successfully, but these errors were encountered: