The Problem

From time to time, a previously approved Chocolatey Package needs to be deprecated. This could be for a number of reasons:

All versions of this package could simply be unlisted from, meaning that they could no longer be installed, however, this solution is not ideal. Any user who previously installed this package, and added it as part of an installation script, would get an error the next time that they tried to install it, and this is far from ideal.

When a package needs to be deprecated, it needs to be handled in such a way that existing users will continue to be able to use the old package id, but take advantage of the replacement package, if there is one.

The Solution

When deprecating a Chocolatey Package, the following steps should be followed:

By following this process, any existing users who try to update the old package will automatically get the new package, as it will be installed as a dependency.