chore(deps): update module github.com/googlecloudplatform/opentelemetry-operations-go/detectors/gcp to v1.38.0 (main)

[renovate-sh-app]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp	v1.32.0 → v1.38.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

Need help?

You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.

[tempo-ci-app]

🤖 fix-renovate-prs rerun_failed_actions: The only failure is TestBackendSchedulerRedactionQuery hitting require.NotEmpty(trs) immediately after ingest — a timing race in a recently-added test unrelated to this PR, which only bumps vendored code for the GCP resource detector.

[tempo-ci-app]

🤖 fix-renovate-prs rerun_failed_actions: The bump only touches the GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp vendored module, which no first-party Tempo code imports — it cannot cause either failure. The unit failure is a timing-sensitive polling assertion in TestCompactionProvider_EmptyStart (modules/backendscheduler/provider/compaction_test.go:157) and the e2e-storage log tail shows only container tear-down with no assertion — both look like unrelated flakes, so re-running the failed jobs should clear them.

[tempo-ci-app]

🤖 fix-renovate-prs rerun_failed_actions: TestBackendSchedulerRedactionQuery failed on an eventual-consistency race — the tempodb_blocklist_length metric flipped from 2 to 3 during the run and a trace wasn't findable before redaction. The PR is a vendor-only bump of the GCP resource-detector library, which cannot influence the backend scheduler or tempodb polling that the test exercises; re-running the job should clear it.

[tempo-ci-app]

🤖 fix-renovate-prs rerun_failed_actions: Analyze (go) log is a bare BlobNotFound XML — log-storage transient, not a real failure. test-e2e-api's TestQueryRangeTypeHandling flaked (expected 2 series, got 0 — eventual-consistency of trace ingest) with an unrelated permission-denied cleanup after; neither exercises the bumped indirect GCP resource detector.

[tempo-ci-app]

🤖 fix-renovate-prs rerun_failed_actions: Both integration test jobs failed because the minio-9000 container could not start — Docker Hub returned 'pull access denied for minio/minio' for the pinned image. This is a registry/auth flake unrelated to the detectors/gcp dependency bump, so a rerun should clear it.

[tempo-ci-app]

🤖 fix-renovate-prs rerun_failed_actions: Both integration test jobs failed only because docker pull minio/minio:RELEASE.2021-10-13T00-23-17Z was denied by Docker Hub (pull access denied for minio/minio), a transient registry/auth issue unrelated to this GCP detector dependency bump. Re-running the failed jobs should clear it.