Skip to content

test: Increase PyMilvus version to 2.5.17rc3 for 2.5 branch #45213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: 2.5
Choose a base branch
from
Open

test: Increase PyMilvus version to 2.5.17rc3 for 2.5 branch #45213

wants to merge 1 commit into from

Conversation

@XuanYang-cn
Copy link
Contributor

Automated daily bump from pymilvus 2.5 branch. Updates tests/python_client/requirements.txt.
@XuanYang-cn
test: Increase PyMilvus version to 2.5.17rc3
e35c082 
Signed-off-by: XuanYang-cn <xuan.yang@zilliz.com>
@sre-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: XuanYang-cn
To complete the pull request process, please assign zhengbuqian after the PR has been reviewed.
You can assign the PR to them by writing /assign @zhengbuqian in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@sre-ci-robot sre-ci-robot added sig/testing size/XS Denotes a PR that changes 0-9 lines. labels Nov 1, 2025
@mergify
Copy link
Contributor

mergify bot commented Nov 1, 2025

@XuanYang-cn Please associate the related pr of master to the body of your Pull Request. (eg. "pr: #")
@sre-ci-robot
Copy link
Contributor

[ci-v2-notice]
Notice: We are gradually rolling out the new ci-v2 system.

  • Legacy CI jobs remain unaffected, you can just ignore ci-v2 if you don't want to run it.
  • Additional "ci-v2/*" checkers will run for this PR to ensure the new ci-v2 system is working as expected.
  • For tests that exist in both v1 and v2, passing in either system is considered PASS.

To rerun ci-v2 checks, comment with:

  • /ci-rerun-code-check // for ci-v2/code-check
  • /ci-rerun-build // for ci-v2/build
  • /ci-rerun-ut-integration // for ci-v2/ut-integration
  • /ci-rerun-ut-go // for ci-v2/ut-go
  • /ci-rerun-ut-cpp // for ci-v2/ut-cpp
  • /ci-rerun-ut // for all ci-v2/ut-integration, ci-v2/ut-go, ci-v2/ut-cpp
  • /ci-rerun-e2e-arm // for ci-v2/e2e-arm

If you have any questions or requests, please contact @zhikunyao.
@sre-ci-robot sre-ci-robot added do-not-merge/need-merge-master-first any pr merge to release branch need to merge master first do-not-merge/need-milestone generate by v2-label-manager labels Nov 1, 2025
@sre-ci-robot
Copy link
Contributor

[INFO] PR Label Summary by Default
[WARNING] No dependent PR reference found

  • Target branch '2.5' requires a PR merged to master first
  • Please add reference in format 'pr: #number'

[WARNING] Milestone not set

You can set milestone by commenting:
/set-milestone
Example:
/set-milestone 2.5.0

Use /refresh-label to update related check and label manually
@mergify
Copy link
Contributor

mergify bot commented Nov 1, 2025

@XuanYang-cn cpu-e2e job failed, comment /run-cpu-e2e can trigger the job again.
@XuanYang-cn
Copy link
Contributor Author

/run-cpu-e2e
@mergify
Copy link
Contributor

mergify bot commented Nov 3, 2025

@XuanYang-cn cpu-e2e job failed, comment /run-cpu-e2e can trigger the job again.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/test dco-passed DCO check passed. do-not-merge/missing-related-pr do-not-merge/need-merge-master-first any pr merge to release branch need to merge master first do-not-merge/need-milestone generate by v2-label-manager kind/test sig/testing size/XS Denotes a PR that changes 0-9 lines.

2 participants

@XuanYang-cn @sre-ci-robot