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.
(A) Under the Advanced Settings section, toggle whether or not pre-release packages and package dependencies are visible in the Package Manager window.
(B) Add, modify, and remove scoped registries for your project under the Scoped Registries group, which contains the following areas:
(1) The list of scoped registries currently defined for this project
(2) The details for the selected scoped registry
Use the Advanced Settings group to toggle the Enable Pre-release Packages and Show Dependencies settings for your current project.
Enable the Enable Pre-release Packages setting to display pre-release packages in the Package Manager window. Pre-release packages appear with the tag in the list view and the tag in the details view, as a reminder of which packages will be released with the LTS version of the Editor.
Warning:
By default this setting is disabled because pre-release packages are still being verified as stable enough for production, but are not fully released yet. For more information about 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 infoNote:
By default, this setting is disabled. For more information about how dependencies work with packages, see Dependency and resolution.
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 /-/v1/search
or /-/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: