fix(deps): unblock cryptography >=48, OTel 1.44, protovalidate 0.15 - #314
Merged
Merged
Conversation
jeanscherf
reviewed
Sep 8, 2026
jeanscherf
previously approved these changes
Sep 8, 2026
ArthurTonial
marked this pull request as ready for review
September 8, 2026 14:57
NicoleMGomes
approved these changes
Sep 8, 2026
Contributor
cassiofariasmachado
approved these changes
Sep 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Description
Fixes three dependency issues introduced by the version pinning in 0.49.2 that are blocking consumers from installing or running the SDK:
cryptographyHIGH vulnerability (GHSA-537c-gmf6-5ccf)Widened
cryptographyfrom>=46.0.3,<47to>=48.0.1,<51. All versions below 48 bundle a vulnerable OpenSSL and are flagged HIGH by SAP Security Validation.protovalidate/protobufruntime crashThe 0.49.2 pin of
protobuf>=6.0.0,<7alongsideprotovalidate<1causes a hard crash at service startup:AttributeError: 'google._upb._message.FieldDescriptor' object has no attribute 'label'
File ".../protovalidate/internal/rules.py", line 1060
protovalidate 0.xcallsFieldDescriptor.labelwhich was removed in protobuf 6.0. The metadata omission (protobuf>=5, no upper bound) means pip resolves the conflict silently and the crash only surfaces at runtime.Fix: downgrade the
protobufconstraint to>=5.29.5,<6and regenerate all bundled_pb2.pyfiles with the matchingbuf.build/protocolbuffers/python:v29.3plugin. The<6cap is safe — no dependency in the tree requires protobuf 6.OTel 1.44.0 blocked
The
~=1.43.0pin onopentelemetry-exporter-*resolved to>=1.43.0, ==1.43.*, excluding 1.44.0. Consumers already on 1.44.0 were forced to downgrade. Updated exporters to~=1.44.0and instrumentation packages to~=0.65b0.Type of Change
How to Test
uv synccryptography≥ 48.0.1protobuf5.29.xopentelemetry-sdk1.44.xuv run python -c "from sap_cloud_sdk.core.auditlog_ng import client"uv run pytest tests/ -m "not integration and not aicore"Checklist
Breaking Changes
None. All constraint changes either widen an existing range or restore a prior lower major version.
Additional Notes
buf.gen.yamlwas updated from pluginv33.5tov29.3to match the newprotobuf<6runtime. All four generated_pb2.py/_pb2.pyifiles undersrc/buf/andsrc/sap_cloud_sdk/core/auditlog_ng/gen/were regenerated accordingly. Future proto regeneration must use a protobuf 5.x plugin untilprotovalidateis migrated to 2.x.