Skip to content
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.

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

bump ovs-cni to v0.37.0 #1951

Merged
merged 1 commit into from
Jan 2, 2025
Merged

bump ovs-cni to v0.37.0 #1951

merged 1 commit into from
Jan 2, 2025

Conversation

kubevirt-bot
Copy link
Collaborator

bump ovs-cni to v0.37.0
Executed by Bumper script

bump ovs-cni to v0.37.0

Signed-off-by: CNAO Bump Bot <[email protected]>
@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Dec 16, 2024
@oshoval
Copy link
Collaborator

oshoval commented Dec 17, 2024

@RamLavi
Copy link
Collaborator

RamLavi commented Dec 17, 2024

/lgtm
/approve

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Dec 17, 2024
@kubevirt-bot
Copy link
Collaborator Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RamLavi

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

The pull request process is described 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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 17, 2024
@RamLavi
Copy link
Collaborator

RamLavi commented Dec 18, 2024

/retest
known flake

@oshoval
Copy link
Collaborator

oshoval commented Jan 2, 2025

/retest

@kubevirt-bot kubevirt-bot merged commit 856c0b3 into main Jan 2, 2025
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants