Function Compute provides the versioning feature to help you efficiently manage services, functions, and triggers. You can use this feature to publish multiple versions of a service to implement continuous integration and publish in software development lifecycles. This topic describes how to publish, view, and delete a version in the Function Compute console.
What is a version?
Function Compute provides service-level versioning feature, which allows you to publish one or more versions for a service. A version is similar to a service snapshot that contains the information such as the service settings, and the code and settings of functions that belong to the service. A version does not contain trigger information. When you publish a version, the system generates a snapshot for the service and assigns a version number that is associated with the snapshot for future use.
If you do not use the versioning feature, every change in a service affects the production environment. This way, you cannot control the time to publish the latest versions. If you use the versioning feature, you can use a stable service version to respond to online requests after the test results become stable. In addition, you can continue to develop and test the LATEST version. The following figure shows the mechanism for the versioning feature.

Precautions
- A new service has only one LATEST version. Before you publish any version of the service, the LATEST version is the only service version that you own. The LATEST version cannot be deleted.
- A published version cannot be modified. The version number monotonically increases and cannot be reused.
Prerequisites
Procedure
References
Aside from the Function Compute console, you can also use Serverless Devs to configure versions for a service. For more information, see Basic features.