fix(deps): update github.com/grafana/dskit digest to a52c9d3

[renovate-sh-app]

This PR contains the following updates:

Package	Type	Update	Change
github.com/grafana/dskit	require	digest	8ff9c65 → a52c9d3

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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.

[renovate-sh-app]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 48 additional dependencies were updated

Details:

Package	Change
github.com/golang/snappy	v0.0.4 -> v1.0.0
github.com/prometheus/client_golang	v1.22.0 -> v1.23.2
github.com/prometheus/common	v0.64.0 -> v0.67.4
github.com/stretchr/testify	v1.10.0 -> v1.11.1
go.opentelemetry.io/otel	v1.37.0 -> v1.38.0
go.opentelemetry.io/otel/trace	v1.37.0 -> v1.38.0
golang.org/x/net	v0.44.0 -> v0.47.0
golang.org/x/oauth2	v0.31.0 -> v0.32.0
golang.org/x/sync	v0.17.0 -> v0.19.0
github.com/cenkalti/backoff/v5	v5.0.2 -> v5.0.3
github.com/coreos/go-systemd/v22	v22.5.0 -> v22.6.0
github.com/gogo/status	v1.1.0 -> v1.1.1
github.com/grpc-ecosystem/grpc-gateway/v2	v2.26.3 -> v2.27.2
github.com/hashicorp/go-sockaddr	v1.0.6 -> v1.0.7
github.com/hashicorp/memberlist	v0.5.2 -> v0.5.3
github.com/prometheus/exporter-toolkit	v0.11.0 -> v0.15.0
github.com/prometheus/procfs	v0.16.1 -> v0.17.0
github.com/uber/jaeger-client-go	v2.28.0+incompatible -> v2.30.0+incompatible
github.com/uber/jaeger-lib	v2.2.0+incompatible -> v2.4.1+incompatible
go.opentelemetry.io/auto/sdk	v1.1.0 -> v1.2.1
go.opentelemetry.io/contrib/bridges/prometheus	v0.61.0 -> v0.63.0
go.opentelemetry.io/contrib/exporters/autoexport	v0.61.0 -> v0.63.0
go.opentelemetry.io/contrib/instrumentation/net/http/httptrace/otelhttptrace	v0.60.0 -> v0.63.0
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp	v0.61.0 -> v0.63.0
go.opentelemetry.io/contrib/propagators/jaeger	v1.35.0 -> v1.38.0
go.opentelemetry.io/contrib/samplers/jaegerremote	v0.30.0 -> v0.32.0
go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc	v0.12.2 -> v0.14.0
go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp	v0.12.2 -> v0.14.0
go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc	v1.36.0 -> v1.38.0
go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp	v1.36.0 -> v1.38.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace	v1.36.0 -> v1.38.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc	v1.36.0 -> v1.38.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp	v1.36.0 -> v1.38.0
go.opentelemetry.io/otel/exporters/prometheus	v0.58.0 -> v0.60.0
go.opentelemetry.io/otel/exporters/stdout/stdoutlog	v0.12.2 -> v0.14.0
go.opentelemetry.io/otel/exporters/stdout/stdoutmetric	v1.36.0 -> v1.38.0
go.opentelemetry.io/otel/exporters/stdout/stdouttrace	v1.36.0 -> v1.38.0
go.opentelemetry.io/otel/log	v0.12.2 -> v0.14.0
go.opentelemetry.io/otel/metric	v1.37.0 -> v1.38.0
go.opentelemetry.io/otel/sdk	v1.37.0 -> v1.38.0
go.opentelemetry.io/otel/sdk/log	v0.12.2 -> v0.14.0
go.opentelemetry.io/otel/sdk/metric	v1.37.0 -> v1.38.0
go.opentelemetry.io/proto/otlp	v1.6.0 -> v1.7.1
golang.org/x/crypto	v0.42.0 -> v0.45.0
golang.org/x/mod	v0.27.0 -> v0.30.0
golang.org/x/sys	v0.36.0 -> v0.38.0
golang.org/x/text	v0.29.0 -> v0.31.0
google.golang.org/grpc	v1.75.1 -> v1.77.0

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is ON. A Cloud Agent has been kicked off to fix the reported issue.}

[cursor]

Duplicate YAML v2 dependencies may cause conflicts

Medium Severity

The module has both go.yaml.in/yaml/v2 v2.4.3 and gopkg.in/yaml.v2 v2.4.0 as indirect dependencies. These are two different import paths for the same YAML library, which can cause import path conflicts and version inconsistencies. The canonical path go.yaml.in/yaml/v2 should be used exclusively, and gopkg.in/yaml.v2 should be removed or migrated via a replace directive.

Additional Locations (1)

• go.mod#L154-L155

 

[cursor]

Bugbot Autofix prepared fixes for 1 of the 1 bugs found in the latest run.

• ✅ Fixed: Duplicate YAML v2 dependencies may cause conflicts
  • Added a replace directive to redirect gopkg.in/yaml.v2 to the canonical go.yaml.in/yaml/v2 v2.4.3 path, ensuring all transitive dependencies resolve to the same module and preventing type incompatibilities.

Or push these changes by commenting:

@cursor push 00d1c9d8dc

Preview (00d1c9d8dc)

diff --git a/go.mod b/go.mod
--- a/go.mod
+++ b/go.mod
@@ -175,3 +175,7 @@
 replace google.golang.org/genproto/googleapis/rpc => google.golang.org/genproto/googleapis/rpc v0.0.0-20251124214823-79d6a2a48846
 
 replace google.golang.org/genproto/googleapis/api => google.golang.org/genproto/googleapis/api v0.0.0-20251124214823-79d6a2a48846
+
+// Redirect old YAML v2 import path to canonical path to avoid type conflicts
+// when different transitive dependencies use different import paths.
+replace gopkg.in/yaml.v2 => go.yaml.in/yaml/v2 v2.4.3