> ## Documentation Index
> Fetch the complete documentation index at: https://docs.launcherforge.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Releases

> Understand LauncherForge versions, stable releases, patches, hotfixes, and changelogs.

# Releases

A release is a version published to a game branch. It records the version, release type, changelog, file manifest, and processing state.

## Release types

<Tabs>
  <Tab title="STABLE">
    Use `STABLE` for a complete production release or a new full baseline.

    The CLI treats the build as a complete upload and processes the full packaged directory.
  </Tab>

  <Tab title="PATCH">
    Use `PATCH` for a planned update based on an existing release.

    The CLI compares file hashes and transfers the files required for the new version.
  </Tab>

  <Tab title="HOTFIX">
    Use `HOTFIX` for an urgent, focused correction.

    It uses the same manifest-based comparison approach while keeping the release intent explicit.
  </Tab>
</Tabs>

## Version numbers

A semantic pattern is recommended:

```text theme={null}
MAJOR.MINOR.PATCH
```

Examples:

* `1.0.0` — first public version.
* `1.1.0` — feature update.
* `1.1.1` — bug-fix update.

Use a version only once within the relevant release context.

## Changelogs

Write changelogs for players, not only developers.

Good changelog:

```text theme={null}
Added controller remapping, improved loading times, and fixed a crash when changing regions.
```

Avoid internal notes that reveal credentials, infrastructure, private URLs, or sensitive implementation details.

## Release verification

After publishing, verify:

* Correct game and branch.
* Correct version and release type.
* Accurate changelog.
* Successful processing status.
* Install and update behavior.
* Game launch after installation.