opentelemetry-opamp-client 0.5b0: Pure Python UUIDv7 Replaces uuid-utils

The maintainers of opentelemetry-python-contrib published opentelemetry-opamp-client 0.5b0 on October 26, 2026. It is a small dependency release: the OpAMP client no longer uses uuid-utils, and the maintainers replaced it with a pure Python UUIDv7 backport taken from CPython.

The full notes and package details are on the GitHub release page.

Why the UUIDv7 change matters

The change came in PR #5207. Before this release, the OpAMP client pulled in uuid-utils to generate UUIDv7 values. UUIDv7 embeds a timestamp, which suits the sort of message and instance identifiers the OpAMP protocol uses. But uuid-utils ships native extensions, and a native dependency brings the usual costs: build steps for platforms without prebuilt wheels, compiler requirements in CI, and a supply chain surface that pure Python does not have.

The replacement is a backport of the UUIDv7 implementation from CPython itself. The behavior stays the same for callers. The dependency list shrinks by one compiled package. If you pin opentelemetry-opamp-client==0.5b0 in environments where installing native wheels is awkward, such as constrained base images or air gapped builds, this removes one friction point.

Is this a prerelease?

The package name carries a 0.5b0 suffix, which marks it as a beta in the Python versioning scheme. The release metadata lists prerelease: False on GitHub, but the b0 flag means tools like pip can still treat it differently depending on your resolver settings. Pin the exact version if you want it.

Anything else in the release?

No. The release notes list a single change under the “Changed” section: the uuid-utils to pure Python UUIDv7 swap. There are no new features, no deprecations, and no documented upgrade steps. If you are already on an earlier 0.4x build of the OpAMP client, the only visible difference should be a smaller dependency tree.

Where to get it

← All updates