Hi @scampbell_8969,
ProGet does not have this feature; we've thought about it after some customer discussions in years past, but I don't think anyone's asked about it until now. And it wasn't the right solution for those customers.
We concluded it would be kind of complicated to document / configure / troubleshoot, especially once we got into the details and specifics. Here's some of those:
A new version could be unwanted, especially after the "Moq Meltdown" from last year
Patch versions are probably okay, but new major versions should still be vetted
Licenses can (and do) change between versions
New versions It's also a vector for malicious update attacks
Some kind of filter would be needed to select package for auto-promotion
Very few packages get frequent updates, so this doesn't seem like it's solving a big problem
Instead we created a "latest version" compliance flag that allows you to flag packages that aren't the latest patch version. We'll see if that's popular.
Thanks,
Alana