Skip to main content
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

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. Air-gapped deployments mirror the new version first. See Air-gapped deployments.
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.

Next step

Return to Kubernetes deployment or All-in-One container to apply the version you picked.