If you have completed a workflow in Agentria, you can deploy it as an API and use it across various tasks.

To deploy an API, you must first create a deployment version of the workflow.

Importance of Version Management

Proper version management offers the following benefits:

• Clearly track and review change history.

• Reduce confusion and conflicts during team collaboration.

• Safely roll back to a stable previous version if issues occur.

• Provide reliable updates to end users.

Through this page, you will learn the criteria for increasing version numbers, how to actually create a new version, and how to review version history.

Versioning Standards

Agentria projects follow Semantic Versioning.

(Reference: https://semver.org/)

A version number is composed in the format: Major.Minor.Patch

• Major version: Increased when backward compatibility is broken.

• Minor version: Increased when new features are added without breaking backward compatibility.

• Patch version: Increased for bug fixes, security patches, or small performance improvements.

Examples

Step1: Creating a Version

Click the Publish button at the top-right corner of the canvas, then select Create Version.

In the pop-up window, you can create a deployment version.

Enter the version number and description according to the semantic versioning standard, then click Create.

Step2: Checking Version History

Once a version has been created, click the Version History button at the top-right corner of the canvas to review and manage past records.