This section explains many of the concepts surrounding the Unity Package Manager functionality:
Multiple versions of each package are available, marking changes to that package along its life cycle. Every time a developer updates the package, they give it a new version number. A change in package version tells you whether it contains a breaking change (major), a new backward-compatible functionality (minor), or bug fixes only (patch), following Semantic Versioning.
To view the list of versions available for a specific package, see Finding a specific version.
There are two types of manifest files:
<project>/Packages directory. The Package Manager uses it to configure many things, including a list of dependencies for that Project, as well as any package repository to query for packages. More infomanifest.json) These store information that the Package Manager needs to locate and load the right packages, including a list of packages and versions declared as dependencies.package.json). These store information about a specific package, and a list of packages and versions that the package requires.Both files use JSON (JavaScript Object Notation) syntax.
Unity maintains a central registry of official packages that are available for distribution. A package registry stores package contents and information (metadata) on each package version. By default, all Projects use the official Unity package registry, but you can add additional registries to store and distribute private packages or stage packages in development.
The Unity Package Manager is a tool that manages the entire package system. Its primary tasks include the following:
The Unity Package Manager installs samples, tools, and Assets on a per-Project basis, rather than installing them across all Projects for a specific machine or device. It uses a read-only global cache to store downloaded package metadata and contents. Once installed, Unity treats package Assets just like any other Asset in the Project, except that these Assets are immutableYou cannot change the contents of an immutable (read-only) package. This is the opposite of mutable. Most packages are immutable, including packages downloaded from the package registry or by Git URL.
See in Glossary (read-only). You can only change Assets from Local and Embedded package sources.
States indicate where the package is in the development cycle:
The Packages window displays a tag that corresponds to some of these states. For more information, see TagsA reference word which you can assign to one or more GameObjects to help you identify GameObjects for scripting purposes. For example, you might define and “Edible” Tag for any item the player can eat in your game. More info
See in Glossary.
Sources describe where the package came from:
| Source | Description |
|---|---|
| Registry | The Unity Package Manager downloads most packages from a package registry into a global cache on your computer as you request them. These packages are immutable (read only), so you can use them in your Project, but you cannot modify them or change their package manifests. |
| Built-in | These packages allow you to enable or disable Unity features (for example, Terrain Physics, Animation, etc.). They are immutable (read only). |
| Embedded | Any package stored inside your Project folder is embedded. This source corresponds with the in development state because you typically put all the scripts, libraries, samples, and other Assets your new package needs in a folder under your Project folder when you begin development on a package. |
| Local | You can install a package from any folder on your computer (for example, if you have cloned a development repository locally). |
| Git | The Package Manager installs Git packages directly from a Git repository instead of from the registry server. |
To edit the package manifest for a package, see Inspecting packages.
The Packages window displays a tag that corresponds to some of these sources. For more information, see Tags.