# Releases

## Schedule

Novel will have a quarterly major release schedule and an indefinite number of minor patches. 

| January 2025 | March 2025 | June 2025 | September 2025 |
| ------------ | ---------- | --------- | -------------- |
| 2025.1.0     | 2025.2.0   | 2025.3.0  | 2025.4.0       |

Nightly releases will be available on the relevant repositories under the `nightly`branches.

## Upgrading

{% hint style="warning" %}
THIS FEATURE IS SCHEDULED FOR 2025.2.0
{% endhint %}

## Support Coverage <a href="#upgrade-support-coverage" id="upgrade-support-coverage"></a>

This document outlines the upgrade process and scope of support for the software. For full details on warranty and support coverage, refer to the `WARRANTY.md` file.

Upgrades to the software are supported as follows:

### Covered Directories <a href="#covered-directories" id="covered-directories"></a>

The following directories are covered under the warranty as specified in `WARRANTY.md`. Upgrades in these directories will be fully supported and aligned with the upgrade process detailed at <https://docs.novel.dev/upgrading>:

* **`deploy`**: All deployment-related configurations and files.
* **`packages`**: Core software logic and modules within this directory.
* **`test`**: Tests provided within the covered directories.

### Userland Directories <a href="#userland-directories" id="userland-directories"></a>

The following directories fall outside the scope of full warranty coverage. Any upgrades affecting these directories will be handled on a best-effort basis. Code generation tools may be provided where feasible to assist with integration:

* **`app`**: Application-specific files, user customization, and logic.
* **`components`**: User-defined or customized UI components.
* **`test`** (outside covered files): User-modified test cases in unrelated directories.

### Important Notes <a href="#important-notes" id="important-notes"></a>

1. Modifications to files within the `packages` directory will void warranty coverage for those files.
2. It is recommended to maintain backups of your customizations before proceeding with upgrades.
3. For a step-by-step guide and resources for upgrading supported directories, visit <https://docs.novel.dev/updates>.


---

# 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.novel.dev/releases.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.