> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/release-notes/version-numbering.md).

# Version Numbering

## Version Numbers <a href="#version-numbers" id="version-numbers"></a>

Frends use [semantic versioning](https://semver.org/) for releases.

Frends can have major, minor and service releases. A release is deemed a major release if it contains a big enough overreaching change, or it is deemed that multiple minor releases combined have changed the product's functionality enough to warrant a major release.

Minor releases are the main type of release for Frends. Minor release always requires both the update of the Core (UI and Log Service) and the Agents. The UI will notify the users of Agents not updated to match the Core.

Frends version is denoted by three numbers, for example in version 5.3.1 5 is the major version, 3 is a minor version and 1 is the service release. So, in other words, it is the first service release to the 3rd minor version update to the major version 5.

## Rollout of updates

All releases are rolled out gradually starting with demo/internal instances.

Customers are notified in advance of planned updates. Scheduling options vary by service tier as specified in the Terms of Service.

For version updates in hybrid installations, the customer is responsible for updating their Self-Hosted Agents after Frends Core and the Frends Cloud Agents have been updated.

Service releases can be deployed without actions from the Tenants on \*frendsapp.com, even in a hybrid environment, as they only affect the Frends Core.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.frends.com/release-notes/version-numbering.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.