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.

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

Should we move to go 1.16 / 1.17 ? #2579

Closed
lburgazzoli opened this issue Aug 18, 2021 · 3 comments · Fixed by #2655
Closed

Should we move to go 1.16 / 1.17 ? #2579

lburgazzoli opened this issue Aug 18, 2021 · 3 comments · Fixed by #2655
Labels
kind/question Further information is requested

Comments

@lburgazzoli
Copy link
Contributor

No description provided.

@lburgazzoli lburgazzoli added the kind/question Further information is requested label Aug 18, 2021
@astefanutti
Copy link
Member

Based on my experience, I think it's safer to transitively follow the Golang version that is used by the current k8s version Camel K depends on.

@lburgazzoli
Copy link
Contributor Author

Seems to be 1.16 from 1.21 right ?

@astefanutti
Copy link
Member

Right, however we still depend on k8s 1.20, as we are held back by Knative that still depends on it, and cannot upgrade to 1.21 due to breaking changes. The path of least resistance would be to wait until Knative upgrade to 1.21, then we can upgrade to it, and to Golang 1.16 along with it.

@squakez squakez mentioned this issue Aug 19, 2021
Merged
@astefanutti astefanutti mentioned this issue Sep 22, 2021
Merged
@chenrui333 chenrui333 mentioned this issue Jan 2, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/question Further information is requested
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(build): Upgrade Go dependencies
2 participants
@astefanutti @lburgazzoli