Skip to content

Conversation

@bouk
Copy link
Contributor

@bouk bouk commented Jun 6, 2025

Fixes #4563, see that issue for details

@bouk bouk requested a review from a team as a code owner June 6, 2025 09:59
Copy link
Member

@emdneto emdneto left a comment

Choose a reason for hiding this comment

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

Does tests pass for newer versions?

@bouk
Copy link
Contributor Author

bouk commented Jun 10, 2025

@emdneto I think running the workflows requires approval, are you able to do that?

@sshishov
Copy link

sshishov commented Jun 10, 2025

I am not the maintainer or even contributor, but based on the upgrading flow to protobuf 5 there was a statement that OTEL desired to support only 1 version of protobuf, no? I hope it will be protobuf 6 soon 🎉

The statement appeared in this issue/comment: #3958 (comment)

@emdneto
Copy link
Member

emdneto commented Jun 10, 2025

I am not the maintainer or even contributor, but based on the upgrading flow to protobuf 5 there was a statement that OTEL desired to support only 1 version of protobuf, no? I hope it will be protobuf 6 soon 🎉

The statement appeared in this issue/comment: #3958 (comment)

Yes, I think this is the general agreement from the SIG.

@bouk I mean, update the test-requirements.txt and run the tests.

@xrmx xrmx moved this to Reviewed PR that needs fixing in @xrmx's Python PR digest Jun 11, 2025
@bouk
Copy link
Contributor Author

bouk commented Jun 12, 2025

@emdneto done, and the tests pass

@iblancasa
Copy link

Hi team, I don't know if you are aware of this https://nvd.nist.gov/vuln/detail/CVE-2025-4565

Copy link
Member

@emdneto emdneto left a comment

Choose a reason for hiding this comment

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

@bouk, we’ll need to create two test-requirements files—one with proto5 and one with proto6—and do the same for components that use opentelemetry-proto, such as exporters. Do you have bandwidth for this? Lmk if not, and I can push the changes to your branch to get this reviewed and merged.

@bouk
Copy link
Contributor Author

bouk commented Jun 19, 2025

I have time for this tomorrow, sure.

@aabmass
Copy link
Member

aabmass commented Jun 23, 2025

there was a statement that OTEL desired to support only 1 version of protobuf, no? I hope it will be protobuf 6 soon 🎉

The statement appeared in this issue/comment: #3958 (comment)

This is no longer relevant see my comment on #4639 (comment). This PR looks is the correct approach

@aabmass aabmass linked an issue Jun 23, 2025 that may be closed by this pull request
@aabmass
Copy link
Member

aabmass commented Jun 23, 2025

I have time for this tomorrow, sure.

Did you already start on this? If not, I already have a fix I can push.

@aabmass
Copy link
Member

aabmass commented Jun 24, 2025

@emdneto PTAL, I added separate tox targets for oldest+latest supported dependencies for opentelemetry-proto and opentelemetry-exporter-otlp-proto-grpc, generated with uv pip compile.

@xrmx
Copy link
Contributor

xrmx commented Jun 24, 2025

Please someone push a changelog :)

@xrmx xrmx moved this from Reviewed PR that needs fixing to Ready for review in @xrmx's Python PR digest Jun 24, 2025
@aabmass aabmass enabled auto-merge (squash) June 26, 2025 01:38
@aabmass aabmass disabled auto-merge June 26, 2025 14:05
@aabmass aabmass enabled auto-merge (squash) June 26, 2025 14:05
@aabmass aabmass merged commit 698f9a5 into open-telemetry:main Jun 26, 2025
471 of 472 checks passed
@github-project-automation github-project-automation bot moved this from Ready for review to Done in @xrmx's Python PR digest Jun 26, 2025
@jmezzera
Copy link

jmezzera commented Jul 3, 2025

Hello everyone! Is this scheduled for release? If so, is there an ETA?

I could take advantage of this fix

Thanks in advance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

9 participants