Hi @jim-borden_4965 , Thanks for the feedback! We will add a note to the migration wizard via PG-3080 that clarifies that mounting the volumes are required - there's no easy way for us to tell if the user did that. Thanks, Steve

Hi @jim-borden_4965 ! I think that the "delete old versions" option of Retention Rules might be what you're looking for; that will let you keep the last "X" versions of each package. That, in combination with "unused versions" (i.e. not recently downloaded) typically cover nearly all desired retentions. As far as a "feed independent" API, that's on our list as a "nice to have", and I don't know how much of an API we'll get in the first version of ProGet 2023. The "hard part" is usually specifications/docs, so if you have any ideas we'd be very open! Currently, our idea is base it off of the upack api: https://docs.inedo.com/docs/upack-feed-api-endpoints Some things will be more difficult (or impossible?) than others. Especially for multi-platform package types like ruby, python. But TBD. Cheers, Alana

Thanks! Looking forward to that.

@atripp Thanks!

Thanks for report @jim-borden_4965 We just reviewed the Version Order Specifications, which are a bit ambiguous... but if that's what the version class does, then we may as well follow. I've fixed this as PG-2226 by comparing integer version qualifiers numerically, and it will be in the next maintenance release.

@jim-borden_4965 glad you got it working :) On Windows, you can just do an in-place upgrade of MSSQL, and not worry about database migrations. The same is probably true on Docker, and you can just upgrade container. Anyways safer to back-up. And if you haven't seen it already, here is the ProGet guidance: https://docs.inedo.com/docs/installation-backing-up-restoring

Oh, if you meant an example with embedded icon, .NET official packages do this too: https://www.nuget.org/packages/System.Collections.Immutable/7.0.0-rc.1.22426.10