Starting from Unity Editor version 2021.1, a package may travel through the following states during its lifecycle:
Birth (A) | 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, mypackage@0.1.2 or mypackage@1.2.3-exp.1 . |
|||
Release track | 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 ![]() If the package developer updates or changes a released package, that package might return to another state depending on the severity: |
|||
Type of change: | New state: | Version bump: | ||
(B) | Major API change that breaks an API | Experimental |
1.2.3 => 2.0.0-exp
|
|
(C) | Minor API change that does not break the API but affects usage | Pre-release |
1.2.3 => 1.3.0-pre
|
|
(D) | Bug fixes, trivial changes, and documentation updates typical of patch updates | Released (same state) |
1.2.3 => 1.2.4
|
|
Death (E) | Packages that reach their end of life are no longer supported in Editors where they’re marked “Deprecated”. Packages in that state shouldn’t be used as they might be nonfunctional or unsafe to use. Specific package versions can also be individually marked as deprecated across all Editors. Unity usually applies this designation when they discover a critical issue in a specific version of a package that hasn’t yet reached its end of life. Custom package authors can also apply this designation based on their own deprecation flow. Some experimental packages go directly to the deprecated state without passing through the release cycle track. |
The Package Manager window displays a label 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.
部分高级或支持包在 Package Manager 窗口中不再可见 2020.1 NewIn20201 New package lifecycle (V2) for the Package Manager 2021.1 NewIn20211
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.
您访问任何网站时,网站都可能在您的浏览器上存储或检索信息,大多数是以 Cookie 的形式进行。此信息可能与您、您的偏好、您的设备相关,或者该信息被用于使网站按照您期望的方式工作。这些信息通常不会直接识别您,但它可为您提供更多个性化的 Web 体验。您可以选择不允许使用某些类型的 Cookie。单击不同类别标题以了解更多信息并更改默认设置。但是,您应该知道,阻止某些类型的 Cookie 可能会影响您的网站体验和我们能够提供的服务。
更多信息
这些 Cookie 允许提供增强功能和个性化内容,如视频和实时聊天。我们或我们已将其服务添加至我们页面上的第三方提供者可以进行设置。如果您不允许使用这些 Cookie,则可能无法实现部分或全部功能的正常工作。
使用 Cookie,我们可以计算访问量和流量来源,以便衡量和提高我们网站的性能。Cookie 有助于我们了解哪些页面最受欢迎、哪些最不受欢迎,并查看访问者如何浏览网站。这些 Cookie 收集的所有信息都聚合在一起,因此是匿名处理方式。如果您不允许使用这些 Cookie,我们将不知道您何时访问了我们的网站。
这些 Cookie 由广告合作伙伴通过我们的网站进行设置。这些公司可能利用 Cookie 构建您的兴趣分布图并向您展示其他网站上的相关广告。它们只需识别您的浏览器和设备便可发挥作用。如果您不允许使用这些 Cookie,您将不能体验不同网站上的定向广告。
网站运行离不开这些 Cookie 且您不能在系统中将其关闭。通常仅根据您所做出的操作(即服务请求)来设置这些 Cookie,如设置隐私偏好、登录或填充表格。您可以将您的浏览器设置为阻止或向您提示这些 Cookie,但可能会导致某些网站功能无法工作。