fix(deps): update go dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
go.opentelemetry.io/collector/cmd/builder	v0.150.0 → v0.151.0
go.opentelemetry.io/collector/cmd/mdatagen	v0.150.0 → v0.151.0
go.opentelemetry.io/collector/component	v1.56.0 → v1.57.0
go.opentelemetry.io/collector/component/componenttest	v0.150.0 → v0.151.0
go.opentelemetry.io/collector/confmap	v1.56.0 → v1.57.0
go.opentelemetry.io/collector/confmap/xconfmap	v0.150.0 → v0.151.0
go.opentelemetry.io/collector/consumer/consumertest	v0.150.0 → v0.151.0
go.opentelemetry.io/collector/consumer/xconsumer	v0.150.0 → v0.151.0
go.opentelemetry.io/collector/pdata	v1.56.0 → v1.57.0
go.opentelemetry.io/collector/pdata/pprofile	v0.150.0 → v0.151.0
go.opentelemetry.io/collector/receiver	v1.56.0 → v1.57.0
go.opentelemetry.io/collector/receiver/receivertest	v0.150.0 → v0.151.0
go.opentelemetry.io/collector/receiver/xreceiver	v0.150.0 → v0.151.0

---

Release Notes

open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/cmd/builder)

v0.151.0

Compare Source

🛑 Breaking changes 🛑

• cmd/builder: In the generated Collector source, the replace statements in the Go module will now use relative paths by default. (#​15097)
  We expect that this will not break existing use-cases where the generated collector is only used in an interim manner for builds. It enables the possibility of tracking the generated Collector code as a longer living artifact, allowing it to be run on any machine (whereas absolute paths will be different depending on the machine the Collector source is generated on.) We have added dist::use_absolute_replace_paths to go back to the absolute path behaviour in the case where there is an unforeseen use-case that requires absolute paths.

• pkg/confighttp: Stabilize framedSnappy feature gate. (#​15096)

💡 Enhancements 💡

• all: Add declarative schema support for service telemetry resource configuration. (#​14411)
  The service::telemetry::resource configuration now accepts the declarative schema with explicit name/value pairs:

  service:
    telemetry:
      resource:
        schema_url: https://opentelemetry.io/schemas/1.38.0
        attributes:
          - name: service.name
            value: my-collector
          - name: host.name
            value: collector-host

  The legacy inline attribute map format is still supported for backward compatibility:

  service:
    telemetry:
      resource:
        service.name: my-collector
        host.name: collector-host

  Note: resource.detectors is accepted for forward compatibility but is not yet applied by the collector.

• exporter/otlp_grpc: Added the server.address and url.path attributes to metrics generated by the otlp exporter. (#​14998)

• exporter/otlp_http: Added the server.address and url.path attributes to metrics generated by the otlp_http exporter. (#​14998)

• pkg/config/configgrpc: Add UserAgent field to ClientConfig to allow overriding the default gRPC user-agent string. (#​14686)
  The otlp gRPC exporter was unconditionally setting the User-Agent via
  grpc.WithUserAgent() at dial time, which takes precedence over per-call
  metadata, causing any user-configured User-Agent to be silently discarded.
  A dedicated UserAgent field has been added to ClientConfig which, when
  set, is used in the dial option directly instead of the default BuildInfo-derived string.

• pkg/config/configgrpc: Accept gRPC resolver scheme URIs in client endpoint (e.g. passthrough:///host:port) to allow control over name resolution (#​14990)
  After the migration to grpc.NewClient, some gRPC client components such as the OTLP
  exporter experienced connection issues in dual-stack DNS environments. This can now be
  fixed by using the passthrough:/// gRPC resolver scheme in the endpoint field.

• pkg/config/confignet: Add support for Windows Named Pipe (npipe) transport (#​15085)

• pkg/service: Emit a warning when using the old v0.2.0 declarative config format (#​15088)

🧰 Bug fixes 🧰

• pkg/otelcol: Print components exactly once in the otelcol components command (#​14682)
  This resolves an issue where aliased components were skipped.

• pkg/otelcol: Synchronize Collector Run and Shutdown lifecycles so that Shutdown blocks until Run completes all cleanup. (#​4947)
  Shutdown now blocks until Run finishes cleanup, matching http.Server semantics.
  If Shutdown is called before Run, the next Run call returns nil after cleaning up
  the config provider.

• pkg/pdata: Use spec-compliant string representation for NaN, Infinity, and -Infinity in Value.AsString(). (#​14487)

• pkg/pprofile: Fix data corruption of resource and scope attributes after marshal-unmarshal-merge round-trip. (#​15084)

• pkg/service: Non-string resource attributes in telemetry configuration now return an error instead of panicking (#​15171)

• pkg/xscraperhelper: fix the merge of profiles in the profiling scraper helpers (#​14790)

• receiver/otlp: Fix profiles receiver reporting its samples as spans (#​15089)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 8am every weekday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ️ 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):

• 6 additional dependencies were updated

Details:

Package	Change
go.opentelemetry.io/collector/consumer	v1.56.0 -> v1.57.0
go.opentelemetry.io/collector/consumer/consumererror	v0.150.0 -> v0.151.0
go.opentelemetry.io/collector/featuregate	v1.56.0 -> v1.57.0
go.opentelemetry.io/collector/internal/componentalias	v0.150.0 -> v0.151.0
go.opentelemetry.io/collector/pipeline	v1.56.0 -> v1.57.0
go.uber.org/zap	v1.27.1 -> v1.28.0

File name: internal/tools/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):

• 11 additional dependencies were updated

Details:

Package	Change
go.opentelemetry.io/collector/component	v1.56.0 -> v1.57.0
go.opentelemetry.io/collector/confmap	v1.56.0 -> v1.57.0
go.opentelemetry.io/collector/confmap/provider/fileprovider	v1.56.0 -> v1.57.0
go.opentelemetry.io/collector/featuregate	v1.56.0 -> v1.57.0
go.opentelemetry.io/collector/filter	v0.150.0 -> v0.151.0
go.opentelemetry.io/collector/pdata	v1.56.0 -> v1.57.0
go.uber.org/zap	v1.27.1 -> v1.28.0
golang.org/x/net	v0.52.0 -> v0.53.0
golang.org/x/term	v0.41.0 -> v0.42.0
golang.org/x/text	v0.35.0 -> v0.36.0
golang.org/x/tools	v0.43.0 -> v0.44.0

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[christos68k]

Shouldn't renovate execute go mod tidy? I looked at some logs but don't see any failures.

[florianl]

gomodTidy is configured as postUpdateOption and it is recognized also in the renovate runs (see https://developer.mend.io/github/open-telemetry/opentelemetry-ebpf-profiler/-/job/019dd853-0340-7608-905a-a763f2d04122 and look for gomodTidy), but it does not happen as far as I can tell.