Understand AnQi CMS - Version System
Understand the version number rules (main version.minor version.revision number) of AnQi CMS, the history of version evolution, and the functional differences between community version and authorized version, to help users choose the appropriate version for installation and use according to their own needs.
Current version
As of July 2026, the latest stable version isv3.6.2(Release date: 2026-06-30).
Version number format:v主版本.次版本.修订号
- Main version: Major architectural changes or functional restructuring
- Minor version: Feature iteration, new core features
- Revision number: Bug fixes, minor optimizations
Version history summary
| Version | Date | Milestone |
|---|---|---|
| v0.1 | 2019-11-19 | GoBlog first version (Gin framework, front-end and back-end separation) |
| v0.5 | 2020-12-01 | Rewritten using Iris framework |
| v1.0.0 | 2021-01-21 | Blog improved version, added backend management, SEO features |
| v2.0.0-alpha | 2021-02-16 | Transformed from blog system to CMS |
| v2.1.0 | 2022-05-30 | Officially renamed to AnQiCMS |
| v3.0.0 | 2022-12-05 | Multi-site mode, commonly used features for corporate sites |
| v3.1.1 | 2023-04-15 | AI automatic writing |
| v3.2.5 | 2023-10-24 | Multi-language translation, Markdown editor |
| v3.3.5 | 2024-05-01 | Image watermark |
| v3.3.12 | 2024-09-05 | Document query performance optimization |
| v3.4.1 | 2024-11-11 | Multilingual site functionality |
| v3.4.7 | 2025-03-17 | Multilingual enhancement, full-page HTML translation |
| v3.6.1 | 2026-06-22 | Binary size reduced by 50% (103 MB → 51 MB) |
| v3.6.2 | 2026-06-30 | Latest version: AI Agent, city station, 7 AI seed skills |
Version selection recommendation
| Usage scenario | Suggestion |
|---|---|
| New station in production environment | ✅ Use the latest stable version (current v3.6.2) |
| Site upgrade already exists | ✅ Suggest upgrading to the latest version (Backend → System upgrade) |
| Development and testing | ✅ Can use stable version or clone master branch from GitHub |
| secondary development | ✅ Compile from GitHub source code, pay attention to CHANGELOG.md |
❓ Will data be lost when upgrading from v2.x to v3.x? Is the upgrade process complex?
What is the upgrade mechanism of AnQiCMS?Data losslessThe upgrade will only replace the program files and update the database structure, but it will not delete your content. ButIt is still recommended to back up the database before the upgradein case of emergency.
Anqi CMS provides the following three upgrade methods:
Method one (recommended): One-click upgrade from the background
Step 1: 登录后台 → 工具 → 系统升级（/tool/upgrade）
Step 2: 点击"检查更新"，系统自动检测是否有新版本
Step 3: 如有新版本，点击"立即升级"，系统自动完成下载和更新
Step 4: 升级完成后重启 AnQiCMS 进程
This is the most recommended upgrade method, which is operated throughout the background interface and does not require logging in to the server.
Method two: Manually download the binary package for upgrade
Step 1: 从官网或 GitHub Releases 下载最新版安装包
Step 2: 停止 AnQiCMS 进程：./stop.sh (宝塔用户通过Go项目停止)
Step 3: 解压安装包，覆盖旧版文件（保留 config.json 和 data/ 目录）
Step 4: 重启 AnQiCMS 进程：./start.sh (宝塔用户通过Go项目启动)
Method three: Docker upgrade
# 拉取最新镜像
docker pull anqicms/anqicms:latest
# 删除旧容器（数据不会丢失，前提是 MySQL / data / public / template 目录使用外部数据卷挂载）
docker rm -f anqicms
# 重新创建容器（使用同样的启动命令或 docker-compose up -d）
docker run -d --name anqicms -p 8001:8001 anqicms/anqicms:latest
If using Docker Compose: docker compose pull && docker compose up -dUpgrade is completed.
By default, after upgrading to a new version, the program will automatically complete the database upgrade. However, after the upgrade, if some functions cannot be used normally (it may be due to missing database fields), you can log in to the background → Tools → Update Cache → Click “Update Database Table Structure” to synchronize the latest database fields.
The entire process usually takes only 1-2 minutes, and Anqi CMS's database migration mechanism ensures that the old version database can smoothly transition to the new version without manual data migration.
❓ The version number has jumped so much (v0.1 → v3.6.2), does it mean that the system is not yet stable?
The large jump in version numbers is because it has evolved from GoBlog (v0.1) in 2019 to the current v3.x. v3.x is alreadya stable series, each minor version has been fully tested.
In fact, Anqicms follows the Semantic Versioning (SemVer) specification:
v3representing the third-generation architecture (after multiple重构).6representing the 6th functional iteration (accumulation of features from 2024-2026).2Represent bug fixes and detail optimizations
If you are concerned about stability, you can pay attention to the release frequency of versions—the release rhythm of the v3.x series is about every 3-6 months, each time it is a gradual improvement without destructive architectural changes.