build(deps): bump go.opentelemetry.io/collector/component/componenttest in /xpumd/exporter/intelxpuinfo

[dependabot]

Bumps go.opentelemetry.io/collector/component/componenttest in /xpumd/exporter/intelxpuinfo from 0.157.0 to 0.158.0.

Updates go.opentelemetry.io/collector/component/componenttest from 0.157.0 to 0.158.0

Release notes

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

v1.64.0/v0.158.0

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

End User Changelog

🚀 New components 🚀

• processor/queuebatch: New queuebatchprocessor to replace the legacy batchprocessor. (#15047, #13582, #12022, #11308, #8272, #6046) New implementation is based exporterhelper, uses same configuration as sending_queue.

💡 Enhancements 💡

• cmd/mdatagen: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml (#15513) Authors can now write type: int64, type: duration, type: opaque_string, type: id, or type: opaque_map directly as a property type in the config: section of metadata.yaml. Each alias expands to the correct JSON Schema representation and Go type automatically. Existing uses of standard JSON Schema types, format:, and x-customType: remain supported without migration.

• extension/memory_limiter: Promote the memory limiter extension to beta stability. (#14533)

🧰 Bug fixes 🧰

• cmd/mdatagen: Removes the extra line in the documentation.md around description (#15664)

• cmd/mdatagen: Auto-enable v1 metrics when legacy metric is enabled and v1 feature gate is on (#15650) When the v1 feature gate is enabled and a legacy metric is enabled, the corresponding v1 metric is now programmatically enabled so users don't need to add the v1 metric to their config.

• cmd/mdatagen: Fix incorrect collision warning for versioned metrics with different emitted names (#15648) Same name collision detection (type/attribute checks) was being used for versioned metrics with different names. This caused the legacy metric to be disabled which was incorrect and also a warning msg was being incorrectly logged that stated the metrics had the same name when in fact they had different names.

• cmd/mdatagen: Versioned metrics don't handle renamed attributes with same type (#15595) Versioned metrics need to support emitting legacy and latest attributes when the metric name is the same but the attributes names differ. This was not working when the attributes name changed but the type remained the same. Here we add support to versioned metrics with renamed attributes where those attributes have the same type.

• exporter/debug: Fix profile sample attribute formatting for non-string values (#15647) Previously, non-string values produced malformed output such as %!s(int64=42). Profile sample attributes now use the debug exporter's typed attribute format, such as Int(42). This will also change strings from hello-world to Str(hello-world).

• pkg/config/configtls: Fix goroutine and file descriptor leak when client_ca_file_reload is enabled (#9221) Every call to ServerConfig.LoadTLSConfig with client_ca_file_reload enabled started a file watcher goroutine that could never be stopped, since the reloader was not reachable from the returned *tls.Config. The client CA file is now checked for changes while TLS handshakes are served, at most once per second, matching how reload_interval already

... (truncated)

Changelog

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

v1.64.0/v0.158.0

🛑 Breaking changes 🛑

• pkg/xconfmap: Remove Validator and Validate (#15613) Use the equivalent symbols in confmap instead.

💡 Enhancements 💡

• cmd/mdatagen: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml (#15513) Authors can now write type: int64, type: duration, type: opaque_string, type: id, or type: opaque_map directly as a property type in the config: section of metadata.yaml. Each alias expands to the correct JSON Schema representation and Go type automatically. Existing uses of standard JSON Schema types, format:, and x-customType: remain supported without migration.

• pkg/config/configgrpc: Mark configgrpc as stable (#9477)

Commits

• 0378e9a [chore] Prepare release v1.64.0/v0.158.0 (#15709)
• 18ed8fe [chore] Use mdatagen for configopaque and configtelemetry (#15696)
• 0ffbf34 [pkg/config/configtls] Don't leak a goroutine for client CA reload (#15678)
• 4aa1b2d [configgrpc] Mark module as 1.x (#15609)
• aa682d1 [chore] Prevent unkeyed literal initialization on confighttp structs (#15688)
• bdf869e [chore][config/configauth] Migrate to mdatagen driven configuration (#15641)
• e864743 Update module go.opentelemetry.io/proto/otlp to v1.11.0 (#15670)
• 9cbfc4b [chore][docs] Update graceful shutdown section in coding-guidelines (#15631)
• 6560a21 [xconfmap] Remove Validator and Validate (#15613)
• 7bc5915 [bug][mdatagen] Auto-enable v1 metrics when legacy is enabled (#15651)
• Additional commits viewable in compare view

Updates go.opentelemetry.io/collector/component/componenttest from 0.157.0 to 0.158.0

Release notes

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

v1.64.0/v0.158.0

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

End User Changelog

🚀 New components 🚀

• processor/queuebatch: New queuebatchprocessor to replace the legacy batchprocessor. (#15047, #13582, #12022, #11308, #8272, #6046) New implementation is based exporterhelper, uses same configuration as sending_queue.

💡 Enhancements 💡

• cmd/mdatagen: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml (#15513) Authors can now write type: int64, type: duration, type: opaque_string, type: id, or type: opaque_map directly as a property type in the config: section of metadata.yaml. Each alias expands to the correct JSON Schema representation and Go type automatically. Existing uses of standard JSON Schema types, format:, and x-customType: remain supported without migration.

• extension/memory_limiter: Promote the memory limiter extension to beta stability. (#14533)

🧰 Bug fixes 🧰

• cmd/mdatagen: Removes the extra line in the documentation.md around description (#15664)

• cmd/mdatagen: Auto-enable v1 metrics when legacy metric is enabled and v1 feature gate is on (#15650) When the v1 feature gate is enabled and a legacy metric is enabled, the corresponding v1 metric is now programmatically enabled so users don't need to add the v1 metric to their config.

• cmd/mdatagen: Fix incorrect collision warning for versioned metrics with different emitted names (#15648) Same name collision detection (type/attribute checks) was being used for versioned metrics with different names. This caused the legacy metric to be disabled which was incorrect and also a warning msg was being incorrectly logged that stated the metrics had the same name when in fact they had different names.

• cmd/mdatagen: Versioned metrics don't handle renamed attributes with same type (#15595) Versioned metrics need to support emitting legacy and latest attributes when the metric name is the same but the attributes names differ. This was not working when the attributes name changed but the type remained the same. Here we add support to versioned metrics with renamed attributes where those attributes have the same type.

• exporter/debug: Fix profile sample attribute formatting for non-string values (#15647) Previously, non-string values produced malformed output such as %!s(int64=42). Profile sample attributes now use the debug exporter's typed attribute format, such as Int(42). This will also change strings from hello-world to Str(hello-world).

• pkg/config/configtls: Fix goroutine and file descriptor leak when client_ca_file_reload is enabled (#9221) Every call to ServerConfig.LoadTLSConfig with client_ca_file_reload enabled started a file watcher goroutine that could never be stopped, since the reloader was not reachable from the returned *tls.Config. The client CA file is now checked for changes while TLS handshakes are served, at most once per second, matching how reload_interval already

... (truncated)

Changelog

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

v1.64.0/v0.158.0

🛑 Breaking changes 🛑

• pkg/xconfmap: Remove Validator and Validate (#15613) Use the equivalent symbols in confmap instead.

💡 Enhancements 💡

• cmd/mdatagen: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml (#15513) Authors can now write type: int64, type: duration, type: opaque_string, type: id, or type: opaque_map directly as a property type in the config: section of metadata.yaml. Each alias expands to the correct JSON Schema representation and Go type automatically. Existing uses of standard JSON Schema types, format:, and x-customType: remain supported without migration.

• pkg/config/configgrpc: Mark configgrpc as stable (#9477)

Commits

• 0378e9a [chore] Prepare release v1.64.0/v0.158.0 (#15709)
• 18ed8fe [chore] Use mdatagen for configopaque and configtelemetry (#15696)
• 0ffbf34 [pkg/config/configtls] Don't leak a goroutine for client CA reload (#15678)
• 4aa1b2d [configgrpc] Mark module as 1.x (#15609)
• aa682d1 [chore] Prevent unkeyed literal initialization on confighttp structs (#15688)
• bdf869e [chore][config/configauth] Migrate to mdatagen driven configuration (#15641)
• e864743 Update module go.opentelemetry.io/proto/otlp to v1.11.0 (#15670)
• 9cbfc4b [chore][docs] Update graceful shutdown section in coding-guidelines (#15631)
• 6560a21 [xconfmap] Remove Validator and Validate (#15613)
• 7bc5915 [bug][mdatagen] Auto-enable v1 metrics when legacy is enabled (#15651)
• Additional commits viewable in compare view

Updates go.opentelemetry.io/collector/component/componenttest from 0.157.0 to 0.158.0

Release notes

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

v1.64.0/v0.158.0

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

End User Changelog

🚀 New components 🚀

• processor/queuebatch: New queuebatchprocessor to replace the legacy batchprocessor. (#15047, #13582, #12022, #11308, #8272, #6046) New implementation is based exporterhelper, uses same configuration as sending_queue.

💡 Enhancements 💡

• cmd/mdatagen: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml (#15513) Authors can now write type: int64, type: duration, type: opaque_string, type: id, or type: opaque_map directly as a property type in the config: section of metadata.yaml. Each alias expands to the correct JSON Schema representation and Go type automatically. Existing uses of standard JSON Schema types, format:, and x-customType: remain supported without migration.

• extension/memory_limiter: Promote the memory limiter extension to beta stability. (#14533)

🧰 Bug fixes 🧰

• cmd/mdatagen: Removes the extra line in the documentation.md around description (#15664)

• cmd/mdatagen: Auto-enable v1 metrics when legacy metric is enabled and v1 feature gate is on (#15650) When the v1 feature gate is enabled and a legacy metric is enabled, the corresponding v1 metric is now programmatically enabled so users don't need to add the v1 metric to their config.

• cmd/mdatagen: Fix incorrect collision warning for versioned metrics with different emitted names (#15648) Same name collision detection (type/attribute checks) was being used for versioned metrics with different names. This caused the legacy metric to be disabled which was incorrect and also a warning msg was being incorrectly logged that stated the metrics had the same name when in fact they had different names.

• cmd/mdatagen: Versioned metrics don't handle renamed attributes with same type (#15595) Versioned metrics need to support emitting legacy and latest attributes when the metric name is the same but the attributes names differ. This was not working when the attributes name changed but the type remained the same. Here we add support to versioned metrics with renamed attributes where those attributes have the same type.

• exporter/debug: Fix profile sample attribute formatting for non-string values (#15647) Previously, non-string values produced malformed output such as %!s(int64=42). Profile sample attributes now use the debug exporter's typed attribute format, such as Int(42). This will also change strings from hello-world to Str(hello-world).

• pkg/config/configtls: Fix goroutine and file descriptor leak when client_ca_file_reload is enabled (#9221) Every call to ServerConfig.LoadTLSConfig with client_ca_file_reload enabled started a file watcher goroutine that could never be stopped, since the reloader was not reachable from the returned *tls.Config. The client CA file is now checked for changes while TLS handshakes are served, at most once per second, matching how reload_interval already

... (truncated)

Changelog

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

v1.64.0/v0.158.0

🛑 Breaking changes 🛑

• pkg/xconfmap: Remove Validator and Validate (#15613) Use the equivalent symbols in confmap instead.

💡 Enhancements 💡

• cmd/mdatagen: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml (#15513) Authors can now write type: int64, type: duration, type: opaque_string, type: id, or type: opaque_map directly as a property type in the config: section of metadata.yaml. Each alias expands to the correct JSON Schema representation and Go type automatically. Existing uses of standard JSON Schema types, format:, and x-customType: remain supported without migration.

• pkg/config/configgrpc: Mark configgrpc as stable (#9477)

Commits

• 0378e9a [chore] Prepare release v1.64.0/v0.158.0 (#15709)
• 18ed8fe [chore] Use mdatagen for configopaque and configtelemetry (#15696)
• 0ffbf34 [pkg/config/configtls] Don't leak a goroutine for client CA reload (#15678)
• 4aa1b2d [configgrpc] Mark module as 1.x (#15609)
• aa682d1 [chore] Prevent unkeyed literal initialization on confighttp structs (#15688)
• bdf869e [chore][config/configauth] Migrate to mdatagen driven configuration (#15641)
• e864743 Update module go.opentelemetry.io/proto/otlp to v1.11.0 (#15670)
• 9cbfc4b [chore][docs] Update graceful shutdown section in coding-guidelines (#15631)
• 6560a21 [xconfmap] Remove Validator and Validate (#15613)
• 7bc5915 [bug][mdatagen] Auto-enable v1 metrics when legacy is enabled (#15651)
• Additional commits viewable in compare view

Updates go.opentelemetry.io/collector/component/componenttest from 0.157.0 to 0.158.0

Release notes

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

v1.64.0/v0.158.0

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

End User Changelog

🚀 New components 🚀

• processor/queuebatch: New queuebatchprocessor to replace the legacy batchprocessor. (#15047, #13582, #12022, #11308, #8272, #6046) New implementation is based exporterhelper, uses same configuration as sending_queue.

💡 Enhancements 💡

• cmd/mdatagen: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml (#15513) Authors can now write type: int64, type: duration, type: opaque_string, type: id, or type: opaque_map directly as a property type in the config: section of metadata.yaml. Each alias expands to the correct JSON Schema representation and Go type automatically. Existing uses of standard JSON Schema types, format:, and x-customType: remain supported without migration.

• extension/memory_limiter: Promote the memory limiter extension to beta stability. (#14533)

🧰 Bug fixes 🧰

• cmd/mdatagen: Removes the extra line in the documentation.md around description (#15664)

• cmd/mdatagen: Auto-enable v1 metrics when legacy metric is enabled and v1 feature gate is on (#15650) When the v1 feature gate is enabled and a legacy metric is enabled, the corresponding v1 metric is now programmatically enabled so users don't need to add the v1 metric to their config.

• cmd/mdatagen: Fix incorrect collision warning for versioned metrics with different emitted names (#15648) Same name collision detection (type/attribute checks) was being used for versioned metrics with different names. This caused the legacy metric to be disabled which was incorrect and also a warning msg was being incorrectly logged that stated the metrics had the same name when in fact they had different names.

• cmd/mdatagen: Versioned metrics don't handle renamed attributes with same type (#15595) Versioned metrics need to support emitting legacy and latest attributes when the metric name is the same but the attributes names differ. This was not working when the attributes name changed but the type remained the same. Here we add support to versioned metrics with renamed attributes where those attributes have the same type.

• exporter/debug: Fix profile sample attribute formatting for non-string values (#15647) Previously, non-string values produced malformed output such as %!s(int64=42). Profile sample attributes now use the debug exporter's typed attribute format, such as Int(42). This will also change strings from hello-world to Str(hello-world).

• pkg/config/configtls: Fix goroutine and file descriptor leak when client_ca_file_reload is enabled (#9221) Every call to ServerConfig.LoadTLSConfig with client_ca_file_reload enabled started a file watcher goroutine that could never be stopped, since the reloader was not reachable from the returned *tls.Config. The client CA file is now checked for changes while TLS handshakes are served, at most once per second, matching how reload_interval already

... (truncated)

Changelog

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

v1.64.0/v0.158.0

🛑 Breaking changes 🛑

• pkg/xconfmap: Remove Validator and Validate (#15613) Use the equivalent symbols in confmap instead.

💡 Enhancements 💡

• cmd/mdatagen: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml (#15513) Authors can now write type: int64, type: duration, type: opaque_string, type: id, or type: opaque_map directly as a property type in the config: section of metadata.yaml. Each alias expands to the correct JSON Schema representation and Go type automatically. Existing uses of standard JSON Schema types, format:, and x-customType: remain supported without migration.

• pkg/config/configgrpc: Mark configgrpc as stable (#9477)

Commits

• 0378e9a [chore] Prepare release v1.64.0/v0.158.0 (#15709)
• 18ed8fe [chore] Use mdatagen for configopaque and configtelemetry (#15696)
• 0ffbf34 [pkg/config/configtls] Don't leak a goroutine for client CA reload (#15678)
• 4aa1b2d [configgrpc] Mark module as 1.x (#15609)
• aa682d1 [chore] Prevent unkeyed literal initialization on confighttp structs (#15688)
• bdf869e [chore][config/configauth] Migrate to mdatagen driven configuration (#15641)
• e864743 Update module go.opentelemetry.io/proto/otlp to v1.11.0 (#15670)
• 9cbfc4b [chore][docs] Update graceful shutdown section in coding-guidelines (#15631)
• 6560a21 [xconfmap] Remove Validator and Validate (#15613)
• 7bc5915 [bug][mdatagen] Auto-enable v1 metrics when legacy is enabled (#15651)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions