> ## Documentation Index
> Fetch the complete documentation index at: https://hanabiaiinc-him188-rename-multi-turn-simulation.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Releases

> How Fish Audio Enterprise versions are identified and how to move between them

Fish Audio publishes a version for each mode once it has been tested.
**Developer → Self Host** lists the versions available to your team and fills the
one you pick into the install commands on that page.

## Version identifiers

| Platform | Identified by | Applied with |
| - | - | - |
| Helm | A chart version | `--version` on `helm pull`/`install` |
| All-in-One | An image tag | The tag in the image reference |

Both Helm profiles are one chart, so they share a version. Which profile you deploy is
decided by the values file, not by the version. Each All-in-One mode — the
combination of billing, GPU topology, and how weights are delivered — is released
and tagged independently; **Developer → Self Host** shows the ones your team
is granted.

## Upgrading

A deployment stays on its version until you change it. Take the new version from
**Developer → Self Host**, then follow the upgrade
procedure in the deployment runbook for the Helm platform, or pull the new tag and
recreate the container against the same volume for
[All-in-One](/developer-guide/self-hosting/all-in-one). Air-gapped deployments
mirror the new version first. See
[Air-gapped deployments](/developer-guide/self-hosting/air-gapped).

<Note>
  Talk to your account team before skipping versions, and before upgrading a
  production deployment, so the change can be checked against how yours is
  configured.
</Note>

## Next step

Return to [Kubernetes deployment](/developer-guide/self-hosting/kubernetes) or
[All-in-One container](/developer-guide/self-hosting/all-in-one) to apply the
version you picked.