cluster-api-provider-packet icon indicating copy to clipboard operation
cluster-api-provider-packet copied to clipboard

✨ Upgrade go version to 1.19

Open moadqassem opened this issue 3 years ago • 7 comments
trafficstars

What this PR does / why we need it: Upgrade go version to 1.19

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 https://github.com/kubernetes-sigs/cluster-api-provider-packet/issues/411

moadqassem avatar Sep 28 '22 10:09 moadqassem

CLA Signed

The committers listed above are authorized under a signed CLA.

  • :white_check_mark: login: moadqassem / name: Moath Qasim (fbe6ca9ee99364f1750bdc08c8c0bdf2e4b42e1b)

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: moadqassem Once this PR has been reviewed and has the lgtm label, please assign enxebre for approval by writing /assign @enxebre in a comment. For more information see:The Kubernetes Code Review Process.

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

k8s-ci-robot avatar Sep 28 '22 10:09 k8s-ci-robot

Welcome @moadqassem!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-packet 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-provider-packet has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. :smiley:

k8s-ci-robot avatar Sep 28 '22 10:09 k8s-ci-robot

@cprivitere PTAL :)

moadqassem avatar Sep 29 '22 08:09 moadqassem

make verify and make lint builds are failing.

We may need to update to a later golangci-lint and disable any linters that are not go 1.19 ready.

@displague So I ran the verify and lint locally and seems to be working now, can you please rerun the workflow?

moadqassem avatar Sep 29 '22 11:09 moadqassem

Locally run through the verify GH action:

./hack/verify-boilerplate.sh
go mod tidy
cd test/e2e; go mod tidy
make generate-go

make generate-go is failing over what appears to be go syntax.

displague avatar Oct 04 '22 16:10 displague

I really don't think this is going to work until we incorporate the cluster-api 1.2 updates. That's where they added 1.18 support.

cprivitere avatar Oct 04 '22 19:10 cprivitere

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jan 02 '23 19:01 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Feb 01 '23 20:02 k8s-triage-robot

/remove-lifecycle rotten

cprivitere avatar Feb 01 '23 20:02 cprivitere

I'm going to be incorporating these into #530 so I'm going to close this one. Thank you @moadqassem

cprivitere avatar Mar 22 '23 20:03 cprivitere