One of the most important aspects of operating services in Agentria is version management.

When versioning is handled properly, you can gain several key benefits:

• Clearly track all changes.

• Reduce confusion and misalignment among team members during collaboration.

• Roll back to a stable previous version in case of issues.

• Provide users with reliable and trustworthy updates.

This page will help you understand the rules for incrementing version numbers, how to create a new version, and how to review version history.

Versioning Rules

Agentria projects follow the principles of Semantic Versioning (SemVer).

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

Version numbers follow the format: Major.Minor.Patch

• Major version:

• Minor version:

• Patch version:

Examples:

Creating a New Version

In Agentria, creating a new version can be done directly within the Canvas editor.

In the Canvas editor, click the Publish button in the upper-right corner.

Select Create Version (Temporary) from the menu.

A modal window will appear where you can enter a version number.

• Make sure to follow the version rules when assigning the version.

Click Create to generate the new version.

Viewing Version History

Once a version has been created, you can manage and review its records using the Version History button in the upper-right corner of the Canvas.

• All versions are listed in chronological order.

Best Practices for Version management

To manage versions effectively, it’s recommended to follow these principles:

• Update in small increments: Instead of bundling many large changes into one release, make smaller, more frequent updates for easier tracking.

• Document changes: Maintain simple release notes or change logs whenever a new version is created to support better collaboration.

• Test before deployment: Especially for major and minor releases, ensure proper validation and QA testing before deploying to production.