Dependency availability and deprecation#

Unity Build Automation provides access to a wide range of dependencies to ensure seamless build processes across platforms and environments. We strive to make dependencies available promptly while balancing the need to remove unsupported or obsolete versions. This ensures that you can access the latest features and updates while you maintain a robust and scalable platform.

Terminology#

Unity Build Automation classifies dependencies into the following categories:

• Supported version are known to be good and are actively supported by both Build Automation and the Unity Editor.
• Available versions are provided for use but not actively maintained or recommended. Issues with these versions are addressed on a best-effort basis.
• Deprecated versions are not recommended because they are scheduled to be removed in the future. We highly encourage you to migrate to newer versions before removal.
• Experimental versions are available for testing but not yet officially supported. Use at your own risk.

Dependency deprecation#

Unity Build Automation actively manages outdated dependencies through an annual deprecation process to ensure an efficient and reliable platform. Unity Build Automation handles the deprecation of old dependencies in the following way:

1. Review phase: Every February, the UBA team evaluates all dependencies to identify those that no longer meet the support criteria.
2. Announcement: The UBA team notifies you about versions and the removal plan, and provides a minimum 60 day grace period for migration to newer versions.
3. Grace period: During the grace period, the UBA team labels deprecated dependencies to highlight the need for you to switch to supported versions.
4. Removal: After the grace period, the UBA team removes deprecated dependencies from the platform to free up resources and improve system performance and stability.