Updates & versions

Checking for updates

Xiaohe Client, Heshi and Heyue check for updates at launch by default. Turn this off under Settings → Updates.

• When a new version exists, an update badge appears in the title bar. The settings page shows the version and notes; download, then restart to finish.
• The Xiaohe settings page shows the current channel and the last check. With “Download updates automatically” on, the download runs in the background and installation still asks first. “Upgrade the local service automatically” restarts the service when no session is running.
• On the command line, run xiaohe upgrade; add --beta to use the beta channel.

Per-platform updates

Desktop apps update in place first. Manual installers remain available for a failed update or a pinned version.

Swipe the table sideways.

The iOS app updates through the App Store. Installers for desktop and Android are on the download page.

Beta channel

Beta is the pre-release channel for trying the next version early. Builds may be unstable or incomplete. Stable and beta each have their own manifest; switching channels does not change the installed version.

• Xiaohe: Settings → Updates → “Beta updates”. The switch covers both the desktop app and the local service, and re-checks immediately.
• Heshi / Heyue: Settings → Updates → “Update from the beta channel”, then confirm.
• Command line: xiaohe upgrade --beta; return to stable with xiaohe upgrade.
• After switching back, a beta newer than the stable release is not downgraded automatically. Wait for stable to catch up, or reinstall the stable package.

When an update fails

1. Use “Check for updates” or “Retry” under Settings → Updates, and confirm the network and disk space are fine.
2. If the download or install fails, download the matching installer from the download page and install it over the current version. Sessions, workspace and settings live on this machine and are not cleared.
3. If macOS says the app cannot be verified, confirm the installer came from the download page, then allow it under System Settings → Privacy & Security.
4. Windows installers do not carry an Authenticode signature yet, so SmartScreen may warn. Confirm the file came from download.xiaohe.team, then choose “More info → Run anyway”.
5. Still stuck? Send the version, platform and error message to support@xiaohe.team.

Rollback and pinning

• Xiaohe Agent: xiaohe upgrade <version> switches to a specific public version, for example xiaohe upgrade 1.2.0; --beta takes a beta build. This changes the Agent and local service, not the desktop client.
• Desktop apps (Xiaohe Client, Heshi, Heyue) have no one-click downgrade. If a release misbehaves, keep your data and wait for a fix; contact support@xiaohe.team if you must go back.
• Heshi maintainers: make rollback-heshi [VERSION=x.y.z] withdraws the public update offer so clients that have not upgraded skip the bad build. Clients already upgraded are not downgraded. End users do not need to run this.

Version numbers

• Each product is versioned independently as major.minor.patch (X.Y.Z). Xiaohe Agent and Client ship separately and one release can carry two tags: agent-v1.2.0 and client-v1.4.0.
• Heshi and Heyue use vX.Y.Z (for example v0.2.3). Hesuan v0 uses vX.Y.Z, v1 uses X.Y (for example 1.3). OpenFOAM keeps the upstream year-based release 2412, with our packaging revision appended (currently v2412.5).
• Beta is a channel, not a version suffix. Stable and beta each have their own latest.json.
• Tags and the download directory are the source of truth. Dates are release dates, not install dates.