OpenIMSDKDocs

Type at least two characters to search titles and routes.

EN

Language

ENEnglishEnglish docs简中简体中文中文文档
Browse OpenIMSDK Guides
GUIDESOpenIMSDK Guides

OpenIMSDK guides organized by implementation stage, from product concepts and deployment to integration, extension, operations, and reliability.

Guides

Choosing Versions

How to choose stable tags for OpenIMServer, ChatServer, and OpenIMClientSDK.

Copy

Production version selection

For production environments, always select the latest official release designated by the green Latest badge on GitHub Releases.

ComponentVersion source
OpenIMServerOpenIMServer Releases
ChatServerChatServer Releases
OpenIMClientSDKThe Releases page of your integrated platform SDK repository
  • Always pin explicit stable release tags; avoid relying on branch names or guessing release ordering.
  • Do not deploy alpha, beta, rc, or other pre-release versions directly into production.
  • When deploying OpenIMServer alongside ChatServer, cross-reference release notes to select mutually compatible stable release tags.
  • When integrating OpenIMClientSDK, verify the supported server version range and release notes to prevent cross-version capability mismatches.
  • Document all component tags in your deployment inventory and rollback plan to streamline issue reproduction, canary rollbacks, and multi-environment consistency.

Query the latest official release

GitHub redirects releases/latest to the current official release. Run the following commands to extract the active stable tags:

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"

Once versions are determined, record both the tags and their corresponding release note links in your deployment manifest. Avoid hardcoding "current latest version" numbers in static documentation, as they become obsolete as soon as a new release is cut.

View release notes