There are currently 2 package download options when deploying a release: using the package from the cache and always re-downloading. Both of these are useful, but each has one big downside that I think this feature would correct.

When using the package cache, Octopus will never pick up changes that were made to the same version of the package. If forcing a re-download, the package cache can quickly fill up, especially with multiple development teams (and yes, we have retention policies configured -- our packages are unfortunately quite large).

A new option that will just always re-download and keep a single package in the cache would address these issues. I am trying to solve a problem we are encountering when deploying packages from feature branches. We want to be able to have a single release (and therefore package version) per feature branch instead of having to create a new package version (and therefore release) for each new build.

Right now we are forced to re-download for every deployment, but this is quickly filling up our package cache. We could add more disk space, but at the same time, we don't care about having older versions of the package -- we don't even want to keep these packages around. For feature branches we only care about deploying the absolute latest version.