Similar to #645.
We currently publish all (currently 16) NuGet packages, which are versioned together, in a single publish step. In some cases, this has caused reentrancy problems, when NuGet.org was temporary unavailable or unresponsive (see #571 and #619).
"Exploding" our package hierarchy (mind dependencies it publish in the correct order) could solve this problem without the current "hack" we have employed for dotnet/nuget.
TODOs
- Provide the algorithm of gathering all packages to publish (keep the order in mind for partial publish / resume / retry)
- either as a small script (e.g. PowerShell or file-based app (if available)), max 30 lines
- or textually to be built into craft
- @Flash0ver
Similar to #645.
We currently publish all (currently 16) NuGet packages, which are versioned together, in a single publish step. In some cases, this has caused reentrancy problems, when NuGet.org was temporary unavailable or unresponsive (see #571 and #619).
"Exploding" our package hierarchy (mind dependencies it publish in the correct order) could solve this problem without the current "hack" we have employed for dotnet/nuget.
TODOs