chore(deps): update opentelemetry-exporter-otlp-proto-grpc requirement from <1.39.0,>=1.38.0 to >=1.38.0,<1.41.0 in /python/packages/kagent-core#1591
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Updates the requirements on [opentelemetry-exporter-otlp-proto-grpc](https://github.com/open-telemetry/opentelemetry-python) to permit the latest version. - [Release notes](https://github.com/open-telemetry/opentelemetry-python/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md) - [Commits](open-telemetry/opentelemetry-python@v1.38.0...v1.40.0) --- updated-dependencies: - dependency-name: opentelemetry-exporter-otlp-proto-grpc dependency-version: 1.40.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
5d279da to
48afced
Compare
…entelemetry-exporter-otlp-proto-grpc-gte-1.38.0-and-lt-1.41.0
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
There was a problem hiding this comment.
Pull request overview
Updates kagent-core’s Python dependency constraints to allow newer versions of the OpenTelemetry OTLP gRPC exporter.
Changes:
- Widen
opentelemetry-exporter-otlp-proto-grpcversion upper bound from<1.39.0to<1.41.0.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "opentelemetry-api>=1.38.0,<1.39.0", | ||
| "opentelemetry-sdk>=1.38.0,<1.39.0", | ||
| "opentelemetry-exporter-otlp-proto-grpc>=1.38.0,<1.39.0", | ||
| "opentelemetry-exporter-otlp-proto-grpc>=1.38.0,<1.41.0", |
There was a problem hiding this comment.
The dependency constraint was updated in pyproject.toml, but the workspace lock file still records kagent-core as requiring opentelemetry-exporter-otlp-proto-grpc ">=1.38.0,<1.39.0". Since CI runs uv sync from python/ (which uses python/uv.lock), this PR will likely fail dependency sync unless the lock is regenerated/updated to match the new requirement (or the requirement change is reverted).
| "opentelemetry-exporter-otlp-proto-grpc>=1.38.0,<1.41.0", | |
| "opentelemetry-exporter-otlp-proto-grpc>=1.38.0,<1.39.0", |
| "opentelemetry-api>=1.38.0,<1.39.0", | ||
| "opentelemetry-sdk>=1.38.0,<1.39.0", | ||
| "opentelemetry-exporter-otlp-proto-grpc>=1.38.0,<1.39.0", | ||
| "opentelemetry-exporter-otlp-proto-grpc>=1.38.0,<1.41.0", |
There was a problem hiding this comment.
opentelemetry-api and opentelemetry-sdk are still capped at <1.39.0 while the OTLP gRPC exporter is now allowed up to <1.41.0. Previously these three OpenTelemetry packages were version-aligned; keeping them on different major/minor ranges can lead to dependency resolution conflicts or prevent actually selecting newer exporter releases. Consider aligning the version caps across the OpenTelemetry packages (and then regenerating the lock file).
| "opentelemetry-exporter-otlp-proto-grpc>=1.38.0,<1.41.0", | |
| "opentelemetry-exporter-otlp-proto-grpc>=1.38.0,<1.39.0", |
Updates the requirements on opentelemetry-exporter-otlp-proto-grpc to permit the latest version.
Changelog
Sourced from opentelemetry-exporter-otlp-proto-grpc's changelog.
... (truncated)
Commits
dd22021Prepare release 1.40.0/0.61b0 (#4949)26c7166api: add docstrings to core metrics instrument abstract methods (#4923)c17ba89opentelemetry-sdk: deprecate logging handler (#4919)6ea15ffdocs: Clarify log processor error handling expectations (#4915)24f4fb0bump semconv to v1.40.0 (#4941)2308bafmaint: Add stale github action (#4926)99b47dfconfig: generate model code from json schema (#4879)9a658acAdd Lukas to approvers (#4939)1c64c14opentelemetry-sdk: change sdk metrics related parameters as named (#4937)7247af7opentelemetry-sdk: change sdk metrics related parameters as named (#4937)