Skip to content

enhance: bump knowhere to v3.0.8 - #52631

Closed
foxspy wants to merge 1 commit into
milvus-io:3.0from
foxspy:update-knowhere-v3.0.8
Closed

enhance: bump knowhere to v3.0.8#52631
foxspy wants to merge 1 commit into
milvus-io:3.0from
foxspy:update-knowhere-v3.0.8

enhance: bump knowhere to v3.0.8

d5db8fa
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Aug 24, 2026 in 3s

4 rules match and 29 potential rules

Rule: Add needs-dco label when DCO check failed (comment, label)

  • -status-success=DCO
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

✅ Rule: Add dco-passed label when DCO check passed (label)

  • status-success=DCO
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Test passed for code changed on 3.0 branch (label)

  • any of:
    • status-success=ci-v2/build-ut-cov
  • any of:
    • status-success=ci-v2/e2e-amd
  • any of:
    • status-success=ci-v2/go-sdk
    • status-success=go-sdk
    • status-success=milvus-sdk-go
  • base=3.0

Rule: Test passed for tests changed on 3.0 (label)

  • -files~=^(?!tests\/python_client).+
  • any of:
    • status-success=ci-v2/e2e-amd
  • base=3.0

Rule: Test passed for docs changed only (label)

  • -files~=^(?!.*\.(md)).*$
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Test passed for non source code changed on 3.0 (label)

  • -files~=^(?=.*((\.(rs|go|h|cpp)|go.sum|go.mod|CMakeLists.txt|conanfile\.*))).*$
  • any of:
    • status-success=ci-v2/e2e-amd
  • base=3.0

Rule: Test passed for go unittest code changed on 3.0 (label)

  • -files~=^(?!(client|internal|pkg|tests)\/.*_test\.go).*$
  • any of:
    • status-success=ci-v2/build-ut-cov
  • base=3.0

Rule: Test passed for mergify changed (label)

  • -files~=^(?!\.github\/mergify\.yml).*$
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Test passed for title skip e2e when no source code changed (label)

  • -files~=^(?=.*((\.(rs|go|h|cpp)|go.sum|go.mod|CMakeLists.txt|conanfile\.*))).*$
  • title~=\[skip e2e\]
  • label=kind/enhancement
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Test passed for skip e2e when source code changed on 3.0 (label)

  • title~=\[skip e2e\]
  • any of:
    • status-success=ci-v2/build-ut-cov
  • base=3.0
  • files~=^(?=.*((\.(rs|go|h|cpp)|go.sum|go.mod|CMakeLists.txt|conanfile\.*))).*$

Rule: Remove ci-passed when E2E test not success for tests changed on 3.0 (label)

  • -files~=^(?!tests\/python_client).+
  • label=ci-passed
  • -status-success=ci-v2/e2e-amd
  • base=3.0
  • label!=manual-pass

Rule: Remove stale ci-passed when required CI is not successful on 3.0 branch (label)

  • label=ci-passed
  • base=3.0
  • files~=^(?=.*((\.(rs|go|h|cpp)|go.sum|go.mod|CMakeLists.txt|conanfile\.*))).*$
  • label!=manual-pass
  • any of:
    • -status-success=ci-v2/build-ut-cov
    • all of:
      • -title~=\[skip e2e\]
      • files~=^(?!(client|internal|pkg|tests)\/.*_test\.go).*$
      • not:
        • any of:
          • status-success=ci-v2/go-sdk
          • status-success=go-sdk
          • status-success=milvus-sdk-go
    • all of:
      • -status-success=ci-v2/e2e-amd
      • -title~=\[skip e2e\]
      • files~=^(?!(client|internal|pkg|tests)\/.*_test\.go).*$

Rule: Blocking PR if missing a related issue or doesn't have kind/enhancement label (comment, label)

  • all of:
    • -body~=\#[0-9]{1,6}(\s+|$)
    • -body~=https://github.com/milvus-io/milvus/issues/[0-9]{1,6}(\s+|$)
  • any of:
    • label=kind/bug
    • label=kind/feature
    • all of:
      • any of:
        • label=size/L
        • label=size/XL
        • label=size/XXL
      • label=kind/enhancement
  • -label=kind/doc
  • -label=kind/test
  • -title~=\[automated\]
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

✅ Rule: Dismiss block label if related issue be added into PR (label)

  • all of:
    • any of:
      • base=3.0
      • base=master
      • base~=^2(\.\d+){1,2}$
    • any of:
      • body~=\#[0-9]{1,6}(\s+|$)
      • body~=https://github.com/milvus-io/milvus/issues/[0-9]{1,6}(\s+|$)

✅ Rule: Blocking PR if missing a related master PR or doesn't have kind/branch-feature label (comment, label)

  • -label=kind/branch-feature
  • -title~=\[automated\]
  • all of:
    • -body~=https://github.com/milvus-io/milvus/pull/[0-9]{1,6}(\s+|$)
    • -body~=pr\:\ \#[0-9]{1,6}(\s+|$)
  • any of:
    • base=3.0
    • base~=^2(\.\d+){1,2}$

Rule: Dismiss block label if related pr be added into PR (label)

  • any of:
    • body~=https://github.com/milvus-io/milvus/pull/[0-9]{1,6}(\s+|$)
    • body~=pr\:\ \#[0-9]{1,6}(\s+|$)
    • label=kind/branch-feature
  • any of:
    • base=3.0
    • base~=^2(\.\d+){1,2}$

Rule: Dismiss block label if automated create PR (label)

  • title~=\[automated\]
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Blocking PR if feat PR missing design doc (comment, label)

  • any of:
    • label=kind/feature
    • title~=^feat:
  • -body~=(^|\s)docs/design-docs/design_docs/[^\s]+\.md
  • -files~=^docs/design-docs/design_docs/.*\.md$
  • -title~=\[automated\]
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Dismiss block label if design doc is provided (label)

  • label=do-not-merge/missing-design-doc
  • any of:
    • body~=(^|\s)docs/design-docs/design_docs/[^\s]+\.md
    • files~=^docs/design-docs/design_docs/.*\.md$
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add 'do-not-merge/invalid-pr-format' label for invalid PR titles (comment, label)

  • any of:
    • -title~=^(feat:|enhance:|fix:|test:|doc:|auto:|build\(deps\):|\[automated\])
    • body=^$
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Remove 'do-not-merge/invalid-pr-format' label for valid PRs (label)

  • label=do-not-merge/invalid-pr-format
  • -body=^$
  • title~=^(feat:|enhance:|fix:|test:|doc:|auto:|build\(deps\):|\[automated\])
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add comment when cpu-e2e job failed (comment)

  • check-failure=cpu-e2e
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add comment when go-sdk check failed (comment)

  • check-failure=go-sdk
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add comment when cpp-unit-test check failed (comment)

  • check-failure=cpp-unit-test
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add comment when go-unit-test check failed (comment)

  • check-failure=go-unit-test
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add comment when integration-test check failed (comment)

  • check-failure=integration-test
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Add comment when code checker or ut failed -master (comment)

  • any of:
    • check-failure=Build and test AMD64 Ubuntu 20.04
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Label bug fix PRs (label)

  • title~=^fix:
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Label feature PRs (label)

  • title~=^feat:
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

✅ Rule: Label enhancement PRs (label)

  • title~=^enhance:
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Label test PRs (label)

  • title~=^test:
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Label doc PRs (label)

  • title~=^doc:
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

Rule: Assign the 'lgtm' and 'approved' labels following the successful testing of the 'Update Knowhere Commit' (label)

  • label=ci-passed
  • title~=Update Knowhere Commit
  • any of:
    • base=3.0
    • base=master
    • base~=^2(\.\d+){1,2}$

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


12 not applicable rules

Rule: Test passed for code changed on master (label)

  • base=master
  • status-success=ci-v2/build-ut-cov
  • any of:
    • status-success=ci-v2/go-sdk
    • status-success=go-sdk
    • status-success=milvus-sdk-go
  • any of:
    • status-success=ci-v2/e2e-default
    • status-success=cpu-e2e

Rule: Test passed for code changed on 2.* branch (label)

  • base~=^2(\.\d+){1,2}$
  • any of:
    • status-success=Build and test AMD64 Ubuntu 22.04
    • status-success=ci-v2/build
  • any of:
    • status-success=UT for Cpp
    • status-success=ci-v2/ut-cpp
    • status-success=cpp-unit-test
  • any of:
    • status-success=UT for Go
    • status-success=ci-v2/ut-go
    • status-success=go-unit-test
  • any of:
    • status-success=Integration Test
    • status-success=ci-v2/integration-test
    • status-success=integration-test
  • any of:
    • status-success=ci-v2/e2e-default
    • status-success=cpu-e2e
  • any of:
    • status-success=Code Checker AMD64 Ubuntu 22.04
    • status-success=ci-v2/code-check

Rule: Test passed for tests changed (label)

  • -files~=^(?!tests\/python_client).+
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$
  • any of:
    • status-success=ci-v2/e2e-default
    • status-success=cpu-e2e

Rule: Test passed for non rust go or c++ code changed (label)

  • -files~=^(?=.*((\.(rs|go|h|cpp)|go.sum|go.mod|CMakeLists.txt|conanfile\.*))).*$
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$
  • any of:
    • status-success=ci-v2/e2e-default
    • status-success=cpu-e2e

Rule: Test passed for go unittest code changed on master (label)

  • -files~=^(?!(client|internal|pkg|tests)\/.*_test\.go).*$
  • base=master
  • status-success=ci-v2/build-ut-cov

Rule: Test passed for go unittest code changed on 2.* branch (label)

  • -files~=^(?!(client|internal|pkg|tests)\/.*_test\.go).*$
  • base~=^2(\.\d+){1,2}$
  • any of:
    • status-success=Build and test AMD64 Ubuntu 22.04
    • status-success=ci-v2/build
  • any of:
    • status-success=Code Checker AMD64 Ubuntu 22.04
    • status-success=ci-v2/code-check
  • any of:
    • status-success=UT for Go
    • status-success=ci-v2/ut-go
    • status-success=go-unit-test

Rule: Test passed for skip e2e when source code changed on master (label)

  • base=master
  • status-success=ci-v2/build-ut-cov
  • title~=\[skip e2e\]
  • files~=^(?=.*((\.(rs|go|h|cpp)|go.sum|go.mod|CMakeLists.txt|conanfile\.*))).*$

Rule: Test passed for skip e2e when source code changed on 2.* branch (label)

  • base~=^2(\.\d+){1,2}$
  • title~=\[skip e2e\]
  • any of:
    • status-success=Build and test AMD64 Ubuntu 22.04
    • status-success=ci-v2/build
  • any of:
    • status-success=UT for Cpp
    • status-success=ci-v2/ut-cpp
    • status-success=cpp-unit-test
  • any of:
    • status-success=UT for Go
    • status-success=ci-v2/ut-go
    • status-success=go-unit-test
  • any of:
    • status-success=Integration Test
    • status-success=ci-v2/integration-test
    • status-success=integration-test
  • any of:
    • status-success=Code Checker AMD64 Ubuntu 22.04
    • status-success=ci-v2/code-check
  • files~=^(?=.*((\.(rs|go|h|cpp)|go.sum|go.mod|CMakeLists.txt|conanfile\.*))).*$

Rule: Remove ci-passed when E2E test not success for tests changed (label)

  • -files~=^(?!tests\/python_client).+
  • label=ci-passed
  • any of:
    • base=master
    • base~=^2(\.\d+){1,2}$
  • label!=manual-pass
  • not:
    • any of:
      • status-success=ci-v2/e2e-default
      • status-success=cpu-e2e

Rule: Remove stale ci-passed when required CI is not successful on master (label)

  • base=master
  • label=ci-passed
  • files~=^(?=.*((\.(rs|go|h|cpp)|go.sum|go.mod|CMakeLists.txt|conanfile\.*))).*$
  • label!=manual-pass
  • any of:
    • -status-success=ci-v2/build-ut-cov
    • all of:
      • -title~=\[skip e2e\]
      • files~=^(?!(client|internal|pkg|tests)\/.*_test\.go).*$
      • not:
        • any of:
          • status-success=ci-v2/go-sdk
          • status-success=go-sdk
          • status-success=milvus-sdk-go
    • all of:
      • -title~=\[skip e2e\]
      • files~=^(?!(client|internal|pkg|tests)\/.*_test\.go).*$
      • not:
        • any of:
          • status-success=ci-v2/e2e-default
          • status-success=cpu-e2e

Rule: Remove stale ci-passed when required CI is not successful on 2.* branch (label)

  • base~=^2(\.\d+){1,2}$
  • label=ci-passed
  • files~=^(?=.*((\.(rs|go|h|cpp)|go.sum|go.mod|CMakeLists.txt|conanfile\.*))).*$
  • label!=manual-pass
  • any of:
    • all of:
      • files~=^(?!(client|internal|pkg|tests)\/.*_test\.go).*$
      • not:
        • any of:
          • status-success=UT for Cpp
          • status-success=ci-v2/ut-cpp
          • status-success=cpp-unit-test
    • all of:
      • files~=^(?!(client|internal|pkg|tests)\/.*_test\.go).*$
      • not:
        • any of:
          • status-success=Integration Test
          • status-success=ci-v2/integration-test
          • status-success=integration-test
    • all of:
      • -title~=\[skip e2e\]
      • files~=^(?!(client|internal|pkg|tests)\/.*_test\.go).*$
      • not:
        • any of:
          • status-success=ci-v2/e2e-default
          • status-success=cpu-e2e
    • not:
      • any of:
        • status-success=Build and test AMD64 Ubuntu 22.04
        • status-success=ci-v2/build
    • not:
      • any of:
        • status-success=UT for Go
        • status-success=ci-v2/ut-go
        • status-success=go-unit-test
    • not:
      • any of:
        • status-success=Code Checker AMD64 Ubuntu 22.04
        • status-success=ci-v2/code-check

Rule: Add comment when code checker or ut failed -2.2.* (comment)

  • base~=^2(\.\d+){1,2}$
  • any of:
    • check-failure=Build and test AMD64 Ubuntu 20.04
Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com