Versioning of integrations is crucial in order to make different interlinked pieces of software work together. By communicating the changes with different stakeholders via version conventions and commonly agreed upon practices, it is easier to handle the lifecycle and make sure the integrations are compatible. Usually pieces of software are versioned with a number to indicate the growth over time and the functionality the software provides.

There are different ways to use versioning and Frends utilizes one of the most common types, semantic versioning. In the end, it is up to developers to handle versioning for the best efficiency and transparency although Frends provides some automation for versioning to help out the developers.

In Frends you can version Processes, Subprocesses and APIs. The versioning between Processes or Subprocesses and APIs differ slightly as APIs utilize Open API Specification which promotes a certain way of versioning consumable APIs.

The following modules will go through how semantic versioning of Frends works and what the best practices for Processes, Subprocesses and APIs are.

The next article is Best practices on Semantic versioning in Frends