# Upgrading ## Introduction The Gum tool and Gum NuGet packages are updated frequently. Most updates to both require no changes in your project. This page explains how to upgrade. See the subsections for upgrading between different versions to make sure you can upgrade safely. ## How to Upgrade If you are upgrading to a new version, you should read the upgrade documentation for all versions up to the version you are upgrading. For example, if you are upgrading from October 2025 to January 2026, then you should read the following documents: * November 2025 * December 2025 * January 2025 Of course, you do not need to actually upgrade to each individual month along the way, but each month may introduce changes which are important for your project. ## Upgrading the Gum Tool The Gum tool is distributed as a .zip file which is not installed on your machine. Therefore, to upgrade Gum, you need to delete the folder that contains the unzipped files, download the latest .zip file, and unzip it. The latest full release can be found in the [Setup](/gum/gum-tool/setup.md) page. The latest releases, including pre-releases, can be found on the [GitHub Releases](https://github.com/vchelaru/Gum/releases) page. All previous releases can be found on the GitHub Releases page in case you need to run an old version. ## Upgrading NuGet Packages Gum frequently upgrades the NuGet packages with enhancements and bug fixes. To upgrade your project, upgrade the latest NuGet package through Visual Studio or the command line. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.flatredball.com/gum/gum-tool/upgrading.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.