Repackaging A Pre-Release Package For A Prior Standard Release Package

[Frueber]

They will be limitations to what we can re-package, especially if we've already moved on to newer standard release versions of the library. For example, if we were to re-package 1.0.0-pr.2.2.2 and the CsProj file shows history of a newer 2.0.0-pr.1.0.0 we should be able to reflect a version 1.0.0 as long as it doesn't already exist.
It can be noted that this might not be a likely scenario. Going back to an older pre-release version and making it a standard release will always have its limitations and developers should do their best to guide away from the overlap by staying on top of when to promote, communicating with their contributors and consumers, and inevitably considering some pre-release packages as forever a pre-release and the support provided in it would be in future release versions.

Re-Packageable Example

Before Re-Package

1.0.0-pr.2.2.2 Old pre-release version that we can promote.
2.0.0-pr.1.0.0 A newer pre-release version 

Attempt to re-package 1.0.0-pr.2.2.2.

After Re-Package

1.0.0-pr.2.2.2 Old pre-release version that we can promote.
1.0.0 Release version from 1.0.0-pr.2.2.2. Old pre-release version that we can promote.
2.0.0-pr.1.0.0 A newer pre-release version 

Not Re-Packageable Example

Before Re-Package

1.0.0-pr.2.2.2 Old pre-release version that we can promote.
1.0.0 Release version from 1.0.0-pr.2.2.2. Old pre-release version that we can promote.
2.0.0-pr.1.0.0 A newer pre-release version 

Attempt to re-package 1.0.0-pr.2.2.2.

Re-Package Attempt Result

The corresponding standard release version 1.0.0 already exists. Can not re-package.