chore: update meta-service compatibility doc

Author: drmingdrmer

docs/en/guides/10-deploy/02-upgrade/10-compatibility.md

@@ -141,7 +141,8 @@ For example, Current Version is 1.2.306 upgrade to 1.2.312:
 |:--------------------|:-------------------------|
 | [0.9.41,   1.2.212) | [0.9.41,  1.2.212)       |
 | [1.2.212,  1.2.479) | [0.9.41,  1.2.479)       |
-| [1.2.479, +∞)       | [1.2.288, +∞)            |
+| [1.2.479,  1.2.655) | [1.2.288, 1.2.655)       |
+| [1.2.655, +∞)       | [1.2.288, +∞)            |
 
 
 - `1.2.53` Incompatible, rolling upgrade is allowed without snapshot transmitting.
@@ -165,11 +166,21 @@ For example, Current Version is 1.2.306 upgrade to 1.2.312:
 - `1.2.552` 2024-07-02 Introduce on-disk `V003`, using `rotbl` format snapshot,
   which is compatible with `V002`. The oldest compatible version is `1.2.288`(`1.2.212~1.2.287` are removed).
 
+- `1.2.655` 2024-11-11 Introduce on-disk `V004`, using WAL based Raft log storage,
+  which is compatible with `V002`. The oldest compatible version is `1.2.288`(`1.2.212~1.2.287` are removed).
+
 
 ## Compatibility of databend-meta on-disk data
 
 The on-disk data of Databend-meta evolves over time while maintaining backward compatibility.
 
+| DataVersion | Databend-version | Min Compatible with |
+|:------------|:-----------------|:--------------------|
+| V004        | 1.2.655          | V002                | 
+| V003        | 1.2.547          | V002                | 
+| V002        | 1.2.53           | V001                | 
+| V001        | 1.1.40           | V0                  |
+
 ### Identifying the versions
 
 Upon startup, Databend-meta will display the on-disk data version: