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

Update golang to 1.19.4 and kubevirtci to latest #156

Merged
merged 1 commit into from
Jan 12, 2023

Conversation

awels
Copy link
Member

@awels awels commented Jan 11, 2023

Signed-off-by: Alexander Wels [email protected]

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

Using golang 1.19.4

@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 Jan 11, 2023
@awels awels force-pushed the update_kubevirtci_golang_119 branch 5 times, most recently from 628986f to 12ab67b Compare January 12, 2023 13:11
@awels awels force-pushed the update_kubevirtci_golang_119 branch from 12ab67b to 16ed3a2 Compare January 12, 2023 13:29
@@ -14,13 +14,13 @@

.PHONY: cluster-up cluster-down cluster-sync cluster-clean

KUBEVIRT_PROVIDER?=k8s-1.23
KUBEVIRT_PROVIDER?=k8s-1.25
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

may want 1.26 now, kubevirt/kubevirt already has required lanes
plus pretty sure main==1.26 at this point

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know 1.26 is available, I wanted to stick to 1.25 for no particular reason other than that I am not 100% sure 1.26 is stable yet.

@ShellyKa13
Copy link
Contributor

/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Jan 12, 2023
@akalenyu
Copy link
Contributor

/lgtm

@awels
Copy link
Member Author

awels commented Jan 12, 2023

/approve

@kubevirt-bot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: awels

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 Jan 12, 2023
@kubevirt-bot kubevirt-bot merged commit d5177df into kubevirt:main Jan 12, 2023
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/XXL
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants