Guides
Choosing Versions
How to choose stable tags for Server, ChatServer, and client SDKs.
Choosing versions for production
For production, use the latest official release marked with the green Latest badge on GitHub Releases.
| Component | Version source |
|---|---|
| OpenIMServer | OpenIMServer Releases |
| ChatServer | ChatServer Releases |
| OpenIMClientSDK | The Releases page for the client SDK repository you integrate |
- Always use an explicit stable tag. Do not rely on branch names or guess version ordering.
- Do not use alpha, beta, rc, or other prerelease versions directly in production.
- When deploying OpenIMServer and ChatServer together, select compatible official tags according to their release notes.
- When integrating OpenIMClientSDK, check the supported server version range and release notes to avoid cross-version capability differences.
- Record every component tag in the deployment inventory and rollback plan so issues can be reproduced, staged rollouts can be reversed, and environments remain consistent.
Finding the latest stable release
GitHub's releases/latest URL redirects to the current official release. Use the following commands to obtain its tag:
SERVER_LATEST_TAG=$(basename "$(curl -fsSLI -o /dev/null -w '%{url_effective}' https://github.com/openimsdk/open-im-server/releases/latest)")
echo "$SERVER_LATEST_TAG"
CHAT_LATEST_TAG=$(basename "$(curl -fsSLI -o /dev/null -w '%{url_effective}' https://github.com/openimsdk/chat/releases/latest)")
echo "$CHAT_LATEST_TAG"After pinning a version, store both the tag and its release-note link in the deployment record. Do not hard-code the "current latest version" on this page because it becomes outdated as soon as a new release is published.
Release notes
- OpenIMServer: OpenIMServer Releases
- ChatServer: ChatServer Releases
- OpenIMClientSDK: the Releases page and release notes for the platform SDK repository you use