nuget update -safe
will update to the latest revision (well, actually to the latest pre-release of the next minor at the moment).
This command could be enhanced to allow fine grained control on which level the update happens;
- nuget update -safe ==> update to the latest revision available
- nuget update -safe:revision ==> same behavior as the one without flag
- nuget update -safe:minor ==> update to the latest minor/revision available
- nuget update -safe:prerelease ==> update to the latest prerelease available
This would help us as we use nuget for distribution of internal components and during the build process the build server updates the dependencies to the latest available prerelease. We can not use the current version of -safe because this would prevent us from
doing parallel development of different revisions of a component.