fix(deps): update module go.opentelemetry.io/collector/config/configgrpc to v0.130.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
go.opentelemetry.io/collector/config/configgrpc	v0.128.0 -> v0.130.1

---

Release Notes

open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/config/configgrpc)

v0.130.1

Compare Source

🧰 Bug fixes 🧰

• service: Fixes bug where internal metrics are emitted with an unexpected suffix in their names when users configure service::telemetry::metrics::readers with Prometheus. (#​13449)
  See more details ohttps://github.com/open-telemetry/opentelemetry-go/issues/703939

v0.130.0

Compare Source

❗ Known Issues ❗

• Due to a bug in the prometheus exporter, if you are configuring a prometheus exporter, the collector's internal metrics will be emitted with an unexpected suffix in its name. For example, the metric otelcol_exporter_sent_spans__spans__total instead of otelcol_exporter_sent_spans_total. The workaround is to manually configure without_units: true in your prometheus exporter config

  service:
    telemetry:
      metrics:
        readers:
          - pull:
              exporter:
                prometheus:
                  host: 0.0.0.0
                  port: 8888
                  without_units: true

  If you are using the collector's default Prometheus exporter for exporting internal metrics you are unaffected.

🛑 Breaking changes 🛑

• exporter/otlp: Remove deprecated batcher config from OTLP, use queuebatch (#​13339)

💡 Enhancements 💡

• exporterhelper: Enable items and bytes sizers for persistent queue (#​12881)
• exporterhelper: Refactor persistent storage size backup to always record it. (#​12890)
• exporterhelper: Add support to configure a different Sizer for the batcher than the queue (#​13313)
• yaml: Replaced sigs.k8s.io/yaml with go.yaml.in/yaml for improved support and long-term maintainability. (#​13308)

🧰 Bug fixes 🧰

• exporterhelper: Fix exporter.PersistRequestContext feature gate (#​13342)

• exporterhelper: Preserve all metrics metadata when batch splitting. (#​13236)
  Previously, when large batches of metrics were processed, the splitting logic in metric_batch.go could
  cause the name field of some metrics to disappear. This fix ensures that all metric fields are
  properly preserved when metricRequest objects are split.

• service: Default internal metrics config now enables otel_scope_ labels (#​12939, #​13344)
  By default, the Collector exports its internal metrics using a Prometheus
  exporter from the opentelemetry-go repository. With this change, the Collector
  no longer sets "without_scope_info" to true in its configuration.

  This means that all exported metrics will have otel_scope_name,
  otel_scope_schema_url, and otel_scope_version labels corresponding to the
  instrumentation scope metadata for that metric.

  This notably prevents an error when multiple metrics are only distinguished
  by their instrumentation scopes and end up aliased during export.

  If this is not desired behavior, a Prometheus exporter can be explicitly
  configured with this option enabled.

v0.129.0

Compare Source

🛑 Breaking changes 🛑

• exporterhelper: Remove deprecated sending_queue::blocking options, use sending_queue::block_on_overflow. (#​13211)

💡 Enhancements 💡

• mdatagen: Taught mdatagen to print the go list stderr output on failures, and to run go list where the metadata file is. (#​13205)

• service: Support setting sampler and limits under service::telemetry::traces (#​13201)
  This allows users to enable sampling and set span limits on internal Collector traces using the
  OpenTelemetry SDK declarative configuration.

• pdata/pprofile: Add new helper methods FromLocationIndices and PutLocation to read and modify the content of locations. (#​13150)

• exporterhelper: Preserve request span context and client information in the persistent queue. (#​11740, #​13220, #​13232)
  It allows internal collector spans and client information to propagate through the persistent queue used by
  the exporters. The same way as it's done for the in-memory queue.
  Currently, it is behind the exporter.PersistRequestContext feature gate, which can be enabled by adding
  --feature-gates=exporter.PersistRequestContext to the collector command line. An exporter buffer stored by
  a previous version of the collector (or by a collector with the feature gate disabled) can be read by a newer
  collector with the feature enabled. However, the reverse is not supported: a buffer stored by a newer collector with
  the feature enabled cannot be read by an older collector (or by a collector with the feature gate disabled).

🧰 Bug fixes 🧰

• pdata: Fix copying of optional fields when the source is unset. (#​13268)
• service: Only allocate one set of internal log sampling counters (#​13014)
  The case where logs are only exported to stdout was fixed in v0.126.0;
  this new fix also covers the case where logs are exported through OTLP.

---

Configuration

📅 Schedule: Branch creation - "before 8am on Monday" (UTC), Automerge - At any time (no schedule defined).

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

♻ 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

---

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

• 16 additional dependencies were updated

Details:

Package	Change
go.opentelemetry.io/collector/config/configtls	v1.34.0 -> v1.36.1
go.opentelemetry.io/collector/consumer	v1.34.0 -> v1.36.1
github.com/go-viper/mapstructure/v2	v2.2.1 -> v2.3.0
github.com/knadh/koanf/v2	v2.2.0 -> v2.2.1
go.opentelemetry.io/collector/client	v1.34.0 -> v1.36.1
go.opentelemetry.io/collector/config/configauth	v0.128.0 -> v0.130.1
go.opentelemetry.io/collector/config/configcompression	v1.34.0 -> v1.36.1
go.opentelemetry.io/collector/config/configmiddleware	v0.128.0 -> v0.130.1
go.opentelemetry.io/collector/config/confignet	v1.34.0 -> v1.36.1
go.opentelemetry.io/collector/confmap	v1.34.0 -> v1.36.1
go.opentelemetry.io/collector/extension	v1.34.0 -> v1.36.1
go.opentelemetry.io/collector/extension/extensionauth	v1.34.0 -> v1.36.1
go.opentelemetry.io/collector/extension/extensionmiddleware	v0.128.0 -> v0.130.1
go.opentelemetry.io/collector/pdata/pprofile	v0.128.0 -> v0.130.1
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc	v0.61.0 -> v0.62.0
google.golang.org/genproto/googleapis/rpc	v0.0.0-20250519155744-55703ea1f237 -> v0.0.0-20250603155806-513f23925822

[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.

[codecov]

Codecov Report

❌ Patch coverage is 95.83333% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 69.86%. Comparing base (e1c4211) to head (8678d91).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/export/otel/traces.go	95.83%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #377      +/-   ##
==========================================
+ Coverage   69.69%   69.86%   +0.16%     
==========================================
  Files         214      214              
  Lines       22427    22440      +13     
==========================================
+ Hits        15630    15677      +47     
+ Misses       6001     5966      -35     
- Partials      796      797       +1     

Flag	Coverage Δ
integration-test	57.31% <95.83%> (+0.50%)	⬆️
integration-test-arm	34.78% <45.83%> (+0.12%)	⬆️
k8s-integration-test	51.41% <45.83%> (-0.12%)	⬇️
oats-test	35.50% <45.83%> (-0.15%)	⬇️
unittests	43.40% <45.83%> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.