Starting from Unity Editor version 2021.1, a package may travel through the following states during its lifecycle:
|While the package developer creates the package, it is in the “Custom” state.
When it is ready for Unity users to test it and provide feedback, a package enters the “Experimental” state. Unity does not support experimental packages and does not guarantee that experimental packages will be fully released and verified to be safe to use in production until they enter the release track.
Experimental packages either use
0 as the major portion of their version or the
-exp.# suffix on the patch portion of their version. For example,
|As soon as a package passes quality testing and doesn’t contain any experimental features or functionality (including having dependencies on experimental packages), it enters the “Pre-release” state, which is on the release track. That means that Unity fully supports it and commits to officially releasing them by the end of the current LTS cycle (for example, 2021.3) at the latest. For a list of pre-release packages available for this version, see Pre-release packages.
Unity’s release management only grants a package the “Released” status after it passes several testing stages and validation procedures, which also include checks for appropriate documentation, changelog, and license files. Packages in this state appear in the Unity Editor with the label and never use non-numeric suffixes as part of their version. For a list of released packages available for this version, see Released packages.
If the package developer updates or changes a released package, that package might return to another state depending on the severity:
|Type of change:
|Major API change that breaks an API
|Minor API change that does not break the API but affects usage
|Bug fixes, trivial changes, and documentation updates typical of patch updates
|Released (same state)
|Packages cannot be used at all in the Unity Editor versions where they have been marked “Deprecated”.
Some experimental packages are deprecated without ever reaching the release cycle track.
The Package Manager window displays a tagA 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 that corresponds to some of these states.
Note: These package states only apply to packages that Unity develops internally. Contact third-party package developers to ask about their specific processes.