chore(deps): update module go.opentelemetry.io/collector/cmd/builder to v0.150.0

[topicus-education-renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
go.opentelemetry.io/collector/cmd/builder	v0.146.1 → v0.150.0

---

Release Notes

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

v0.150.0

Compare Source

💡 Enhancements 💡

• all: Update semconv package from 1.38.0 to 1.40.0 (#​15095)
• cmd/mdatagen: Only allow the ToVersion feature flag attribute to be set for the Stable and Deprecated stages. (#​15040)
  To better match the feature flag README
  (https://github.com/open-telemetry/opentelemetry-collector/blob/main/featuregate/README.md#feature-lifecycle).

🧰 Bug fixes 🧰

• exporter/debug: Guard from out of bounds profiles dictionary indices (#​14803)

• pdata/pprofile: create a copy when the input is marked as read-only (#​15080)

• pkg/otelcol: Fix missing default values in unredacted print-config command by introducing confmap.WithUnredacted MarshalOption. (#​14750)
  Resolves an issue where the unredacted mode output omitted all default-valued options. By introducing a new MarshalOption to disable redaction directly at the confmap encoding level, the unredacted mode now preserves all component defaults natively without requiring post-processing.

• pkg/service: Headers on the internal telemetry OTLP exporter are now redacted when the configuration is marshaled (#​14756)

v0.149.0

Compare Source

🛑 Breaking changes 🛑

• pkg/service: Remove service_name, service_instance_id, and service_version as constant labels on every internal metric datapoint. These attributes are already present in target_info and were being duplicated on each series for OpenCensus backwards compatibility. (#​14811)
  Previously, the collector stamped every internal metric series (e.g. otelcol_process_runtime_heap_alloc_bytes)
  with service_name, service_instance_id, and service_version labels to match the old OpenCensus behavior.
  These attributes are now only present in the target_info metric, which is the correct Prometheus/OTel convention.
  Users who filter or group by these labels on individual metrics will need to update their queries to use
  target_info joins instead.

💡 Enhancements 💡

• all: Move aix/ppc64 to tier 3 support (#​13380)

• all: Upgrade the profiles stability status to alpha (#​14817)
  The following components have their profiles status upgraded from development to alpha:

  • pdata/pprofile
  • connector/forward
  • exporter/debug
  • receiver/nop
  • exporter/nop
  • exporter/otlp_grpc
  • exporter/otlp_http

• cmd/mdatagen: Add semconv reference for attributes (#​13297)

🧰 Bug fixes 🧰

• cmd/mdatagen: Fix entity code generation so extra_attributes are emitted as resource attributes instead of entity descriptive attributes. (#​14778)

v0.148.0

Compare Source

❗ Known Issues ❗

• service: The collector's internal Prometheus metrics endpoint (:8888) now emits OTel service labels with underscore
  names (service_name, service_instance_id, service_version) instead of dot-notation names (service.name,
  service.instance.id, service.version). Users scraping this endpoint with the Prometheus receiver will see these renamed
  labels in resource and datapoint attributes. As a workaround, add the following metric_relabel_configs to your scrape
  config in prometheus receiver:

  metric_relabel_configs:
    - source_labels: [service_name]
      target_label: service.name
    - source_labels: [service_instance_id]
      target_label: service.instance.id
    - source_labels: [service_version]
      target_label: service.version
    - regex: service_name|service_instance_id|service_version
      action: labeldrop

  See #​14814 for details and updates.

🛑 Breaking changes 🛑

• all: Change metric units to be singular to match OTel specification, e.g. {requests} -> {request} (#​14753)

💡 Enhancements 💡

• cmd/mdatagen: Add deprecated_type field to allow specifying an alias for component types. (#​14718)
• cmd/mdatagen: Generate entity-scoped MetricsBuilder API that enforces entity-metric associations at compile time (#​14659)
• cmd/mdatagen: Skip generating reaggregation config options for metrics that have no aggregatable attributes. (#​14689)
• pkg/service: The internal status reporter no longer drops repeated Ok and RecoverableError statuses (#​14282)
  Status events can now carry metadata and there's value in allowing them to be emitted despite the status value itself
  not changing.

🧰 Bug fixes 🧰

• cmd/builder: Add .exe to output binary names when building for Windows targets. (#​12591)

• exporter/debug: Add printing of metric metadata in detailed verbosity. (#​14667)

• exporter/otlp_grpc: Prevent nil pointer panic when push methods are called before the OTLP exporter initializes its gRPC clients. (#​14663)
  When the sending queue and retry are disabled, calling ConsumeTraces,
  ConsumeMetrics, ConsumeLogs, or ConsumeProfiles before the OTLP exporter
  initializes its gRPC clients could cause a nil pointer dereference panic.
  The push methods now return an error instead of panicking.

• exporter/otlp_http: Show the actual destination URL in error messages when request URL is modified by middleware. (#​14673)
  Unwraps the *url.Error returned by http.Client.Do() to prevent misleading error logs when a middleware extension dynamically updates the endpoint.

• pdata/pprofile: Switch the dictionary of dictionary tables entries only once when merging profiles (#​14709)
  For dictionary table data, we used to switch their dictionaries when doing
  the switch for the data that uses them.
  However, when an entry is associated with multiple other data (several
  samples can use the same stack), we would have been switching the
  dictionaries of the entry multiple times.

  We now switch dictionaries for dictionary table data only once, before
  switching the resource profiles.

v0.147.0

Compare Source

💡 Enhancements 💡

• exporter/debug: Output bucket counts for exponential histogram data points in normal verbosity. (#​10463)
• pkg/exporterhelper: Add metadata_keys configuration to sending_queue.batch.partition to partition batches by client metadata (#​14139)
  The metadata_keys configuration option is now available in the sending_queue.batch.partition section for all exporters.
  When specified, batches are partitioned based on the values of the listed metadata keys, allowing separate batching per metadata partition. This feature
  is automatically configured when using exporterhelper.WithQueue().

🧰 Bug fixes 🧰

• cmd/builder: Fix duplicate error output when CLI command execution fails in the builder tool. (#​14436)

• cmd/mdatagen: Fix duplicate error output when CLI command execution fails in the mdatagen tool. (#​14436)

• cmd/mdatagen: Fix semconv URL validation for metrics with underscores in their names (#​14583)
  Metrics like system.disk.io_time now correctly validate against semantic convention URLs containing underscores in the anchor tag.

• extension/memory_limiter: Use ChainUnaryInterceptor instead of UnaryInterceptor to allow multiple interceptors. (#​14634)
  If multiple extensions that use the UnaryInterceptor are set the binary panics at start time.

• extension/memory_limiter: Add support for streaming services. (#​14634)

• pkg/config/configmiddleware: Add context.Context to HTTP middleware interface constructors. (#​14523)
  This is a breaking API change for components that implement or use extensionmiddleware.

• pkg/confmap: Fix another issue where configs could fail to decode when using interpolated values in string fields. (#​14034)
  For example, a resource attribute can be set via an environment variable to a string that is parseable as a number, e.g. 1234.

  (A similar bug was fixed in a previous release: that one was triggered when the field was nested in a struct,
  whereas this one is triggered when the field internally has type "pointer to string" rather than "string".)

• pkg/otelcol: The featuregate subcommand now rejects extra positional arguments instead of silently ignoring them. (#​14554)

• pkg/queuebatch: Fix data race in partition_batcher where resetTimer() was called outside mutex, causing concurrent timer.Reset() calls and unpredictable batch flush timing under load. (#​14491)

• pkg/scraperhelper: Log scrapers now emit log-appropriate receiver telemetry (#​14654)
  Log scrapers previously emitted the same receiver telemetry as metric scrapers,
  such as the otelcol_receiver_accepted_metric_points metric (instead of otelcol_receiver_accepted_log_records),
  or spans named receiver/myreceiver/MetricsReceived (instead of receiver/myreceiver/LogsReceived).

  This did not affect scraper-specific spans and metrics.

• processor/batch: Fixes a bug where the batch processor would not copy SchemaUrl metadata from resource and scope containers during partial batch splits. (#​12279, #​14620)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)

🚦 Automerge: Enabled.

♻ 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

---

This PR has been generated by Renovate Bot.

[topicus-education-renovate-bot]

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

• 3 additional dependencies were updated

Details:

Package	Change
github.com/knadh/koanf/v2	v2.3.2 -> v2.3.4
golang.org/x/mod	v0.33.0 -> v0.34.0
golang.org/x/sys	v0.36.0 -> v0.41.0