More info See in Glossary ( package.json) store information about a specific package, and a list of packages and versions that the package requires.īoth files use JSON (JavaScript Object Notation) syntax. The manifest contains information such as the name of the package, its version, a description for users, dependencies on other packages (if any), and other details.

Package manifests Each package has a manifest, which provides information about the package to the Package Manager.

More info See in Glossary ( manifest.json) store information that the Package Manager needs to locate and load the right packages, including a list of packages and versions declared as dependencies. 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. This file must be available in the /Packages directory.

Project manifests Each Unity project has a project manifest, which acts as an entry point for the Package Manager.

To view the list of versions available for a specific package, see Finding a specific version.

A change in package version tells you whether it contains a breaking change (major), new backward-compatible functionality (minor), or bug fixes only (patch), following Semantic Versioning. Every time a developer updates the package, they give it a new version number.

Multiple versions of each package are available, marking changes to that package along its life cycle.

Manifests There are two types of manifest files: project manifest s and package manifest s.

This section explains many of the concepts surrounding the Unity Package Manager functionality:

Unity package manager