Skip to content

Release non-beta versions of the azure-monitor-opentelemetry-exporter and azure-core-tracing-opentelemetry packages #44309

@12rambau

Description

@12rambau

Is your feature request related to a problem? Please describe.
We use the following python libs in our pipelining system:

  • azure-monitor-opentelemetry-exporter
  • azure-core-tracing-opentelemetry

The recent bug with open-telemetry made us realise that we are using a hard pin for dependecies as it's the only way to reach the latest version that is systematically deployed as beta.
Could you consider releasing a non-beta version so pip/uv can catch up the latest version spcifically when you do patch releases like this one

Describe the solution you'd like
I would appreciate if the next release of the lib could be following the sementic numbering i.e.e 1.1.0 for the next one I guess

Describe alternatives you've considered
We currently hard pinning this everywhere but it makes it super weak to any change that require propagations, this is a typical exemple that put down our entire data integration system for several hours.

Metadata

Metadata

Assignees

Labels

MonitorMonitor, Monitor Ingestion, Monitor QueryService AttentionWorkflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions