This is an automated email from the ASF dual-hosted git repository.

jin pushed a commit to branch fix-docker
in repository https://gitbox.apache.org/repos/asf/incubator-hugegraph-doc.git

commit 8602996f3ee4dcd11301f483a70284b1977f8531
Author: imbajin <j...@apache.org>
AuthorDate: Thu Dec 12 18:35:09 2024 +0800

    chore: update version to 1.5.0
---
 .../docs/changelog/hugegraph-1.3.0-release-notes.md  |  2 +-
 .../docs/changelog/hugegraph-1.5.0-release-notes.md  |  2 +-
 content/cn/docs/config/config-authentication.md      |  4 ++--
 content/cn/docs/quickstart/hugegraph-client.md       |  2 +-
 content/cn/docs/quickstart/hugegraph-hubble.md       |  8 ++++----
 content/cn/docs/quickstart/hugegraph-loader.md       | 10 +++++-----
 content/cn/docs/quickstart/hugegraph-server.md       | 20 ++++++++++----------
 content/en/docs/config/config-authentication.md      |  8 ++++----
 content/en/docs/quickstart/hugegraph-client.md       |  2 +-
 content/en/docs/quickstart/hugegraph-hubble.md       |  8 ++++----
 content/en/docs/quickstart/hugegraph-loader.md       |  4 ++--
 content/en/docs/quickstart/hugegraph-server.md       | 20 ++++++++++----------
 12 files changed, 45 insertions(+), 45 deletions(-)

diff --git a/content/cn/docs/changelog/hugegraph-1.3.0-release-notes.md 
b/content/cn/docs/changelog/hugegraph-1.3.0-release-notes.md
index 7eedc8c3..aa84047f 100644
--- a/content/cn/docs/changelog/hugegraph-1.3.0-release-notes.md
+++ b/content/cn/docs/changelog/hugegraph-1.3.0-release-notes.md
@@ -9,7 +9,7 @@ weight: 4
 1. 优先在 `hugegraph/toolchain/commons`软件中使用 Java 11, 此次是这些模块最后一次主版本兼容 Java 8 
了。(computer 则仅支持 Java11)
 2. 另外相比 Java11, 使用 Java8 会失去一些**安全性**的保障,我们推荐生产或对外网暴露访问的环境使用 Java11 并开启 [Auth 
权限认证](/cn/docs/config/config-authentication/)
 
-**1.3.0** 是最后兼容 **Java 8** 的版本,在下一个 1.5.0 版本发布 -- 
[PD/Store](https://github.com/apache/incubator-hugegraph/issues/2265) 
合入主分支时就会全面使用 Java 11 (除`client`外).
+**1.3.0** 是最后兼容 **Java 8** 的版本,在 1.5.0 开始就会全面使用 Java 11 (除`client`外).
 
 PS: 未来 HugeGraph 组件的版本会朝着 `Java 11 -> Java 17 -> Java 21` 演进
 
diff --git a/content/cn/docs/changelog/hugegraph-1.5.0-release-notes.md 
b/content/cn/docs/changelog/hugegraph-1.5.0-release-notes.md
index 8a7ca703..1e29e29c 100644
--- a/content/cn/docs/changelog/hugegraph-1.5.0-release-notes.md
+++ b/content/cn/docs/changelog/hugegraph-1.5.0-release-notes.md
@@ -15,6 +15,6 @@ Please check the release details/contributor in each 
repository:
 
 ### 运行环境/版本说明
 
-1. 相较于 **1.3.0**,**1.5.0** 的 `hugegraph` 仅支持 Java 11
+1. 相较于 **1.3.0**,**1.5.0** 及后的 `hugegraph` 仅支持 Java 11
 
 PS: 未来 HugeGraph 组件的版本会朝着 `Java 11 -> Java 17 -> Java 21` 演进
diff --git a/content/cn/docs/config/config-authentication.md 
b/content/cn/docs/config/config-authentication.md
index 7e8f28f4..0f0aa13c 100644
--- a/content/cn/docs/config/config-authentication.md
+++ b/content/cn/docs/config/config-authentication.md
@@ -123,7 +123,7 @@ bin/start-hugegraph.sh
 在 `docker run` 中添加环境变量 `PASSWORD=123456`(密码可以自由设置)即可开启鉴权模式::
 
 ```bash
-docker run -itd -e PASSWORD=123456 --name=server -p 8080:8080 
hugegraph/hugegraph:1.3.0
+docker run -itd -e PASSWORD=123456 --name=server -p 8080:8080 
hugegraph/hugegraph:1.5.0
 ```
 
 #### 2. 采用 docker-compose
@@ -134,7 +134,7 @@ docker run -itd -e PASSWORD=123456 --name=server -p 
8080:8080 hugegraph/hugegrap
 version: '3'
 services:
   server:
-    image: hugegraph/hugegraph:1.3.0
+    image: hugegraph/hugegraph:1.5.0
     container_name: server
     ports:
       - 8080:8080
diff --git a/content/cn/docs/quickstart/hugegraph-client.md 
b/content/cn/docs/quickstart/hugegraph-client.md
index df44ec4c..5934cfdf 100644
--- a/content/cn/docs/quickstart/hugegraph-client.md
+++ b/content/cn/docs/quickstart/hugegraph-client.md
@@ -48,7 +48,7 @@ weight: 4
         <groupId>org.apache.hugegraph</groupId>
         <artifactId>hugegraph-client</artifactId>
         <!-- Update to the latest release version -->
-        <version>1.3.0</version>
+        <version>1.5.0</version>
     </dependency>
 </dependencies>
 ```
diff --git a/content/cn/docs/quickstart/hugegraph-hubble.md 
b/content/cn/docs/quickstart/hugegraph-hubble.md
index 6e022340..e784c488 100644
--- a/content/cn/docs/quickstart/hugegraph-hubble.md
+++ b/content/cn/docs/quickstart/hugegraph-hubble.md
@@ -53,7 +53,7 @@ weight: 3
 > 
 > 若 hubble 和 server 在同一 docker 网络下,**推荐**直接使用`container_name` (如下例的 `server`) 
 > 作为主机名。或者也可以使用 **宿主机 IP** 作为主机名,此时端口号为宿主机给 server 配置的端口
 
-我们可以使用 `docker run -itd --name=hubble -p 8088:8088 hugegraph/hubble:1.2.0` 
快速启动 [hubble](https://hub.docker.com/r/hugegraph/hubble).
+我们可以使用 `docker run -itd --name=hubble -p 8088:8088 hugegraph/hubble:1.5.0` 
快速启动 [hubble](https://hub.docker.com/r/hugegraph/hubble).
 
 或者使用 docker-compose 启动 hubble,另外如果 hubble 和 server 在同一个 docker 网络下,可以使用 server 
的 contain_name 进行访问,而不需要宿主机的 ip
 
@@ -63,13 +63,13 @@ weight: 3
 version: '3'
 services:
   server:
-    image: hugegraph/hugegraph:1.3.0
+    image: hugegraph/hugegraph:1.5.0
     container_name: server
     ports:
       - 8080:8080
 
   hubble:
-    image: hugegraph/hubble:1.2.0
+    image: hugegraph/hubble:1.5.0
     container_name: hubble
     ports:
       - 8088:8088
@@ -79,7 +79,7 @@ services:
 >
 > 1. `hugegraph-hubble` 的 docker 镜像是一个便捷发布版本,用于快速测试试用 hubble,并非**ASF 
 > 官方发布物料包的方式**。你可以从 [ASF Release Distribution 
 > Policy](https://infra.apache.org/release-distribution.html#dockerhub) 
 > 中得到更多细节。
 >
-> 2. **生产环境**推荐使用 `release tag`(如 `1.2.0`) 稳定版。使用 `latest` tag 默认对应 master 
最新代码。
+> 2. **生产环境**推荐使用 `release tag`(如 `1.5.0`) 稳定版。使用 `latest` tag 默认对应 master 
最新代码。
 
 #### 2.2 下载 toolchain 二进制包
 
diff --git a/content/cn/docs/quickstart/hugegraph-loader.md 
b/content/cn/docs/quickstart/hugegraph-loader.md
index 09e41a34..a15f39e8 100644
--- a/content/cn/docs/quickstart/hugegraph-loader.md
+++ b/content/cn/docs/quickstart/hugegraph-loader.md
@@ -31,7 +31,7 @@ HugeGraph-Loader 是 HugeGraph 的数据导入组件,能够将多种数据源
 
 #### 2.1 使用 Docker 镜像 (便于**测试**)
 
-我们可以使用 `docker run -itd --name loader hugegraph/loader:1.3.0`部署 loader 
服务。对于需要加载的数据,则可以通过挂载 `-v /path/to/data/file:/loader/file` 或者`docker 
cp`的方式将文件复制到 loader 容器内部。
+我们可以使用 `docker run -itd --name loader hugegraph/loader:1.5.0`部署 loader 
服务。对于需要加载的数据,则可以通过挂载 `-v /path/to/data/file:/loader/file` 或者`docker 
cp`的方式将文件复制到 loader 容器内部。
 
 或者使用 docker-compose 启动 loader, 启动命令为 `docker-compose up -d`, 样例的 
docker-compose.yml 如下所示:
 
@@ -40,19 +40,19 @@ version: '3'
 
 services:
   server:
-    image: hugegraph/hugegraph:1.3.0
+    image: hugegraph/hugegraph:1.5.0
     container_name: server
     ports:
       - 8080:8080
 
   hubble:
-    image: hugegraph/hubble:1.2.0
+    image: hugegraph/hubble:1.5.0
     container_name: hubble
     ports:
       - 8088:8088
 
   loader:
-    image: hugegraph/loader:1.3.0
+    image: hugegraph/loader:1.5.0
     container_name: loader
     # mount your own data here
     # volumes:
@@ -66,7 +66,7 @@ services:
 > 
 > 1. hugegraph-loader 的 docker 镜像是一个便捷版本,用于快速启动 loader,并不是**官方发布物料包方式**。你可以从 
 > [ASF Release Distribution 
 > Policy](https://infra.apache.org/release-distribution.html#dockerhub) 
 > 中得到更多细节。
 > 
-> 2. 推荐使用 `release tag`(如 `1.2.0`) 以获取稳定版。使用 `latest` tag 可以使用开发中的最新功能。
+> 2. 推荐使用 `release tag`(如 `1.5.0`) 以获取稳定版。使用 `latest` tag 可以使用开发中的最新功能。
 
 #### 2.2 下载已编译的压缩包
 
diff --git a/content/cn/docs/quickstart/hugegraph-server.md 
b/content/cn/docs/quickstart/hugegraph-server.md
index 5b406f9b..de1f9873 100644
--- a/content/cn/docs/quickstart/hugegraph-server.md
+++ b/content/cn/docs/quickstart/hugegraph-server.md
@@ -39,12 +39,12 @@ Core 模块是 Tinkerpop 接口的实现,Backend 模块用于管理数据存
 
 可参考 [Docker 
部署方式](https://github.com/apache/incubator-hugegraph/blob/master/hugegraph-server/hugegraph-dist/docker/README.md)。
 
-我们可以使用 `docker run -itd --name=server -p 8080:8080 hugegraph/hugegraph:1.3.0` 
去快速启动一个内置了 `RocksDB` 的 `Hugegraph server`.
+我们可以使用 `docker run -itd --name=server -p 8080:8080 hugegraph/hugegraph:1.5.0` 
去快速启动一个内置了 `RocksDB` 的 `Hugegraph server`.
 
 可选项:
 
 1. 可以使用 `docker exec -it server bash` 进入容器完成一些操作
-2. 可以使用 `docker run -itd --name=server -p 8080:8080 -e PRELOAD="true" 
hugegraph/hugegraph:1.3.0` 在启动的时候预加载一个**内置的**样例图。可以通过 `RESTful API` 
进行验证。具体步骤可以参考 
[5.1.1](/cn/docs/quickstart/hugegraph-server/#511-%E5%90%AF%E5%8A%A8-server-%E7%9A%84%E6%97%B6%E5%80%99%E5%88%9B%E5%BB%BA%E7%A4%BA%E4%BE%8B%E5%9B%BE)
 
+2. 可以使用 `docker run -itd --name=server -p 8080:8080 -e PRELOAD="true" 
hugegraph/hugegraph:1.5.0` 在启动的时候预加载一个**内置的**样例图。可以通过 `RESTful API` 
进行验证。具体步骤可以参考 
[5.1.1](/cn/docs/quickstart/hugegraph-server/#511-%E5%90%AF%E5%8A%A8-server-%E7%9A%84%E6%97%B6%E5%80%99%E5%88%9B%E5%BB%BA%E7%A4%BA%E4%BE%8B%E5%9B%BE)
 
 3. 可以使用 `-e PASSWORD=123456` 设置是否开启鉴权模式以及 admin 的密码,具体步骤可以参考 [Config 
Authentication](/cn/docs/config/config-authentication#使用-docker-时开启鉴权模式) 
 
 如果使用 docker desktop,则可以按照如下的方式设置可选项:
@@ -59,7 +59,7 @@ Core 模块是 Tinkerpop 接口的实现,Backend 模块用于管理数据存
 version: '3'
 services:
   server:
-    image: hugegraph/hugegraph:1.3.0
+    image: hugegraph/hugegraph:1.5.0
     container_name: server
     # environment:
     #  - PRELOAD=true 为可选参数,为 True 时可以在启动的时候预加载一个内置的样例图
@@ -72,12 +72,12 @@ services:
 > 
 > 1. hugegraph 的 docker 镜像是一个便捷版本,用于快速启动 hugegraph,并不是**官方发布物料包方式**。你可以从 [ASF 
 > Release Distribution 
 > Policy](https://infra.apache.org/release-distribution.html#dockerhub) 
 > 中得到更多细节。
 >
-> 2. 推荐使用 `release tag`(如 `1.3.0/1.5.0`) 以获取稳定版。使用 `latest` tag 可以使用开发中的最新功能。
+> 2. 推荐使用 `release tag`(如 `1.5.0/1.x.0`) 以获取稳定版。使用 `latest` tag 可以使用开发中的最新功能。
 
 #### 3.2 下载 tar 包
 
 ```bash
-# use the latest version, here is 1.3.0 for example
+# use the latest version, here is 1.5.0 for example
 wget 
https://downloads.apache.org/incubator/hugegraph/{version}/apache-hugegraph-incubating-{version}.tar.gz
 tar zxf *hugegraph*.tar.gz
 ```
@@ -104,7 +104,7 @@ mvn package -DskipTests
 
 ```bash
 ......
-[INFO] Reactor Summary for hugegraph 1.3.0:
+[INFO] Reactor Summary for hugegraph 1.5.0:
 [INFO] 
 [INFO] hugegraph .......................................... SUCCESS [  2.405 s]
 [INFO] hugegraph-core ..................................... SUCCESS [ 13.405 s]
@@ -132,8 +132,8 @@ mvn package -DskipTests
 HugeGraph-Tools 提供了一键部署的命令行工具,用户可以使用该工具快速地一键下载、解压、配置并启动 HugeGraph-Server 和 
HugeGraph-Hubble,最新的 HugeGraph-Toolchain 中已经包含所有的这些工具,直接下载它解压就有工具包集合了
 
 ```bash
-# download toolchain package, it includes loader + tool + hubble, please check 
the latest version (here is 1.3.0)
-wget 
https://downloads.apache.org/incubator/hugegraph/1.3.0/apache-hugegraph-toolchain-incubating-1.3.0.tar.gz
+# download toolchain package, it includes loader + tool + hubble, please check 
the latest version (here is 1.5.0)
+wget 
https://downloads.apache.org/incubator/hugegraph/1.5.0/apache-hugegraph-toolchain-incubating-1.5.0.tar.gz
 tar zxf *hugegraph-*.tar.gz
 # enter the tool's package
 cd *hugegraph*/*tool* 
@@ -516,7 +516,7 @@ volumes:
 
 1. 使用`docker run`
 
-    使用 `docker run -itd --name=server -p 8080:8080 -e PRELOAD=true 
hugegraph/hugegraph:1.3.0`
+    使用 `docker run -itd --name=server -p 8080:8080 -e PRELOAD=true 
hugegraph/hugegraph:1.5.0`
 
 2. 使用`docker-compose`
 
@@ -526,7 +526,7 @@ volumes:
     version: '3'
       services:
         server:
-          image: hugegraph/hugegraph:1.3.0
+          image: hugegraph/hugegraph:1.5.0
           container_name: server
           environment:
             - PRELOAD=true
diff --git a/content/en/docs/config/config-authentication.md 
b/content/en/docs/config/config-authentication.md
index 512c63df..46b945f0 100644
--- a/content/en/docs/config/config-authentication.md
+++ b/content/en/docs/config/config-authentication.md
@@ -99,9 +99,9 @@ After the authentication configuration completed, enter the 
**admin password** o
 
 If deployed based on Docker image or if HugeGraph has already been initialized 
and needs to be converted to authentication mode, 
 relevant graph data needs to be deleted and HugeGraph needs to be restarted. 
If there is already business data in the diagram, 
-it is temporarily **not possible** to directly convert the authentication mode 
(version<=1.2.0 )
+it is temporarily **not possible** to directly convert the authentication mode 
(version<=1.2.0)
 
-> Improvements for this feature have been included in the latest release 
(available in latest docker image), please refer to  [PR 
2411](https://github.com/apache/incubator-hugegraph/pull/2411). Seamless 
switching is now available.
+> Improvements for this feature have been included in the latest release 
(available in the latest docker image), please refer to [PR 
2411](https://github.com/apache/incubator-hugegraph/pull/2411). Seamless 
switching is now available.
 
 ```bash
 # stop the hugeGraph firstly
@@ -130,7 +130,7 @@ The steps are as follows:
 To enable authentication mode, add the environment variable `PASSWORD=123456` 
(you can freely set the password) in the `docker run` command:
 
 ```bash
-docker run -itd -e PASSWORD=123456 --name=server -p 8080:8080 
hugegraph/hugegraph:1.3.0
+docker run -itd -e PASSWORD=123456 --name=server -p 8080:8080 
hugegraph/hugegraph:1.5.0
 ```
 
 #### 2. Use docker-compose
@@ -141,7 +141,7 @@ Use `docker-compose` and set the environment variable 
`PASSWORD=123456`:
 version: '3'
 services:
   server:
-    image: hugegraph/hugegraph:1.2.0
+    image: hugegraph/hugegraph:1.5.0
     container_name: server
     ports:
       - 8080:8080
diff --git a/content/en/docs/quickstart/hugegraph-client.md 
b/content/en/docs/quickstart/hugegraph-client.md
index f480a1f2..f81000a3 100644
--- a/content/en/docs/quickstart/hugegraph-client.md
+++ b/content/en/docs/quickstart/hugegraph-client.md
@@ -44,7 +44,7 @@ Using IDEA or Eclipse to create the project:
         <groupId>org.apache.hugegraph</groupId>
         <artifactId>hugegraph-client</artifactId>
         <!-- Update to the latest release version -->
-        <version>1.3.0</version>
+        <version>1.5.0</version>
     </dependency>    
 </dependencies>
 ```
diff --git a/content/en/docs/quickstart/hugegraph-hubble.md 
b/content/en/docs/quickstart/hugegraph-hubble.md
index 2664e8eb..499b8152 100644
--- a/content/en/docs/quickstart/hugegraph-hubble.md
+++ b/content/en/docs/quickstart/hugegraph-hubble.md
@@ -64,7 +64,7 @@ There are three ways to deploy `hugegraph-hubble`
 >
 >  If `hubble` and `server` is in the same docker network, we **recommend** 
 > using the `container_name` (in our example, it is `server`) as the hostname, 
 > and `8080` as the port. Or you can use the **host IP** as the hostname, and 
 > the port is configured by the host for the server.
 
-We can use `docker run -itd --name=hubble -p 8088:8088 hugegraph/hubble:1.2.0` 
to quick start [hubble](https://hub.docker.com/r/hugegraph/hubble).
+We can use `docker run -itd --name=hubble -p 8088:8088 hugegraph/hubble:1.5.0` 
to quick start [hubble](https://hub.docker.com/r/hugegraph/hubble).
 
 Alternatively, you can use Docker Compose to start `hubble`. Additionally, if 
`hubble` and the graph are in the same Docker network, you can access the graph 
using the container name of the graph, eliminating the need for the host 
machine's IP address.
 
@@ -74,13 +74,13 @@ Use `docker-compose up -d`,`docker-compose.yml` is 
following:
 version: '3'
 services:
   server:
-    image: hugegraph/hugegraph:1.3.0
+    image: hugegraph/hugegraph:1.5.0
     container_name: server
     ports:
       - 8080:8080
 
   hubble:
-    image: hugegraph/hubble:1.2.0
+    image: hugegraph/hubble:1.5.0
     container_name: hubble
     ports:
       - 8088:8088
@@ -90,7 +90,7 @@ services:
 >
 > 1. The docker image of hugegraph-hubble is a convenience release to start 
 > hugegraph-hubble quickly, but not **official distribution** artifacts. You 
 > can find more details from [ASF Release Distribution 
 > Policy](https://infra.apache.org/release-distribution.html#dockerhub).
 > 
-> 2. Recommand to use `release tag`(like `1.2.0`) for the stable version. Use 
`latest` tag to experience the newest functions in development.
+> 2. Recommand to use `release tag`(like `1.5.0`) for the stable version. Use 
`latest` tag to experience the newest functions in development.
 
 #### 2.2 Download the Toolchain binary package
 
diff --git a/content/en/docs/quickstart/hugegraph-loader.md 
b/content/en/docs/quickstart/hugegraph-loader.md
index 36189057..0d747bee 100644
--- a/content/en/docs/quickstart/hugegraph-loader.md
+++ b/content/en/docs/quickstart/hugegraph-loader.md
@@ -29,7 +29,7 @@ There are two ways to get HugeGraph-Loader:
 
 #### 2.1 Use Docker image (Convenient for Test/Dev)
 
-We can deploy the loader service using `docker run -itd --name loader 
hugegraph/loader:1.3.0`. For the data that needs to be loaded, it can be copied 
into the loader container either by mounting `-v 
/path/to/data/file:/loader/file` or by using `docker cp`.
+We can deploy the loader service using `docker run -itd --name loader 
hugegraph/loader:1.5.0`. For the data that needs to be loaded, it can be copied 
into the loader container either by mounting `-v 
/path/to/data/file:/loader/file` or by using `docker cp`.
 
 Alternatively, to start the loader using docker-compose, the command is 
`docker-compose up -d`. An example of the docker-compose.yml is as follows:
 
@@ -56,7 +56,7 @@ The specific data loading process can be referenced under 
[4.5 User Docker to lo
 > Note: 
 > 1. The docker image of hugegraph-loader is a convenience release to start 
 > hugegraph-loader quickly, but not **official distribution** artifacts. You 
 > can find more details from [ASF Release Distribution 
 > Policy](https://infra.apache.org/release-distribution.html#dockerhub).
 > 
-> 2. Recommand to use `release tag`(like `1.2.0`) for the stable version. Use 
`latest` tag to experience the newest functions in development.
+> 2. Recommend to use `release tag`(like `1.5.0`) for the stable version. Use 
`latest` tag to experience the newest functions in development.
 
 #### 2.2 Download the compiled archive
 
diff --git a/content/en/docs/quickstart/hugegraph-server.md 
b/content/en/docs/quickstart/hugegraph-server.md
index 75d914e3..439b6247 100644
--- a/content/en/docs/quickstart/hugegraph-server.md
+++ b/content/en/docs/quickstart/hugegraph-server.md
@@ -42,11 +42,11 @@ There are four ways to deploy HugeGraph-Server components:
 <!-- 3.1 is linked by another place. if change 3.1's title, please check -->
 You can refer to [Docker deployment 
guide](https://hub.docker.com/r/hugegraph/hugegraph).
 
-We can use `docker run -itd --name=graph -p 8080:8080 
hugegraph/hugegraph:1.3.0` to quickly start an inner `HugeGraph server` with 
`RocksDB` in background.
+We can use `docker run -itd --name=graph -p 8080:8080 
hugegraph/hugegraph:1.5.0` to quickly start an inner `HugeGraph server` with 
`RocksDB` in background.
 
 Optional: 
 1. use `docker exec -it graph bash` to enter the container to do some 
operations.
-2. use `docker run -itd --name=graph -p 8080:8080 -e PRELOAD="true" 
hugegraph/hugegraph:1.3.0` to start with a **built-in** example graph. We can 
use `RESTful API` to verify the result. The detailed step can refer to 
[5.1.7](#517-create-an-example-graph-when-startup)
+2. use `docker run -itd --name=graph -p 8080:8080 -e PRELOAD="true" 
hugegraph/hugegraph:1.5.0` to start with a **built-in** example graph. We can 
use `RESTful API` to verify the result. The detailed step can refer to 
[5.1.7](#517-create-an-example-graph-when-startup)
 3. use `-e PASSWORD=123456` to enable auth mode and set the password for 
admin. You can find more details from [Config 
Authentication](/docs/config/config-authentication#Use-docker-to-enble-authentication-mode)
 
 If you use docker desktop, you can set the option like: 
@@ -60,7 +60,7 @@ Also, if we want to manage the other Hugegraph related 
instances in one file, we
 version: '3'
 services:
   server:
-    image: hugegraph/hugegraph:1.3.0
+    image: hugegraph/hugegraph:1.5.0
     container_name: server
     # environment:
     #  - PRELOAD=true
@@ -75,13 +75,13 @@ services:
 >
 > 1. The docker image of hugegraph is a convenience release to start hugegraph 
 > quickly, but not **official distribution** artifacts. You can find more 
 > details from [ASF Release Distribution 
 > Policy](https://infra.apache.org/release-distribution.html#dockerhub).
 > 
-> 2. Recommend to use `release tag`(like `1.3.0`/`1.5.0`) for the stable 
version. Use `latest` tag to experience the newest functions in development.
+> 2. Recommend to use `release tag`(like `1.5.0`/`1.5.0`) for the stable 
version. Use `latest` tag to experience the newest functions in development.
 
 #### 3.2 Download the binary tar tarball
 
 You could download the binary tarball from the download page of ASF site like 
this:
 ```bash
-# use the latest version, here is 1.3.0 for example
+# use the latest version, here is 1.5.0 for example
 wget 
https://downloads.apache.org/incubator/hugegraph/{version}/apache-hugegraph-incubating-{version}.tar.gz
 tar zxf *hugegraph*.tar.gz
 
@@ -122,7 +122,7 @@ The execution log is as follows:
 
 ```bash
 ......
-[INFO] Reactor Summary for hugegraph 1.3.0:
+[INFO] Reactor Summary for hugegraph 1.5.0:
 [INFO] 
 [INFO] hugegraph .......................................... SUCCESS [  2.405 s]
 [INFO] hugegraph-core ..................................... SUCCESS [ 13.405 s]
@@ -153,8 +153,8 @@ Of course, you should download the tarball of 
`HugeGraph-Toolchain` first.
 
 ```bash
 # download toolchain binary package, it includes loader + tool + hubble
-# please check the latest version (e.g. here is 1.3.0)
-wget 
https://downloads.apache.org/incubator/hugegraph/1.3.0/apache-hugegraph-toolchain-incubating-1.3.0.tar.gz
+# please check the latest version (e.g. here is 1.5.0)
+wget 
https://downloads.apache.org/incubator/hugegraph/1.5.0/apache-hugegraph-toolchain-incubating-1.5.0.tar.gz
 tar zxf *hugegraph-*.tar.gz
 
 # enter the tool's package
@@ -536,7 +536,7 @@ Set the environment variable `PRELOAD=true` when starting 
Docker in order to loa
 
 1. Use `docker run`
 
-    Use `docker run -itd --name=server -p 8080:8080 -e PRELOAD=true 
hugegraph/hugegraph:1.3.0`
+    Use `docker run -itd --name=server -p 8080:8080 -e PRELOAD=true 
hugegraph/hugegraph:1.5.0`
 
 2. Use `docker-compose`
 
@@ -546,7 +546,7 @@ Set the environment variable `PRELOAD=true` when starting 
Docker in order to loa
     version: '3'
       services:
         server:
-          image: hugegraph/hugegraph:1.3.0
+          image: hugegraph/hugegraph:1.5.0
           container_name: server
           environment:
             - PRELOAD=true

Reply via email to