Switching to another package version

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 dependenciesIn the context of the Package Manager, a dependency is a specific package version (expressed in the form package_name@package_version) that a project or another package requires in order to work. Projects and packages use the dependencies attribute in their manifests to define the set of packages they require. For projects, these are considered direct dependencies; for packages, these are indirect, or transitive, dependencies. 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:

1. 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.

2. Select the installed package you want to update from the list of packages. The package information appears in the details view.

3. The lock icon () indicates that this package and version is locked to an installed feature set. To unlock the package and select another version, click the Unlock button.

   Note: The package is only temporarily unlocked. If you change to a different list context, or close either the Package Manager or the Editor, the package reverts to being locked again. However, if you switch versions when the package is unlocked (for example, with the Add package by name method), the package stays unlocked.

4. In the list of packages, click the expander icon to the left of the package name.

   

   Note: If you see the See other versions link after expanding the package, you can click it to see the list of all available versions for that package.

5. Select any version of the current package to see the details specific to that version in the details view.

   

6. Click the Update to button.

   When the progress bar finishes, 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.