opentelemetry-exporter-gcp-trace broken with opentelemetry-resourcedetector-gcp==1.13.0 (import path rename)

[etiennevincent]

Summary

opentelemetry-resourcedetector-gcp==1.13.0 (released 2026-07-22 from open-telemetry/opentelemetry-python-contrib#4749 / #4846) moved the public module path:

• before (≤1.12.0a0): opentelemetry.resourcedetector.gcp_resource_detector
• after (1.13.0): opentelemetry.resource.detector.gcp

opentelemetry-exporter-gcp-trace (including latest 1.12.0) still imports the old path at module import time, and depends on:

opentelemetry-resourcedetector-gcp ==1.*,>=1.5.0dev0

Pip prefers the new stable 1.13.0 over 1.12.0a0, so any fresh install of the exporter now fails with:

ModuleNotFoundError: No module named 'opentelemetry.resourcedetector'

when importing opentelemetry.exporter.cloud_trace.

Impact

Any service using Cloud Trace via this exporter breaks on image rebuild / fresh pip install after 1.13.0 was published. Workaround: pin opentelemetry-resourcedetector-gcp==1.12.0a0.

Expected / asks

1. Tighten the exporter dependency (e.g. pin <1.13 or ==1.12.0a0) and/or update imports to opentelemetry.resource.detector.gcp.
2. Coordinate with the contrib migration — the 1.13.0 changelog describes a “move” but does not call out the import path change; the migration PR was labeled non-breaking.

Related

• Migration: Migrate GCP resource detector (opentelemetry-resourcedetector-gcp) to contrib open-telemetry/opentelemetry-python-contrib#4749
• Release workflow: Add release for GCP resource detector open-telemetry/opentelemetry-python-contrib#4846
• Prior contribution intent: Contribute resource detector to opentelemetry-python-contrib #384

[etiennevincent]

Also filed on the OT contrib side (where 1.13.0 was released / a compatibility shim would land): open-telemetry/opentelemetry-python-contrib#4855

[DylanRussell]

Sorry, didn't mean to change the import path.. I've yanked the release off PyPi for now

[DylanRussell]

Re-released this with correct import paths.. marking this as fixed