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

dependency update to go 1.22.7 #5969

Open
codeboten opened this issue Nov 12, 2024 · 5 comments
Open

dependency update to go 1.22.7 #5969

codeboten opened this issue Nov 12, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@codeboten
Copy link
Contributor

Description

Updating the packages to the latest version of the go SDK libraries and saw that the minimum version of go was bumped from 1.22 to 1.22.7 in the dependency change 5e9da3a. Is this intentional? It's causing the collector to need to bump its minimum version as well

Expected behavior

Expected to be able to bump otel-go dependencies without requiring a bump in minimum go version

@codeboten codeboten added the bug Something isn't working label Nov 12, 2024
@pellared
Copy link
Member

pellared commented Nov 12, 2024

I do see requiring to bump a patch version of Go as a bug. We are still supporting the same versions of Go as currently supported by the Go team. I find the changes in https://github.com/grpc/grpc-go/releases/tag/v1.68.0 quite important.

From https://github.com/open-telemetry/opentelemetry-go?tab=readme-ov-file#compatibility:

OpenTelemetry-Go ensures compatibility with the current supported versions of the Go language:

Each major Go release is supported until there are two newer major releases. For example, Go 1.5 was supported until the Go 1.7 release, and Go 1.6 was supported until the Go 1.8 release.

@codeboten
Copy link
Contributor Author

There was a change to revert that bump grpc/grpc-go@3db86e2

@pellared
Copy link
Member

There was a change to revert that bump grpc/grpc-go@3db86e2

I still do not see requiring to patch Go as a bug. However, if there would be a new go-grpc release that reverts the Go requirements and there will be a considerable pushback to do the same here, then I think we can consider also doing a patch release for OTel Go as well.

@codeboten
Copy link
Contributor Author

@pellared is updating the requirement to 1.22.7 not breaking the requirement to support the two newest versions?

Each major Go release is supported until there are two newer major releases. For example, Go 1.5 was supported until the Go 1.7 release, and Go 1.6 was supported until the Go 1.8 release.

If that's not the case, then I agree this is not a bug. In the collector we tend to support the lowest patch version of the last 2 go releases

@pellared
Copy link
Member

Yes. That is my interpretation. However, I added this issue as a topic to next SIG meeting agenda as I do (or at least try to) not blindly trust my own judgement.

@github-project-automation github-project-automation bot moved this to Needs triage in Go: Triage Nov 21, 2024
@MrAlias MrAlias moved this from Needs triage to Low priority in Go: Triage Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Low priority
Development

No branches or pull requests

2 participants