|How do you use documentation throughout your workflow? Share your experience with us by taking this survey.|
Note: The information on this page applies only to packages installed from the Unity Registry, a scoped registry, or from a local source. To update packages installed from a Git URL, you can either re-install it as a Git dependency using a new revision or re-install it from the Unity Registry. For more information about how to specify revisions with Git dependenciesThe Package Manager retrieves Git dependencies from a Git repository directly rather than from a package registry. Git dependencies use a Git URL reference instead of a version, and there’s no guarantee about the package quality, stability, validity, or even whether the version stated in its
package.json file respects Semantic Versioning rules with regards to officially published releases of this package. More info
See in Glossary, see Targeting a specific revision.
You can update a package while in the In Project, Unity Registry, or My Registries context:
Open the Package Manager window and select In Project from the PackagesPackages are collections of assets to be shared and re-used in Unity. The Unity Package Manager (UPM) can display, add, and remove packages from your project. These packages are native to the Unity Package Manager and provide a fundamental method of delivering Unity functionality. However, the Unity Package Manager can also display Asset Store packages that you downloaded from the Asset Store. More info
See in Glossary drop-down menu.
An arrow indicator appears next to any packages that have updates available.
In the list of packages, click the expander icon to the left of the package name.
If there are updates available, the latest version and verified version appear along with the See all versions link.
Click See all versions to see the list of all available versions for that package.
You can select any of these versions for the current package and see the details specific to that version in the details view.
Click the Update to button.
When the progress bar finishes, the new package version information appears in the details view, and any new functionality is immediately available.
Note: If you switch to an older version of a package, you might have to run the API Updater on the package contents.