Skip to content

chore(deps): bump the go-deps group with 11 updates#211

Open
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/go_modules/go-deps-9c9356c546
Open

chore(deps): bump the go-deps group with 11 updates#211
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/go_modules/go-deps-9c9356c546

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 22, 2026

Copy link
Copy Markdown
Contributor

Bumps the go-deps group with 11 updates:

Package From To
github.com/dash0hq/dash0-api-client-go 1.16.0 1.17.1
go.opentelemetry.io/collector/component 1.62.0 1.63.0
go.opentelemetry.io/collector/config/configgrpc 0.156.0 0.157.0
go.opentelemetry.io/collector/config/confighttp 0.156.0 0.157.0
go.opentelemetry.io/collector/config/configoptional 1.62.0 1.63.0
go.opentelemetry.io/collector/consumer 1.62.0 1.63.0
go.opentelemetry.io/collector/consumer/consumererror 0.156.0 0.157.0
go.opentelemetry.io/collector/pdata 1.62.0 1.63.0
go.opentelemetry.io/collector/receiver 1.62.0 1.63.0
go.opentelemetry.io/collector/receiver/otlpreceiver 0.156.0 0.157.0
google.golang.org/grpc 1.82.0 1.82.1

Updates github.com/dash0hq/dash0-api-client-go from 1.16.0 to 1.17.1

Release notes

Sourced from github.com/dash0hq/dash0-api-client-go's releases.

v1.17.1

Bug Fixes

  • index members by metadata.name in ResolveMemberIDsToEmails

v1.17.0

Features

  • declarative CRD support for the Dash0 Teams API (#21)
Changelog

Sourced from github.com/dash0hq/dash0-api-client-go's changelog.

v1.17.1

Bug Fixes

  • index members by metadata.name in ResolveMemberIDsToEmails

v1.17.0

Features

  • declarative CRD support for the Dash0 Teams API (#21)
Commits
  • 77899f0 chore: prepare release v1.17.1
  • 08aa9eb fix(teams): index members by metadata.name in ResolveMemberIDsToEmails
  • a31206e chore: transfer code ownership to @​dash0hq/engineering-iac (#23)
  • 2492458 chore: prepare release v1.17.0
  • 1e9e040 feat(teams): declarative CRD support for the Dash0 Teams API (#21)
  • 86af1bf Add CODEOWNERS requiring @​mmanciop review (#18)
  • See full diff in compare view

Updates go.opentelemetry.io/collector/component from 1.62.0 to 1.63.0

Release notes

Sourced from go.opentelemetry.io/collector/component's releases.

v1.63.0/v0.157.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.157.0

End User Changelog

🛑 Breaking changes 🛑

  • pkg/exporterhelper: Replace histogram bucket boundaries for otelcol_exporter_queue_batch_send_size_bytes and otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads, and otelcol_exporter_queue_batch_send_size_bytes topped out at 6000 bytes so nearly all observations fell into the +Inf overflow bucket. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the two metrics directly comparable on the same dashboards. Dashboards or alerts that hard-code specific le values for these histograms will need to be updated.

  • processor/batch: Replace histogram bucket boundaries for otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the metric directly comparable with otelcol_exporter_queue_batch_send_size_bytes on the same dashboards. Dashboards or alerts that hard-code specific le values for this histogram will need to be updated.

💡 Enhancements 💡

  • all: Bootstrap config.schema.yaml for core components (debug/otlp/otlphttp exporters, otlp receiver, batch/memory_limiter processors, memory_limiter/zpages extensions). Implements Phase 1 of the component configuration schema roadmap RFC. (#14543) Schemas are generated using the schemagen tool from opentelemetry-collector-contrib and hand-tuned to capture validation rules and references to shared library schemas (confighttp, configgrpc, configretry, exporterhelper, etc.). A .schemagen.yaml settings file and a generate-schemas Makefile target are added so the schemas can be regenerated reproducibly.

  • pkg/service: Apply experimental service::telemetry::resource::detection/development resource detection to the Collector's internal telemetry resource. (#14311) This follows the OpenTelemetry configuration schema by treating service::telemetry::resource::detection/development::detectors as detector selection. Currently supported detector entries are container, host, process, and service. See the OpenTelemetry Configuration Go support table and search for ExperimentalResourceDetector for current detector support: https://github.com/open-telemetry/opentelemetry-configuration/blob/main/language-support-status.md#go

    Example:

    service:
      telemetry:
        resource:
          attributes:
            - name: foo
              value: bar
          detection/development:

... (truncated)

Changelog

Sourced from go.opentelemetry.io/collector/component's changelog.

v1.63.0/v0.157.0

🛑 Breaking changes 🛑

  • pkg/config/configgrpc: Remove the BalancerName function (#9477) Use the DefaultBalancerName constant instead.

🚩 Deprecations 🚩

  • pkg/xconfmap: Deprecate WithForceUnmarshaler option. (#15614) Use confmap.WithForceUnmarshaler instead.

🚀 New components 🚀

  • pkg/config/configstorage: Add a new configstorage module to support storage configuration fields. (#5832)

💡 Enhancements 💡

  • pkg/confmap: Add WithForceUnmarshaler option. (#15614) This option allows forcing the top-level Unmarshal method even if the Conf is already a parameter from an Unmarshal method. See the Godoc for more details.
Commits
  • 4908404 [chore] Prepare release v1.63.0/v0.157.0 (#15624)
  • c823638 [service] chore: Forward hostcapabilities interfaces through extension host...
  • 1a861f0 [confmap] Stabilize WithForceUnmarshaler (#15614)
  • 7d0e3a0 [configgrpc] Remove the BalancerName function (#15611)
  • bd0d94a [configgrpc] Apply WaitForReady option (#15615)
  • 3294e3d [chore][configgrpc] Remove direct dependency on xconfmap (#15612)
  • 6885b26 [chore][configgrpc] Return correct error when PerRPCCredentials fails (#15616)
  • b873893 [chore][configgrpc] Remove duplicate omitempty tag (#15610)
  • 2ab65ae [service] Record status events reported by extensions (#15557)
  • fa69e2c [service] Fix startup panic when a resource detector emits a slice-valued att...
  • Additional commits viewable in compare view

Updates go.opentelemetry.io/collector/config/configgrpc from 0.156.0 to 0.157.0

Changelog

Sourced from go.opentelemetry.io/collector/config/configgrpc's changelog.

v1.63.0/v0.157.0

🛑 Breaking changes 🛑

  • pkg/config/configgrpc: Remove the BalancerName function (#9477) Use the DefaultBalancerName constant instead.

🚩 Deprecations 🚩

  • pkg/xconfmap: Deprecate WithForceUnmarshaler option. (#15614) Use confmap.WithForceUnmarshaler instead.

🚀 New components 🚀

  • pkg/config/configstorage: Add a new configstorage module to support storage configuration fields. (#5832)

💡 Enhancements 💡

  • pkg/confmap: Add WithForceUnmarshaler option. (#15614) This option allows forcing the top-level Unmarshal method even if the Conf is already a parameter from an Unmarshal method. See the Godoc for more details.
Commits
  • 4908404 [chore] Prepare release v1.63.0/v0.157.0 (#15624)
  • c823638 [service] chore: Forward hostcapabilities interfaces through extension host...
  • 1a861f0 [confmap] Stabilize WithForceUnmarshaler (#15614)
  • 7d0e3a0 [configgrpc] Remove the BalancerName function (#15611)
  • bd0d94a [configgrpc] Apply WaitForReady option (#15615)
  • 3294e3d [chore][configgrpc] Remove direct dependency on xconfmap (#15612)
  • 6885b26 [chore][configgrpc] Return correct error when PerRPCCredentials fails (#15616)
  • b873893 [chore][configgrpc] Remove duplicate omitempty tag (#15610)
  • 2ab65ae [service] Record status events reported by extensions (#15557)
  • fa69e2c [service] Fix startup panic when a resource detector emits a slice-valued att...
  • Additional commits viewable in compare view

Updates go.opentelemetry.io/collector/config/confighttp from 0.156.0 to 0.157.0

Changelog

Sourced from go.opentelemetry.io/collector/config/confighttp's changelog.

v1.63.0/v0.157.0

🛑 Breaking changes 🛑

  • pkg/config/configgrpc: Remove the BalancerName function (#9477) Use the DefaultBalancerName constant instead.

🚩 Deprecations 🚩

  • pkg/xconfmap: Deprecate WithForceUnmarshaler option. (#15614) Use confmap.WithForceUnmarshaler instead.

🚀 New components 🚀

  • pkg/config/configstorage: Add a new configstorage module to support storage configuration fields. (#5832)

💡 Enhancements 💡

  • pkg/confmap: Add WithForceUnmarshaler option. (#15614) This option allows forcing the top-level Unmarshal method even if the Conf is already a parameter from an Unmarshal method. See the Godoc for more details.
Commits
  • 4908404 [chore] Prepare release v1.63.0/v0.157.0 (#15624)
  • c823638 [service] chore: Forward hostcapabilities interfaces through extension host...
  • 1a861f0 [confmap] Stabilize WithForceUnmarshaler (#15614)
  • 7d0e3a0 [configgrpc] Remove the BalancerName function (#15611)
  • bd0d94a [configgrpc] Apply WaitForReady option (#15615)
  • 3294e3d [chore][configgrpc] Remove direct dependency on xconfmap (#15612)
  • 6885b26 [chore][configgrpc] Return correct error when PerRPCCredentials fails (#15616)
  • b873893 [chore][configgrpc] Remove duplicate omitempty tag (#15610)
  • 2ab65ae [service] Record status events reported by extensions (#15557)
  • fa69e2c [service] Fix startup panic when a resource detector emits a slice-valued att...
  • Additional commits viewable in compare view

Updates go.opentelemetry.io/collector/config/configoptional from 1.62.0 to 1.63.0

Release notes

Sourced from go.opentelemetry.io/collector/config/configoptional's releases.

v1.63.0/v0.157.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.157.0

End User Changelog

🛑 Breaking changes 🛑

  • pkg/exporterhelper: Replace histogram bucket boundaries for otelcol_exporter_queue_batch_send_size_bytes and otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads, and otelcol_exporter_queue_batch_send_size_bytes topped out at 6000 bytes so nearly all observations fell into the +Inf overflow bucket. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the two metrics directly comparable on the same dashboards. Dashboards or alerts that hard-code specific le values for these histograms will need to be updated.

  • processor/batch: Replace histogram bucket boundaries for otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the metric directly comparable with otelcol_exporter_queue_batch_send_size_bytes on the same dashboards. Dashboards or alerts that hard-code specific le values for this histogram will need to be updated.

💡 Enhancements 💡

  • all: Bootstrap config.schema.yaml for core components (debug/otlp/otlphttp exporters, otlp receiver, batch/memory_limiter processors, memory_limiter/zpages extensions). Implements Phase 1 of the component configuration schema roadmap RFC. (#14543) Schemas are generated using the schemagen tool from opentelemetry-collector-contrib and hand-tuned to capture validation rules and references to shared library schemas (confighttp, configgrpc, configretry, exporterhelper, etc.). A .schemagen.yaml settings file and a generate-schemas Makefile target are added so the schemas can be regenerated reproducibly.

  • pkg/service: Apply experimental service::telemetry::resource::detection/development resource detection to the Collector's internal telemetry resource. (#14311) This follows the OpenTelemetry configuration schema by treating service::telemetry::resource::detection/development::detectors as detector selection. Currently supported detector entries are container, host, process, and service. See the OpenTelemetry Configuration Go support table and search for ExperimentalResourceDetector for current detector support: https://github.com/open-telemetry/opentelemetry-configuration/blob/main/language-support-status.md#go

    Example:

    service:
      telemetry:
        resource:
          attributes:
            - name: foo
              value: bar
          detection/development:

... (truncated)

Changelog

Sourced from go.opentelemetry.io/collector/config/configoptional's changelog.

v1.63.0/v0.157.0

🛑 Breaking changes 🛑

  • pkg/config/configgrpc: Remove the BalancerName function (#9477) Use the DefaultBalancerName constant instead.

🚩 Deprecations 🚩

  • pkg/xconfmap: Deprecate WithForceUnmarshaler option. (#15614) Use confmap.WithForceUnmarshaler instead.

🚀 New components 🚀

  • pkg/config/configstorage: Add a new configstorage module to support storage configuration fields. (#5832)

💡 Enhancements 💡

  • pkg/confmap: Add WithForceUnmarshaler option. (#15614) This option allows forcing the top-level Unmarshal method even if the Conf is already a parameter from an Unmarshal method. See the Godoc for more details.
Commits
  • 4908404 [chore] Prepare release v1.63.0/v0.157.0 (#15624)
  • c823638 [service] chore: Forward hostcapabilities interfaces through extension host...
  • 1a861f0 [confmap] Stabilize WithForceUnmarshaler (#15614)
  • 7d0e3a0 [configgrpc] Remove the BalancerName function (#15611)
  • bd0d94a [configgrpc] Apply WaitForReady option (#15615)
  • 3294e3d [chore][configgrpc] Remove direct dependency on xconfmap (#15612)
  • 6885b26 [chore][configgrpc] Return correct error when PerRPCCredentials fails (#15616)
  • b873893 [chore][configgrpc] Remove duplicate omitempty tag (#15610)
  • 2ab65ae [service] Record status events reported by extensions (#15557)
  • fa69e2c [service] Fix startup panic when a resource detector emits a slice-valued att...
  • Additional commits viewable in compare view

Updates go.opentelemetry.io/collector/consumer from 1.62.0 to 1.63.0

Release notes

Sourced from go.opentelemetry.io/collector/consumer's releases.

v1.63.0/v0.157.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.157.0

End User Changelog

🛑 Breaking changes 🛑

  • pkg/exporterhelper: Replace histogram bucket boundaries for otelcol_exporter_queue_batch_send_size_bytes and otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads, and otelcol_exporter_queue_batch_send_size_bytes topped out at 6000 bytes so nearly all observations fell into the +Inf overflow bucket. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the two metrics directly comparable on the same dashboards. Dashboards or alerts that hard-code specific le values for these histograms will need to be updated.

  • processor/batch: Replace histogram bucket boundaries for otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the metric directly comparable with otelcol_exporter_queue_batch_send_size_bytes on the same dashboards. Dashboards or alerts that hard-code specific le values for this histogram will need to be updated.

💡 Enhancements 💡

  • all: Bootstrap config.schema.yaml for core components (debug/otlp/otlphttp exporters, otlp receiver, batch/memory_limiter processors, memory_limiter/zpages extensions). Implements Phase 1 of the component configuration schema roadmap RFC. (#14543) Schemas are generated using the schemagen tool from opentelemetry-collector-contrib and hand-tuned to capture validation rules and references to shared library schemas (confighttp, configgrpc, configretry, exporterhelper, etc.). A .schemagen.yaml settings file and a generate-schemas Makefile target are added so the schemas can be regenerated reproducibly.

  • pkg/service: Apply experimental service::telemetry::resource::detection/development resource detection to the Collector's internal telemetry resource. (#14311) This follows the OpenTelemetry configuration schema by treating service::telemetry::resource::detection/development::detectors as detector selection. Currently supported detector entries are container, host, process, and service. See the OpenTelemetry Configuration Go support table and search for ExperimentalResourceDetector for current detector support: https://github.com/open-telemetry/opentelemetry-configuration/blob/main/language-support-status.md#go

    Example:

    service:
      telemetry:
        resource:
          attributes:
            - name: foo
              value: bar
          detection/development:

... (truncated)

Changelog

Sourced from go.opentelemetry.io/collector/consumer's changelog.

v1.63.0/v0.157.0

🛑 Breaking changes 🛑

  • pkg/config/configgrpc: Remove the BalancerName function (#9477) Use the DefaultBalancerName constant instead.

🚩 Deprecations 🚩

  • pkg/xconfmap: Deprecate WithForceUnmarshaler option. (#15614) Use confmap.WithForceUnmarshaler instead.

🚀 New components 🚀

  • pkg/config/configstorage: Add a new configstorage module to support storage configuration fields. (#5832)

💡 Enhancements 💡

  • pkg/confmap: Add WithForceUnmarshaler option. (#15614) This option allows forcing the top-level Unmarshal method even if the Conf is already a parameter from an Unmarshal method. See the Godoc for more details.
Commits
  • 4908404 [chore] Prepare release v1.63.0/v0.157.0 (#15624)
  • c823638 [service] chore: Forward hostcapabilities interfaces through extension host...
  • 1a861f0 [confmap] Stabilize WithForceUnmarshaler (#15614)
  • 7d0e3a0 [configgrpc] Remove the BalancerName function (#15611)
  • bd0d94a [configgrpc] Apply WaitForReady option (#15615)
  • 3294e3d [chore][configgrpc] Remove direct dependency on xconfmap (#15612)
  • 6885b26 [chore][configgrpc] Return correct error when PerRPCCredentials fails (#15616)
  • b873893 [chore][configgrpc] Remove duplicate omitempty tag (#15610)
  • 2ab65ae [service] Record status events reported by extensions (#15557)
  • fa69e2c [service] Fix startup panic when a resource detector emits a slice-valued att...
  • Additional commits viewable in compare view

Updates go.opentelemetry.io/collector/consumer/consumererror from 0.156.0 to 0.157.0

Changelog

Sourced from go.opentelemetry.io/collector/consumer/consumererror's changelog.

v1.63.0/v0.157.0

🛑 Breaking changes 🛑

  • pkg/config/configgrpc: Remove the BalancerName function (#9477) Use the DefaultBalancerName constant instead.

🚩 Deprecations 🚩

  • pkg/xconfmap: Deprecate WithForceUnmarshaler option. (#15614) Use confmap.WithForceUnmarshaler instead.

🚀 New components 🚀

  • pkg/config/configstorage: Add a new configstorage module to support storage configuration fields. (#5832)

💡 Enhancements 💡

  • pkg/confmap: Add WithForceUnmarshaler option. (#15614) This option allows forcing the top-level Unmarshal method even if the Conf is already a parameter from an Unmarshal method. See the Godoc for more details.
Commits
  • 4908404 [chore] Prepare release v1.63.0/v0.157.0 (#15624)
  • c823638 [service] chore: Forward hostcapabilities interfaces through extension host...
  • 1a861f0 [confmap] Stabilize WithForceUnmarshaler (#15614)
  • 7d0e3a0 [configgrpc] Remove the BalancerName function (#15611)
  • bd0d94a [configgrpc] Apply WaitForReady option (#15615)
  • 3294e3d [chore][configgrpc] Remove direct dependency on xconfmap (#15612)
  • 6885b26 [chore][configgrpc] Return correct error when PerRPCCredentials fails (#15616)
  • b873893 [chore][configgrpc] Remove duplicate omitempty tag (#15610)
  • 2ab65ae [service] Record status events reported by extensions (#15557)
  • fa69e2c [service] Fix startup panic when a resource detector emits a slice-valued att...
  • Additional commits viewable in compare view

Updates go.opentelemetry.io/collector/pdata from 1.62.0 to 1.63.0

Release notes

Sourced from go.opentelemetry.io/collector/pdata's releases.

v1.63.0/v0.157.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.157.0

End User Changelog

🛑 Breaking changes 🛑

  • pkg/exporterhelper: Replace histogram bucket boundaries for otelcol_exporter_queue_batch_send_size_bytes and otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads, and otelcol_exporter_queue_batch_send_size_bytes topped out at 6000 bytes so nearly all observations fell into the +Inf overflow bucket. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the two metrics directly comparable on the same dashboards. Dashboards or alerts that hard-code specific le values for these histograms will need to be updated.

  • processor/batch: Replace histogram bucket boundaries for otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the metric directly comparable with otelcol_exporter_queue_batch_send_size_bytes on the same dashboards. Dashboards or alerts that hard-code specific le values for this histogram will need to be updated.

💡 Enhancements 💡

  • all: Bootstrap config.schema.yaml for core components (debug/otlp/otlphttp exporters, otlp receiver, batch/memory_limiter processors, memory_limiter/zpages extensions). Implements Phase 1 of the component configuration schema roadmap RFC. (#14543) Schemas are generated using the schemagen tool from opentelemetry-collector-contrib and hand-tuned to capture validation rules and references to shared library schemas (confighttp, configgrpc, configretry, exporterhelper, etc.). A .schemagen.yaml settings file and a generate-schemas Makefile target are added so the schemas can be regenerated reproducibly.

  • pkg/service: Apply experimental service::telemetry::resource::detection/development resource detection to the Collector's internal telemetry resource. (#14311) This follows the OpenTelemetry configuration schema by treating service::telemetry::resource::detection/development::detectors as detector selection. Currently supported detector entries are container, host, process, and service. See the OpenTelemetry Configuration Go support table and search for ExperimentalResourceDetector for current detector support: https://github.com/open-telemetry/opentelemetry-configuration/blob/main/language-support-status.md#go

    Example:

    service:
      telemetry:
        resource:
          attributes:
            - name: foo
              value: bar
          detection/development:

... (truncated)

Changelog

Sourced from go.opentelemetry.io/collector/pdata's changelog.

v1.63.0/v0.157.0

🛑 Breaking changes 🛑

  • pkg/config/configgrpc: Remove the BalancerName function (#9477) Use the DefaultBalancerName constant instead.

🚩 Deprecations 🚩

  • pkg/xconfmap: Deprecate WithForceUnmarshaler option. (#15614) Use confmap.WithForceUnmarshaler instead.

🚀 New components 🚀

  • pkg/config/configstorage: Add a new configstorage module to support storage configuration fields. (#5832)

💡 Enhancements 💡

  • pkg/confmap: Add WithForceUnmarshaler option. (#15614) This option allows forcing the top-level Unmarshal method even if the Conf is already a parameter from an Unmarshal method. See the Godoc for more details.
Commits
  • 4908404 [chore] Prepare release v1.63.0/v0.157.0 (#15624)
  • c823638 [service] chore: Forward hostcapabilities interfaces through extension host...
  • 1a861f0 [confmap] Stabilize WithForceUnmarshaler (#15614)
  • 7d0e3a0 [configgrpc] Remove the BalancerName function (#15611)
  • bd0d94a [configgrpc] Apply WaitForReady option (#15615)
  • 3294e3d [chore][configgrpc] Remove direct dependency on xconfmap (#15612)
  • 6885b26 [chore][configgrpc] Return correct error when PerRPCCredentials fails (#15616)
  • b873893 [chore][configgrpc] Remove duplicate omitempty tag (#15610)
  • 2ab65ae [service] Record status events reported by extensions (#15557)
  • fa69e2c [service] Fix startup panic when a resource detector emits a slice-valued att...
  • Additional commits viewable in compare view

Updates go.opentelemetry.io/collector/receiver from 1.62.0 to 1.63.0

Release notes

Sourced from go.opentelemetry.io/collector/receiver's releases.

v1.63.0/v0.157.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.157.0

End User Changelog

🛑 Breaking changes 🛑

  • pkg/exporterhelper: Replace histogram bucket boundaries for otelcol_exporter_queue_batch_send_size_bytes and otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads, and otelcol_exporter_queue_batch_send_size_bytes topped out at 6000 bytes so nearly all observations fell into the +Inf overflow bucket. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the two metrics directly comparable on the same dashboards. Dashboards or alerts that hard-code specific le values for these histograms will need to be updated.

  • processor/batch: Replace histogram bucket boundaries for otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#15535) The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale payloads. The new boundaries are powers of two from 128 B to 16777216 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the metric directly comparable with otelcol_exporter_queue_batch_send_size_bytes on the same dashboards. Dashboards or alerts that hard-code specific le values for this histogram will need to be updated.

💡 Enhancements 💡

  • all: Bootstrap config.schema.yaml for core components (debug/otlp/otlphttp exporters, otlp receiver, batch/memory_limiter processors, memory_limiter/zpages extensions). Implements Phase 1 of the component configuration schema roadmap RFC. (#14543) Schemas are generated using the schemagen tool from opentelemetry-collector-contrib and hand-tuned to capture validation rules and references to shared library schemas (confighttp, configgrpc, configretry, exporterhelper, etc.). A .schemagen.yaml settings file and a generate-schemas Makefile target are added so the schemas can be regenerated reproducibly.

  • pkg/service: Apply experimental service::telemetry::resource::detection/development resource detection to the Collector's internal telemetry resource. (#14311) This follows the OpenTelemetry configuration schema by treating service::telemetry::resource::detection/development::detectors as detector selection. Currently supported detector entries are container, host, process, and service. See the OpenTelemetry Configuration Go support table and search for ExperimentalResourceDetector for current detector support: https://github.com/open-telemetry/opentelemetry-configuration/blob/main/language-support-status.md#go

    Example:

    service:
      telemetry:
        resource:
          attributes:
            - name: foo
              value: bar
          detection/development:

... (truncated)

Changelog

Sourced from go.opentelemetry.io/collector/receiver's changelog.

v1.63.0/v0.157.0

🛑 Breaking changes 🛑

  • pkg/config/configgrpc: Remove the BalancerName function (#9477) Use the DefaultBalancerName constant instead.

🚩 Deprecations 🚩

  • pkg/xconfmap: Deprecate WithForceUnmarshaler option. (#15614) Use confmap.WithForceUnmarshaler instead.

🚀 New components 🚀

  • pkg/config/configstorage: Add a new configstorage module to support storage configuration fields. (#5832)

💡 Enhancements 💡

  • pkg/confmap: Add WithForceUnmarshaler option. (#15614) This option allows forcing the top-level Unmarshal method even if the Conf is already a parameter from an Unmarshal method. See the Godoc for more details.
Commits
  • 4908404 [chore] Prepare release v1.63.0/v0.157.0 (#15624)
  • c823638 [service] chore: Forward hostcapabilities interfaces through extension host...
  • 1a861f0 [confmap] Stabilize WithForceUnmarshaler (#15614)
  • 7d0e3a0 [configgrpc] Remove the BalancerName function (#15611)
  • bd0d94a [configgrpc] Apply WaitForReady option (#15615)
  • 3294e3d [chore][configgrpc] Remove direct dependency on xconfmap (#15612)
  • 6885b26 [chore][configgrpc] Return correct error when PerRPCCredentials fails (#15616)
  • b873893 [chore][configgrpc] Remove duplicate omitempty tag (#15610)
  • 2ab65ae [service] Record status events reported by extensions (#15557)
  • fa69e2c [service] Fix startup panic when a resource detector emits a slice-valued att...
  • Additional commits viewable in compare view

Updates go.opentelemetry.io/collector/receiver/otlpreceiver from 0.156.0 to 0.157.0

Changelog

Sourced from go.opentelemetry.io/collector/receiver/otlpreceiver's changelog.

v1.63.0/v0.157.0

🛑 Breaking changes 🛑

  • pkg/config/configgrpc: Remove the BalancerName function (#9477) Use the DefaultBalancerName constant instead.

🚩 Deprecations 🚩

  • pkg/xconfmap: Deprecate WithForceUnmarshaler option. (#15614) Use confmap.WithForceUnmarshaler instead.

🚀 New components 🚀...

Description has been truncated

Bumps the go-deps group with 11 updates:

| Package | From | To |
| --- | --- | --- |
| [github.com/dash0hq/dash0-api-client-go](https://github.com/dash0hq/dash0-api-client-go) | `1.16.0` | `1.17.1` |
| [go.opentelemetry.io/collector/component](https://github.com/open-telemetry/opentelemetry-collector) | `1.62.0` | `1.63.0` |
| [go.opentelemetry.io/collector/config/configgrpc](https://github.com/open-telemetry/opentelemetry-collector) | `0.156.0` | `0.157.0` |
| [go.opentelemetry.io/collector/config/confighttp](https://github.com/open-telemetry/opentelemetry-collector) | `0.156.0` | `0.157.0` |
| [go.opentelemetry.io/collector/config/configoptional](https://github.com/open-telemetry/opentelemetry-collector) | `1.62.0` | `1.63.0` |
| [go.opentelemetry.io/collector/consumer](https://github.com/open-telemetry/opentelemetry-collector) | `1.62.0` | `1.63.0` |
| [go.opentelemetry.io/collector/consumer/consumererror](https://github.com/open-telemetry/opentelemetry-collector) | `0.156.0` | `0.157.0` |
| [go.opentelemetry.io/collector/pdata](https://github.com/open-telemetry/opentelemetry-collector) | `1.62.0` | `1.63.0` |
| [go.opentelemetry.io/collector/receiver](https://github.com/open-telemetry/opentelemetry-collector) | `1.62.0` | `1.63.0` |
| [go.opentelemetry.io/collector/receiver/otlpreceiver](https://github.com/open-telemetry/opentelemetry-collector) | `0.156.0` | `0.157.0` |
| [google.golang.org/grpc](https://github.com/grpc/grpc-go) | `1.82.0` | `1.82.1` |


Updates `github.com/dash0hq/dash0-api-client-go` from 1.16.0 to 1.17.1
- [Release notes](https://github.com/dash0hq/dash0-api-client-go/releases)
- [Changelog](https://github.com/dash0hq/dash0-api-client-go/blob/main/CHANGELOG.md)
- [Commits](dash0hq/dash0-api-client-go@v1.16.0...v1.17.1)

Updates `go.opentelemetry.io/collector/component` from 1.62.0 to 1.63.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-collector/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CHANGELOG-API.md)
- [Commits](open-telemetry/opentelemetry-collector@pdata/v1.62.0...pdata/v1.63.0)

Updates `go.opentelemetry.io/collector/config/configgrpc` from 0.156.0 to 0.157.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-collector/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CHANGELOG-API.md)
- [Commits](open-telemetry/opentelemetry-collector@v0.156.0...v0.157.0)

Updates `go.opentelemetry.io/collector/config/confighttp` from 0.156.0 to 0.157.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-collector/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CHANGELOG-API.md)
- [Commits](open-telemetry/opentelemetry-collector@v0.156.0...v0.157.0)

Updates `go.opentelemetry.io/collector/config/configoptional` from 1.62.0 to 1.63.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-collector/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CHANGELOG-API.md)
- [Commits](open-telemetry/opentelemetry-collector@pdata/v1.62.0...pdata/v1.63.0)

Updates `go.opentelemetry.io/collector/consumer` from 1.62.0 to 1.63.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-collector/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CHANGELOG-API.md)
- [Commits](open-telemetry/opentelemetry-collector@pdata/v1.62.0...pdata/v1.63.0)

Updates `go.opentelemetry.io/collector/consumer/consumererror` from 0.156.0 to 0.157.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-collector/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CHANGELOG-API.md)
- [Commits](open-telemetry/opentelemetry-collector@v0.156.0...v0.157.0)

Updates `go.opentelemetry.io/collector/pdata` from 1.62.0 to 1.63.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-collector/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CHANGELOG-API.md)
- [Commits](open-telemetry/opentelemetry-collector@pdata/v1.62.0...pdata/v1.63.0)

Updates `go.opentelemetry.io/collector/receiver` from 1.62.0 to 1.63.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-collector/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CHANGELOG-API.md)
- [Commits](open-telemetry/opentelemetry-collector@pdata/v1.62.0...pdata/v1.63.0)

Updates `go.opentelemetry.io/collector/receiver/otlpreceiver` from 0.156.0 to 0.157.0
- [Release notes](https://github.com/open-telemetry/opentelemetry-collector/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CHANGELOG-API.md)
- [Commits](open-telemetry/opentelemetry-collector@v0.156.0...v0.157.0)

Updates `google.golang.org/grpc` from 1.82.0 to 1.82.1
- [Release notes](https://github.com/grpc/grpc-go/releases)
- [Commits](grpc/grpc-go@v1.82.0...v1.82.1)

---
updated-dependencies:
- dependency-name: github.com/dash0hq/dash0-api-client-go
  dependency-version: 1.17.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/collector/component
  dependency-version: 1.63.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/collector/config/configgrpc
  dependency-version: 0.157.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/collector/config/confighttp
  dependency-version: 0.157.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/collector/config/configoptional
  dependency-version: 1.63.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/collector/consumer
  dependency-version: 1.63.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/collector/consumer/consumererror
  dependency-version: 0.157.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/collector/pdata
  dependency-version: 1.63.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/collector/receiver
  dependency-version: 1.63.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: go.opentelemetry.io/collector/receiver/otlpreceiver
  dependency-version: 0.157.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go-deps
- dependency-name: google.golang.org/grpc
  dependency-version: 1.82.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: go-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Jul 22, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner July 22, 2026 23:25
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Jul 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants