Dependency availability and deprecation
Explore dependency availability and deprecation policies.
Read time 1 minuteLast updated 20 days ago
Unity Build Automation (UBA) provides access to a wide range of dependencies to ensure seamless build processes across platforms and environments. UBA makes dependencies available while removing unsupported or obsolete versions. This ensures that you can access the latest features and updates while you maintain a reliable and scalable platform.
Terminology
Unity Build Automation categorizes each dependency as follows:
Category | Description |
|---|---|
| Supported | Unity actively supports this dependency. |
| Available | Unity provides but doesn't support this dependency. Unity addresses issues with an available dependency on a best-effort basis. |
| Deprecated | Unity will remove support for this dependency in the future according to the dependency deprecation process. If you use a deprecated dependency, you must migrate to a supported dependency. |
| Experimental | Unity provides but doesn't support this dependency. Unity provides this dependency for testing purposes. Use an experimental dependency at your own risk. |
Dependency deprecation
Unity Build Automation (UBA) manages outdated dependencies through an annual deprecation process to improve platform performance and stability. The annual deprecation process has the following phases:
Phase | Description |
|---|---|
| Review phase | Every February, Unity evaluates each dependency to determine if it no longer meets its support criteria. |
| Announcement phase | Unity notifies UBA users which dependencies will be removed and the removal plan. |
| Deprecation phase | During this phase, Unity labels each dependency to be removed as deprecated. Unity provides a minimum 60 day migration period so that UBA users can migrate to a supported version. |
| Removal phase | After the migration period ends, Unity removes deprecated dependencies from UBA to free up resources and improve system performance and stability. |