mergify: edit condition to fit 2.5 (#520)

Signed-off-by: huanghaoyuanhhy <haoyuan.huang@zilliz.com>
zilliztech · Jan 23, 2025 · e52d6b9 · e52d6b9
1 parent 3fdd33f
commit e52d6b9
Showing 1 changed file with 16 additions and 16 deletions.
diff --git a/.github/mergify.yml b/.github/mergify.yml
@@ -27,21 +27,21 @@ pull_request_rules:
   - name: Test passed for code changed-main
     conditions:
       - check-success=Unit test go
-      - check-success=Backup and restore cross version (docker-compose, standalone, standalone, 2.3-latest, master-latest)
-      - check-success=Backup and restore cross version (docker-compose, standalone, standalone, 2.3-latest, 2.4-latest)
       - check-success=Backup and restore cross version (docker-compose, standalone, standalone, 2.4-latest, master-latest)
-      - check-success=Backup and restore after upgrade (docker-compose, standalone, standalone, v2.4.17, master-latest)
-      - check-success=Backup and restore after upgrade (docker-compose, standalone, standalone, v2.4.17, 2.4-latest)
-      - check-success=Backup and restore after upgrade (docker-compose, standalone, standalone, 2.4-latest, master-latest)
+      - check-success=Backup and restore cross version (docker-compose, standalone, standalone, 2.4-latest, v2.5.4)
+      - check-success=Backup and restore cross version (docker-compose, standalone, standalone, v2.5.4, master-latest)
+      - check-success=Backup and restore after upgrade (docker-compose, standalone, standalone, v2.4.21, master-latest)
+      - check-success=Backup and restore after upgrade (docker-compose, standalone, standalone, v2.4.21, v2.5.4)
+      - check-success=Backup and restore after upgrade (docker-compose, standalone, standalone, v2.5.4, master-latest)
       - check-success=Backup and restore cli (docker-compose, standalone, standalone, master-latest)
       - check-success=Backup and restore with rbac config (helm, standalone, master-latest)
       - check-success=Backup and restore api (docker-compose, standalone, master-latest, L0)
       - check-success=Backup and restore api (docker-compose, standalone, master-latest, L1)
       - check-success=Backup and restore api (docker-compose, standalone, master-latest, L2)
       - check-success=Backup and restore api (docker-compose, standalone, master-latest, MASTER)
-      - check-success=Backup and restore api (docker-compose, standalone, 2.4-latest, L0)
-      - check-success=Backup and restore api (docker-compose, standalone, 2.4-latest, L1)
-      - check-success=Backup and restore api (docker-compose, standalone, 2.4-latest, L2)
+      - check-success=Backup and restore api (docker-compose, standalone, v2.5.4, L0)
+      - check-success=Backup and restore api (docker-compose, standalone, v2.5.4, L1)
+      - check-success=Backup and restore api (docker-compose, standalone, v2.5.4, L2)
     actions:
       label:
         add:
@@ -115,21 +115,21 @@ pull_request_rules:
       - files~=^(?=.*((\.(go|h|cpp)|CMakeLists.txt))).*$
       - or:
         - check-success!=Unit test go
-        - check-success!=Backup and restore cross version (docker-compose, standalone, standalone, 2.3-latest, master-latest)
-        - check-success!=Backup and restore cross version (docker-compose, standalone, standalone, 2.3-latest, 2.4-latest)
         - check-success!=Backup and restore cross version (docker-compose, standalone, standalone, 2.4-latest, master-latest)
-        - check-success!=Backup and restore after upgrade (docker-compose, standalone, standalone, v2.4.17, master-latest)
-        - check-success!=Backup and restore after upgrade (docker-compose, standalone, standalone, v2.4.17, 2.4-latest)
-        - check-success!=Backup and restore after upgrade (docker-compose, standalone, standalone, 2.4-latest, master-latest)
+        - check-success!=Backup and restore cross version (docker-compose, standalone, standalone, 2.4-latest, v2.5.4)
+        - check-success!=Backup and restore cross version (docker-compose, standalone, standalone, v2.5.4, master-latest)
+        - check-success!=Backup and restore after upgrade (docker-compose, standalone, standalone, v2.4.21, master-latest)
+        - check-success!=Backup and restore after upgrade (docker-compose, standalone, standalone, v2.4.21, v2.5.4)
+        - check-success!=Backup and restore after upgrade (docker-compose, standalone, standalone, v2.5.4, master-latest)
         - check-success!=Backup and restore cli (docker-compose, standalone, standalone, master-latest)
         - check-success!=Backup and restore with rbac config (helm, standalone, master-latest)
         - check-success!=Backup and restore api (docker-compose, standalone, master-latest, L0)
         - check-success!=Backup and restore api (docker-compose, standalone, master-latest, L1)
         - check-success!=Backup and restore api (docker-compose, standalone, master-latest, L2)
         - check-success!=Backup and restore api (docker-compose, standalone, master-latest, MASTER)
-        - check-success!=Backup and restore api (docker-compose, standalone, 2.4-latest, L0)
-        - check-success!=Backup and restore api (docker-compose, standalone, 2.4-latest, L1)
-        - check-success!=Backup and restore api (docker-compose, standalone, 2.4-latest, L2)
+        - check-success!=Backup and restore api (docker-compose, standalone, v2.5.4, L0)
+        - check-success!=Backup and restore api (docker-compose, standalone, v2.5.4, L1)
+        - check-success!=Backup and restore api (docker-compose, standalone, v2.5.4, L2)
     actions:
       label:
         remove: