t.behrendt/tracebasedlogsampler
1
0
Fork 0
Code Issues 1 Pull Requests 3 Actions Packages Releases Activity

chore(deps): update module go.opentelemetry.io/collector/processor/processortest to v0.147.0 #38

Merged
t.behrendt merged 1 commits from renovate/go.opentelemetry.io-collector-processor-processortest-0.x into main 2026-03-19 08:02:35 +01:00
Conversation 2 Commits 1 Files Changed 2 +70 -25
renovate-bot commented 2026-02-15 00:27:10 +01:00
Collaborator
Copy Link

This PR contains the following updates:

Package Change Age Confidence
go.opentelemetry.io/collector/processor/processortest v0.144.0 → v0.147.0 age confidence

Release Notes

open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/processor/processortest)

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)

v0.146.1

Compare Source

v0.146.0

Compare Source

🛑 Breaking changes 🛑
  • all: Increase minimum Go version to 1.25 (#​14567)
🚩 Deprecations 🚩
  • pdata/pprofile: Declare removed aggregation elements as deprecated. (#​14528)
💡 Enhancements 💡

  • all: Add detailed failure attributes to exporter send_failed metrics at detailed telemetry level. (#​13956)
    The otelcol_exporter_send_failed_{spans,metric_points,log_records} metrics now include
    failure attributes when telemetry level is Detailed: error.type (OpenTelemetry semantic convention
    describing the error class) and error.permanent (indicates if error is permanent/non-retryable).
    The error.type attribute captures gRPC status codes (e.g., "Unavailable", "ResourceExhausted"),
    standard Go context errors (e.g., "canceled", "deadline_exceeded"),
    and collector-specific errors (e.g., "shutdown").
    This enables better alerting and debugging by providing standardized error classification.

  • cmd/builder: Introduce new experimental init subcommand (#​14530)
    The new init subcommand initializes a new custom collector

  • cmd/builder: Add "telemetry" field to allow configuring telemetry providers (#​14575)
    Most users should not need to use this, this field should only be set if you
    intend to provide your own OpenTelemetry SDK.

  • cmd/mdatagen: Introduce additional metadata (the version since the deprecation started, and the deprecation reason) for deprecated metrics. (#​14113)

  • cmd/mdatagen: Add optional relationships field to entity schema in metadata.yaml (#​14284)

  • exporter/debug: Add output_paths configuration option to control output destination when use_internal_logger is false. (#​10472)
    When use_internal_logger is set to false, the debug exporter now supports configuring the output destination via the output_paths option.
    This allows users to send debug exporter output to stdout, stderr, or a file path.
    The default value is ["stdout"] to maintain backward compatibility.

  • pkg/confmap: Add experimental ToStringMapRaw function to decode confmap.Conf into a string map without losing internal types (#​14480)
    This method exposes the internal structure of a confmap.Conf which may change at any time without prior notice

🧰 Bug fixes 🧰
  • cmd/mdatagen: Reset aggDataPoints during metric init to avoid index out of range panic across emit cycles when reaggregation is enabled. (#​14569)
  • cmd/mdatagen: Fix panic when mdatagen is run without arguments. (#​14506)
  • pdata/pprofile: Fix off-by-one issue in dictionary lookups. (#​14534)
  • pkg/config/confighttp: Fix high cardinality span name from request method from confighttp server internal telemetry (#​14516)
    Follow spec to bound request method cardinality.
  • pkg/otelcol: Ignore component aliases in the otelcol components command (#​14492)
  • pkg/otelcol: Order providers and converters in alphabetical order in the components subcommand. (#​14476)

v0.145.0

Compare Source

💡 Enhancements 💡
  • pkg/scraperhelper: ScraperID has been added to the logs for metrics, logs, and profiles (#​14461)
🧰 Bug fixes 🧰

  • exporter/otlp_grpc: Fix the OTLP exporter balancer to use round_robin by default, as intended. (#​14090)

  • pkg/config/configoptional: Fix Unmarshal methods not being called when config is wrapped inside Optional (#​14500)
    This bug notably manifested in the fact that the sending_queue::batch::sizer config for exporters
    stopped defaulting to sending_queue::sizer, which sometimes caused the wrong units to be used
    when configuring sending_queue::batch::min_size and max_size.

    As part of the fix, xconfmap exposes a new xconfmap.WithForceUnmarshaler option, to be used in the Unmarshal methods
    of wrapper types like configoptional.Optional to make sure the Unmarshal method of the inner type is called.

    The default behavior remains that calling conf.Unmarshal on the confmap.Conf passed as argument to an Unmarshal
    method will skip any top-level Unmarshal methods to avoid infinite recursion in standard use cases.

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

  • pkg/service: Don't error on startup when process metrics are enabled on unsupported OSes (e.g. AIX) (#​14307)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [go.opentelemetry.io/collector/processor/processortest](https://github.com/open-telemetry/opentelemetry-collector) | `v0.144.0` → `v0.147.0` | ![age](https://developer.mend.io/api/mc/badges/age/go/go.opentelemetry.io%2fcollector%2fprocessor%2fprocessortest/v0.147.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/go.opentelemetry.io%2fcollector%2fprocessor%2fprocessortest/v0.144.0/v0.147.0?slim=true) | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/processor/processortest)</summary> ### [`v0.147.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1530v01470) [Compare Source](https://github.com/open-telemetry/opentelemetry-collector/compare/v0.146.1...v0.147.0) ##### 💡 Enhancements 💡 - `exporter/debug`: Output bucket counts for exponential histogram data points in normal verbosity. ([#&#8203;10463](https://github.com/open-telemetry/opentelemetry-collector/issues/10463)) - `pkg/exporterhelper`: Add `metadata_keys` configuration to `sending_queue.batch.partition` to partition batches by client metadata ([#&#8203;14139](https://github.com/open-telemetry/opentelemetry-collector/issues/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. ([#&#8203;14436](https://github.com/open-telemetry/opentelemetry-collector/issues/14436)) - `cmd/mdatagen`: Fix duplicate error output when CLI command execution fails in the mdatagen tool. ([#&#8203;14436](https://github.com/open-telemetry/opentelemetry-collector/issues/14436)) - `cmd/mdatagen`: Fix semconv URL validation for metrics with underscores in their names ([#&#8203;14583](https://github.com/open-telemetry/opentelemetry-collector/issues/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. ([#&#8203;14634](https://github.com/open-telemetry/opentelemetry-collector/issues/14634)) If multiple extensions that use the UnaryInterceptor are set the binary panics at start time. - `extension/memory_limiter`: Add support for streaming services. ([#&#8203;14634](https://github.com/open-telemetry/opentelemetry-collector/issues/14634)) - `pkg/config/configmiddleware`: Add context.Context to HTTP middleware interface constructors. ([#&#8203;14523](https://github.com/open-telemetry/opentelemetry-collector/issues/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. ([#&#8203;14034](https://github.com/open-telemetry/opentelemetry-collector/issues/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. ([#&#8203;14554](https://github.com/open-telemetry/opentelemetry-collector/issues/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. ([#&#8203;14491](https://github.com/open-telemetry/opentelemetry-collector/issues/14491)) - `pkg/scraperhelper`: Log scrapers now emit log-appropriate receiver telemetry ([#&#8203;14654](https://github.com/open-telemetry/opentelemetry-collector/issues/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. ([#&#8203;12279](https://github.com/open-telemetry/opentelemetry-collector/issues/12279), [#&#8203;14620](https://github.com/open-telemetry/opentelemetry-collector/issues/14620)) <!-- previous-version --> ### [`v0.146.1`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1520v01461) [Compare Source](https://github.com/open-telemetry/opentelemetry-collector/compare/v0.146.0...v0.146.1) <!-- previous-version --> ### [`v0.146.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v01460) [Compare Source](https://github.com/open-telemetry/opentelemetry-collector/compare/v0.145.0...v0.146.0) ##### 🛑 Breaking changes 🛑 - `all`: Increase minimum Go version to 1.25 ([#&#8203;14567](https://github.com/open-telemetry/opentelemetry-collector/issues/14567)) ##### 🚩 Deprecations 🚩 - `pdata/pprofile`: Declare removed aggregation elements as deprecated. ([#&#8203;14528](https://github.com/open-telemetry/opentelemetry-collector/issues/14528)) ##### 💡 Enhancements 💡 - `all`: Add detailed failure attributes to exporter send\_failed metrics at detailed telemetry level. ([#&#8203;13956](https://github.com/open-telemetry/opentelemetry-collector/issues/13956)) The `otelcol_exporter_send_failed_{spans,metric_points,log_records}` metrics now include failure attributes when telemetry level is Detailed: `error.type` (OpenTelemetry semantic convention describing the error class) and `error.permanent` (indicates if error is permanent/non-retryable). The `error.type` attribute captures gRPC status codes (e.g., "Unavailable", "ResourceExhausted"), standard Go context errors (e.g., "canceled", "deadline\_exceeded"), and collector-specific errors (e.g., "shutdown"). This enables better alerting and debugging by providing standardized error classification. - `cmd/builder`: Introduce new experimental `init` subcommand ([#&#8203;14530](https://github.com/open-telemetry/opentelemetry-collector/issues/14530)) The new `init` subcommand initializes a new custom collector - `cmd/builder`: Add "telemetry" field to allow configuring telemetry providers ([#&#8203;14575](https://github.com/open-telemetry/opentelemetry-collector/issues/14575)) Most users should not need to use this, this field should only be set if you intend to provide your own OpenTelemetry SDK. - `cmd/mdatagen`: Introduce additional metadata (the version since the deprecation started, and the deprecation reason) for deprecated metrics. ([#&#8203;14113](https://github.com/open-telemetry/opentelemetry-collector/issues/14113)) - `cmd/mdatagen`: Add optional `relationships` field to entity schema in metadata.yaml ([#&#8203;14284](https://github.com/open-telemetry/opentelemetry-collector/issues/14284)) - `exporter/debug`: Add `output_paths` configuration option to control output destination when `use_internal_logger` is false. ([#&#8203;10472](https://github.com/open-telemetry/opentelemetry-collector/issues/10472)) When `use_internal_logger` is set to `false`, the debug exporter now supports configuring the output destination via the `output_paths` option. This allows users to send debug exporter output to `stdout`, `stderr`, or a file path. The default value is `["stdout"]` to maintain backward compatibility. - `pkg/confmap`: Add experimental `ToStringMapRaw` function to decode `confmap.Conf` into a string map without losing internal types ([#&#8203;14480](https://github.com/open-telemetry/opentelemetry-collector/issues/14480)) This method exposes the internal structure of a `confmap.Conf` which may change at any time without prior notice ##### 🧰 Bug fixes 🧰 - `cmd/mdatagen`: Reset aggDataPoints during metric init to avoid index out of range panic across emit cycles when reaggregation is enabled. ([#&#8203;14569](https://github.com/open-telemetry/opentelemetry-collector/issues/14569)) - `cmd/mdatagen`: Fix panic when mdatagen is run without arguments. ([#&#8203;14506](https://github.com/open-telemetry/opentelemetry-collector/issues/14506)) - `pdata/pprofile`: Fix off-by-one issue in dictionary lookups. ([#&#8203;14534](https://github.com/open-telemetry/opentelemetry-collector/issues/14534)) - `pkg/config/confighttp`: Fix high cardinality span name from request method from confighttp server internal telemetry ([#&#8203;14516](https://github.com/open-telemetry/opentelemetry-collector/issues/14516)) Follow spec to bound request method cardinality. - `pkg/otelcol`: Ignore component aliases in the `otelcol components` command ([#&#8203;14492](https://github.com/open-telemetry/opentelemetry-collector/issues/14492)) - `pkg/otelcol`: Order providers and converters in alphabetical order in the `components` subcommand. ([#&#8203;14476](https://github.com/open-telemetry/opentelemetry-collector/issues/14476)) <!-- previous-version --> ### [`v0.145.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1510v01450) [Compare Source](https://github.com/open-telemetry/opentelemetry-collector/compare/v0.144.0...v0.145.0) ##### 💡 Enhancements 💡 - `pkg/scraperhelper`: ScraperID has been added to the logs for metrics, logs, and profiles ([#&#8203;14461](https://github.com/open-telemetry/opentelemetry-collector/issues/14461)) ##### 🧰 Bug fixes 🧰 - `exporter/otlp_grpc`: Fix the OTLP exporter balancer to use round\_robin by default, as intended. ([#&#8203;14090](https://github.com/open-telemetry/opentelemetry-collector/issues/14090)) - `pkg/config/configoptional`: Fix `Unmarshal` methods not being called when config is wrapped inside `Optional` ([#&#8203;14500](https://github.com/open-telemetry/opentelemetry-collector/issues/14500)) This bug notably manifested in the fact that the `sending_queue::batch::sizer` config for exporters stopped defaulting to `sending_queue::sizer`, which sometimes caused the wrong units to be used when configuring `sending_queue::batch::min_size` and `max_size`. As part of the fix, `xconfmap` exposes a new `xconfmap.WithForceUnmarshaler` option, to be used in the `Unmarshal` methods of wrapper types like `configoptional.Optional` to make sure the `Unmarshal` method of the inner type is called. The default behavior remains that calling `conf.Unmarshal` on the `confmap.Conf` passed as argument to an `Unmarshal` method will skip any top-level `Unmarshal` methods to avoid infinite recursion in standard use cases. - `pkg/confmap`: Fix an issue where configs could fail to decode when using interpolated values in string fields. ([#&#8203;14413](https://github.com/open-telemetry/opentelemetry-collector/issues/14413)) For example, a header can be set via an environment variable to a string that is parseable as a number, e.g. `1234` - `pkg/service`: Don't error on startup when process metrics are enabled on unsupported OSes (e.g. AIX) ([#&#8203;14307](https://github.com/open-telemetry/opentelemetry-collector/issues/14307)) <!-- previous-version --> </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My41LjQiLCJ1cGRhdGVkSW5WZXIiOiI0My41LjQiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->
renovate-bot added 1 commit 2026-02-15 00:27:10 +01:00
chore(deps): update module go.opentelemetry.io/collector/processor/processortest to v0.145.0
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
Details
CI / test (push) Successful in 1m11s
Details
2e567fed7c
renovate-bot commented 2026-02-15 00:27:11 +01:00
Author
Collaborator
Copy Link

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

  • 23 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.24.2 -> 1.25.0
go.opentelemetry.io/collector/component/componentstatus v0.144.0 -> v0.147.0
go.opentelemetry.io/collector/consumer/xconsumer v0.144.0 -> v0.147.0
go.opentelemetry.io/collector/featuregate v1.50.0 -> v1.53.0
go.opentelemetry.io/collector/internal/componentalias v0.144.0 -> v0.147.0
go.opentelemetry.io/collector/pdata/pprofile v0.144.0 -> v0.147.0
go.opentelemetry.io/collector/pdata/testdata v0.144.0 -> v0.147.0
go.opentelemetry.io/collector/pipeline v1.50.0 -> v1.53.0
go.opentelemetry.io/collector/processor/xprocessor v0.144.0 -> v0.147.0
go.opentelemetry.io/otel v1.39.0 -> v1.40.0
go.opentelemetry.io/otel/metric v1.39.0 -> v1.40.0
go.opentelemetry.io/otel/sdk v1.39.0 -> v1.40.0
go.opentelemetry.io/otel/sdk/metric v1.39.0 -> v1.40.0
go.opentelemetry.io/otel/trace v1.39.0 -> v1.40.0
golang.org/x/net v0.47.0 -> v0.51.0
golang.org/x/sys v0.39.0 -> v0.41.0
golang.org/x/text v0.31.0 -> v0.34.0
google.golang.org/grpc v1.78.0 -> v1.79.1
go.opentelemetry.io/collector/component v1.50.0 -> v1.53.0
go.opentelemetry.io/collector/component/componenttest v0.144.0 -> v0.147.0
go.opentelemetry.io/collector/consumer v1.50.0 -> v1.53.0
go.opentelemetry.io/collector/consumer/consumertest v0.144.0 -> v0.147.0
go.opentelemetry.io/collector/pdata v1.50.0 -> v1.53.0
go.opentelemetry.io/collector/processor v1.50.0 -> v1.53.0
### ℹ️ 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): - 23 additional dependencies were updated - The `go` directive was updated for compatibility reasons Details: | **Package** | **Change** | | :-------------------------------------------------------- | :----------------------- | | `go` | `1.24.2` -> `1.25.0` | | `go.opentelemetry.io/collector/component/componentstatus` | `v0.144.0` -> `v0.147.0` | | `go.opentelemetry.io/collector/consumer/xconsumer` | `v0.144.0` -> `v0.147.0` | | `go.opentelemetry.io/collector/featuregate` | `v1.50.0` -> `v1.53.0` | | `go.opentelemetry.io/collector/internal/componentalias` | `v0.144.0` -> `v0.147.0` | | `go.opentelemetry.io/collector/pdata/pprofile` | `v0.144.0` -> `v0.147.0` | | `go.opentelemetry.io/collector/pdata/testdata` | `v0.144.0` -> `v0.147.0` | | `go.opentelemetry.io/collector/pipeline` | `v1.50.0` -> `v1.53.0` | | `go.opentelemetry.io/collector/processor/xprocessor` | `v0.144.0` -> `v0.147.0` | | `go.opentelemetry.io/otel` | `v1.39.0` -> `v1.40.0` | | `go.opentelemetry.io/otel/metric` | `v1.39.0` -> `v1.40.0` | | `go.opentelemetry.io/otel/sdk` | `v1.39.0` -> `v1.40.0` | | `go.opentelemetry.io/otel/sdk/metric` | `v1.39.0` -> `v1.40.0` | | `go.opentelemetry.io/otel/trace` | `v1.39.0` -> `v1.40.0` | | `golang.org/x/net` | `v0.47.0` -> `v0.51.0` | | `golang.org/x/sys` | `v0.39.0` -> `v0.41.0` | | `golang.org/x/text` | `v0.31.0` -> `v0.34.0` | | `google.golang.org/grpc` | `v1.78.0` -> `v1.79.1` | | `go.opentelemetry.io/collector/component` | `v1.50.0` -> `v1.53.0` | | `go.opentelemetry.io/collector/component/componenttest` | `v0.144.0` -> `v0.147.0` | | `go.opentelemetry.io/collector/consumer` | `v1.50.0` -> `v1.53.0` | | `go.opentelemetry.io/collector/consumer/consumertest` | `v0.144.0` -> `v0.147.0` | | `go.opentelemetry.io/collector/pdata` | `v1.50.0` -> `v1.53.0` | | `go.opentelemetry.io/collector/processor` | `v1.50.0` -> `v1.53.0` |
renovate-bot changed title from chore(deps): update module go.opentelemetry.io/collector/processor/processortest to v0.145.0 to chore(deps): update module go.opentelemetry.io/collector/processor/processortest to v0.146.1 2026-02-25 12:13:56 +01:00
renovate-bot force-pushed renovate/go.opentelemetry.io-collector-processor-processortest-0.x from 2e567fed7c to 8f3efe3c10 2026-02-25 12:13:56 +01:00 Compare
renovate-bot changed title from chore(deps): update module go.opentelemetry.io/collector/processor/processortest to v0.146.1 to chore(deps): update module go.opentelemetry.io/collector/processor/processortest to v0.147.0 2026-03-10 12:20:01 +01:00
renovate-bot force-pushed renovate/go.opentelemetry.io-collector-processor-processortest-0.x from 8f3efe3c10 to 42addad6eb 2026-03-10 12:20:02 +01:00 Compare
t.behrendt approved these changes 2026-03-19 08:02:31 +01:00
t.behrendt merged commit 440d77600f into main 2026-03-19 08:02:35 +01:00
t.behrendt deleted branch renovate/go.opentelemetry.io-collector-processor-processortest-0.x 2026-03-19 08:02:35 +01:00
Sign in to join this conversation.
Reviewers
No Reviewers
t.behrendt
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
branch-buddy renovate-bot trivy-bot t.behrendt
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: t.behrendt/tracebasedlogsampler#38
Delete Branch "renovate/go.opentelemetry.io-collector-processor-processortest-0.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?