# Change Log

The **Change Log** page provides a detailed record of updates, improvements, and bug fixes for the software or installation process. It is divided into two main sections:

**1.** [**Stable**](/install/change-log/stable.md)

The **Stable** section lists changes that have been thoroughly tested and are considered fully functional and reliable for production environments. These updates have undergone comprehensive testing and are suitable for general use. It includes:

* New features that are now available in the stable release.
* Bug fixes and improvements that have been resolved and validated.
* Any changes to the installation or configuration processes that impact the overall stability of the system.

This section is ideal for users who are running the current stable release and need to track changes that have been implemented for their environment.

**2.** [**Beta**](/install/change-log/beta.md)

The **Beta** section includes updates that are in the testing phase and not yet fully verified for production use. These changes may introduce new features, optimizations, or experimental fixes that are being tested and are subject to change. This section is intended for users who are testing pre-release versions and want to stay informed of ongoing updates. It includes:

* Features or functionality that are still being validated or refined.
* Known issues or limitations in the current beta release.
* Changes that may require additional testing or feedback from users before being included in the stable release.

This section is ideal for developers, testers, or early adopters who are working with the beta version and contributing feedback.


---

# Agent Instructions: 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:

```
GET https://docs.nuvens.cloud/install/change-log.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
