Upgrading to Latest 2.0.0 and 6.0.0 of Chocolatey Products

We have provided a lot of information on upgrading to the latest versions of the Chocolatey products and wanted to ensure it's all in one place. There is [support available if you have any questions](https://docs.chocolatey.org/en-us/guides/upgrading-to-chocolatey-v2-v6#what-should-you-do-if-you-have-questions), or you can post your issue or ask your question in [this discussion](https://github.com/chocolatey/choco/discussions/3173).

It's important to highlight some important information before we start:

* **Ensure that any automations, scripts, or integrations are not installing the latest version of Chocolatey products.** This applies to any software and is best practice. Major version releases will likely include breaking changes and if you automatically upgrade without testing, you are going to have issues now, or in the future.
* **Test the upgrade of Chocolatey products on a test sample of computers, before deploying further.** This is best practice for any software. Please see our [Support Lifecycle](https://docs.chocolatey.org/en-us/chocolatey-components-dependencies-and-support-lifecycle) and **do not upgrade if you have any issues or concerns.** Reach out for [support](https://docs.chocolatey.org/en-us/guides/upgrading-to-chocolatey-v2-v6#what-should-you-do-if-you-have-questions).
* **You must read the [important information you should know before upgrading](https://docs.chocolatey.org/en-us/guides/upgrading-to-chocolatey-v2-v6#important-information-you-should-know-before-upgrading-your-chocolatey-products).** Ensure you are aware of the [new .NET 4.8 framework requirement](https://docs.chocolatey.org/en-us/guides/upgrading-to-chocolatey-v2-v6#net-framework-4.8-required) and how it impacts how you use Chocolatey CLI.
* **Performance, particularly of the `outdated` command, is not where we want it to be.**

We have the resource below to help you with the decision to upgrade, and the upgrade itself.

* [Blog post announcement](https://blog.chocolatey.org/2023/05/announcing-chocolatey-products-2-and-6/)
* [Upgrade guide](https://docs.chocolatey.org/en-us/guides/upgrading-to-chocolatey-v2-v6)
* [Highlight of changes](https://docs.chocolatey.org/en-us/choco/new-in-v2)
* [Release Livestream ](https://discord.com/events/778552361454141460/1113133304007381002)

For detailed information on the changes for each product, see the release notes:

* [Chocolatey CLI](https://docs.chocolatey.org/en-us/choco/release-notes#may-31-2023)
* [Chocolatey Licensed Extension](https://docs.chocolatey.org/en-us/licensed-extension/release-notes#may-31-2023)
* [Chocolatey Agent](https://docs.chocolatey.org/en-us/agent/release-notes#may-31-2023)
* [Chocolatey GUI](https://docs.chocolatey.org/en-us/chocolatey-gui/release-notes#may-31-2023)
* [Chocolatey GUI Licensed Extension](https://docs.chocolatey.org/en-us/chocolatey-gui-licensed-extension/release-notes#may-31-2023)

Finally, if you use third-party integrations with Chocolatey products, we have created issues for [these integrations](https://docs.chocolatey.org/en-us/features/integrations) (note that only Chef supports side-by-side installs):

* [Ansible](https://github.com/chocolatey/chocolatey-ansible/) supports the new Chocolatey product versions.
* [Puppet](https://github.com/puppetlabs/puppetlabs-chocolatey/issues/321)
* [Octopus Deploy](https://github.com/OctopusDeploy/Library/issues/1358)
* [Otter](https://github.com/Inedo/inedox-chocolatey/issues/22)
* [PSDeploy](https://github.com/RamblingCookieMonster/PSDeploy/issues/135)
* [SaltStack](https://github.com/saltstack/salt/issues/64271)
* [Chef](https://github.com/chef/chef/issues/13751) (and an issue about [side-by-side installed being removed](https://github.com/chef/chef/issues/13368))

Start by reviewing the linked upgrade guide, announcement, highlight of changes, and product release notes. The issue does not identify a file or a specific documentation change, so a contributor would first need the maintainers to define what should be updated and how completion will be verified.

Written by the indexing model from the issue text.