> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.7.1/getting-started/release-cycles.md).

# Release Cycles

his guide offers a detailed explanation of the various release types, their significance, how to access them, and the expected release schedule.

We strongly encourage our customers to deploy the latest versions in their staging environments and conduct thorough testing before updating their production systems.

Customers with a valid support contract are entitled to a staging license. If you wish to request yours, please contact our support team via our [support portal](/helmut4-releases/v4.7.1/support/requesting-support.md#moovits-support-portal)

## **Stable Releases**

A stable release is published approximately every three to four months, specifically designed for deployment in production systems. This release is covered by the Helmut4 support contract.

To update to a stable release, access your Helmut server console and enter the following command with admin privileges:

```bash
helmut-snapshot <snapshot_version_number>

#example for Helmut 4.7.1
sudo helmut-snapshot 4.7.1
```

{% hint style="info" %}
The snapshot number of a release version can be found on the [changelog](/helmut4-releases/v4.7.1/release-notes/changelog.md) page.
{% endhint %}

### **DEV Releases**

Development releases are provided during the development of each stable release to give ourDevelopment releases are provided during the development of each stable release to offer our customers early access to bug fixes and features.

To update to a stable release, access your Helmut server console and enter the following command with admin privileges:

```bash
sudo helmut-update
```

{% hint style="warning" %}
These releases are password-protected. If you would like access, please contact our support team through the [support portal](/helmut4-releases/v4.7.1/support/requesting-support.md#moovits-support-portal)
{% endhint %}

#### Disclaimer DEV Releases

{% hint style="danger" %}
These releases are intended for staging systems only and ***not for production systems***.

They are not covered by the software maintenance contract.
{% endhint %}

### Semantic versioning

Helmut version 4.1.0 introduced a significant change in the way we version our backend components. We started using semantic versioning for all of our microservice endpoints.

The versioning format is as follows:&#x20;

```
Helmut_Version.Major_change.Minor_change.Patch
```

To better understand how this convention is applied, consider the following example: during the development of release 4.1.0, if we perform bug fixes in the Streams container, the shipped Docker container will have version 4.1.0.2.

However, if we introduce any breaking changes that are not backward compatible, we will ship the Streams container with version 4.2.0.1.

Because the backend microservices are completely decoupled from the product version (currently at version 4), there may be mixed version numbers for a single snapshot, such as a container with version 4.3.0.1 in the 4.5.0 product release.

Taking this into consideration, it is expected for a stable release to include new versions of some containers while others remain untouched.

This strategy results in shorter downtime and fewer untagged/unused, but still cached, images on the host system.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.helmut.de/helmut4-releases/v4.7.1/getting-started/release-cycles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.