The Package Manager settings (menu: Edit > Project Settings, then the Package Manager category) let you manage your scoped registries and modify the advanced settings for your current project.
(1) The list of scoped registries currently defined for this project
(2) The details for the selected scoped registry
(B) Under the Advanced Settings section, toggle whether or not preview packagesA preview package is in development and not yet ready for production. A package in preview might be at any stage of development, from the initial stages to near completion.
See in Glossary and package dependencies are visible in the Package Manager window.
The Scoped Registries group displays a list of scoped registries already added to the current project on the left, and the details of the selected registry on the right.
For detailed information about scoped registries, including how to use and configure them with the Unity Package Manager, see the documentation on Scoped Registries.
Note: If you added a scoped registry but you don’t see it in the My Registries context or the My Registries context isn’t available at all, it might be because the package registry server you added does not implement the
/-/all endpoints, which means that it is not compatible with Unity’s Package Manager.
To add a new scoped registry to your project:
To modify an existing scoped registry:
To delete an existing scoped registry:
Enable the Enable Preview Packages setting to display preview packages in the Package Manager window. Preview packages appear with the tag in both the list view and the details view, as a reminder of which packages are in preview.
By default this setting is disabled because you should only use preview packages for testing or providing feedback to the package developer. For more information about the preview state and the lifecycle of packages, see Package states and lifecycle.
Enable the Show Dependencies setting to:
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
By default, this setting is disabled. For more information about how dependencies work with packages, see Dependency and resolution.
Scoped Registries, __Enable Preview Packages__ and __Show Dependencies__ project settings added in 2020.1 NewIn20201