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/component/componenttest to v0.148.0 - autoclosed #32

Closed
renovate-bot wants to merge 1 commits from renovate/go.opentelemetry.io-collector-component-componenttest-0.x into main
pull from: renovate/go.opentelemetry.io-collector-component-componenttest-0.x
merge into: t.behrendt:main
Conversation 1 Commits 1 Files Changed 2 +29 -10
renovate-bot commented 2026-02-15 00:26:59 +01:00
Collaborator
Copy Link

This PR contains the following updates:

Package Change Age Confidence
go.opentelemetry.io/collector/component/componenttest v0.147.0 → v0.148.0 age confidence

Release Notes

open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/component/componenttest)

v0.148.0

Compare Source

❗ Known Issues ❗
  • service: The collector's internal Prometheus metrics endpoint (:8888) now emits OTel service labels with underscore
    names (service_name, service_instance_id, service_version) instead of dot-notation names (service.name,
    service.instance.id, service.version). Users scraping this endpoint with the Prometheus receiver will see these renamed
    labels in resource and datapoint attributes. As a workaround, add the following metric_relabel_configs to your scrape
    config in prometheus receiver: 
    metric_relabel_configs:
  - source_labels: [service_name]
    target_label: service.name
  - source_labels: [service_instance_id]
    target_label: service.instance.id
  - source_labels: [service_version]
    target_label: service.version
  - regex: service_name|service_instance_id|service_version
    action: labeldrop
    See #​14814 for details and updates.
🛑 Breaking changes 🛑
  • all: Change metric units to be singular to match OTel specification, e.g. {requests} -> {request} (#​14753)
💡 Enhancements 💡
  • cmd/mdatagen: Add deprecated_type field to allow specifying an alias for component types. (#​14718)
  • cmd/mdatagen: Generate entity-scoped MetricsBuilder API that enforces entity-metric associations at compile time (#​14659)
  • cmd/mdatagen: Skip generating reaggregation config options for metrics that have no aggregatable attributes. (#​14689)
  • pkg/service: The internal status reporter no longer drops repeated Ok and RecoverableError statuses (#​14282)
    Status events can now carry metadata and there's value in allowing them to be emitted despite the status value itself
    not changing.
🧰 Bug fixes 🧰

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

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

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

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

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

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

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/component/componenttest](https://github.com/open-telemetry/opentelemetry-collector) | `v0.147.0` → `v0.148.0` | ![age](https://developer.mend.io/api/mc/badges/age/go/go.opentelemetry.io%2fcollector%2fcomponent%2fcomponenttest/v0.148.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/go.opentelemetry.io%2fcollector%2fcomponent%2fcomponenttest/v0.147.0/v0.148.0?slim=true) | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/component/componenttest)</summary> ### [`v0.148.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1540v01480) [Compare Source](https://github.com/open-telemetry/opentelemetry-collector/compare/v0.147.0...v0.148.0) ##### ❗ Known Issues ❗ - `service`: The collector's internal Prometheus metrics endpoint (`:8888`) now emits OTel service labels with underscore names (`service_name`, `service_instance_id`, `service_version`) instead of dot-notation names (`service.name`, `service.instance.id`, `service.version`). Users scraping this endpoint with the Prometheus receiver will see these renamed labels in resource and datapoint attributes. As a workaround, add the following `metric_relabel_configs` to your scrape config in prometheus receiver: ```yaml metric_relabel_configs: - source_labels: [service_name] target_label: service.name - source_labels: [service_instance_id] target_label: service.instance.id - source_labels: [service_version] target_label: service.version - regex: service_name|service_instance_id|service_version action: labeldrop ``` See [#&#8203;14814](https://github.com/open-telemetry/opentelemetry-collector/issues/14814) for details and updates. ##### 🛑 Breaking changes 🛑 - `all`: Change metric units to be singular to match OTel specification, e.g. `{requests}` -> `{request}` ([#&#8203;14753](https://github.com/open-telemetry/opentelemetry-collector/issues/14753)) ##### 💡 Enhancements 💡 - `cmd/mdatagen`: Add deprecated\_type field to allow specifying an alias for component types. ([#&#8203;14718](https://github.com/open-telemetry/opentelemetry-collector/issues/14718)) - `cmd/mdatagen`: Generate entity-scoped MetricsBuilder API that enforces entity-metric associations at compile time ([#&#8203;14659](https://github.com/open-telemetry/opentelemetry-collector/issues/14659)) - `cmd/mdatagen`: Skip generating reaggregation config options for metrics that have no aggregatable attributes. ([#&#8203;14689](https://github.com/open-telemetry/opentelemetry-collector/issues/14689)) - `pkg/service`: The internal status reporter no longer drops repeated Ok and RecoverableError statuses ([#&#8203;14282](https://github.com/open-telemetry/opentelemetry-collector/issues/14282)) Status events can now carry metadata and there's value in allowing them to be emitted despite the status value itself not changing. ##### 🧰 Bug fixes 🧰 - `cmd/builder`: Add `.exe` to output binary names when building for Windows targets. ([#&#8203;12591](https://github.com/open-telemetry/opentelemetry-collector/issues/12591)) - `exporter/debug`: Add printing of metric metadata in detailed verbosity. ([#&#8203;14667](https://github.com/open-telemetry/opentelemetry-collector/issues/14667)) - `exporter/otlp_grpc`: Prevent nil pointer panic when push methods are called before the OTLP exporter initializes its gRPC clients. ([#&#8203;14663](https://github.com/open-telemetry/opentelemetry-collector/issues/14663)) When the sending queue and retry are disabled, calling ConsumeTraces, ConsumeMetrics, ConsumeLogs, or ConsumeProfiles before the OTLP exporter initializes its gRPC clients could cause a nil pointer dereference panic. The push methods now return an error instead of panicking. - `exporter/otlp_http`: Show the actual destination URL in error messages when request URL is modified by middleware. ([#&#8203;14673](https://github.com/open-telemetry/opentelemetry-collector/issues/14673)) Unwraps the `*url.Error` returned by `http.Client.Do()` to prevent misleading error logs when a middleware extension dynamically updates the endpoint. - `pdata/pprofile`: Switch the dictionary of dictionary tables entries only once when merging profiles ([#&#8203;14709](https://github.com/open-telemetry/opentelemetry-collector/issues/14709)) For dictionary table data, we used to switch their dictionaries when doing the switch for the data that uses them. However, when an entry is associated with multiple other data (several samples can use the same stack), we would have been switching the dictionaries of the entry multiple times. We now switch dictionaries for dictionary table data only once, before switching the resource profiles. <!-- 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:00 +01:00
chore(deps): update module go.opentelemetry.io/collector/component/componenttest to v0.145.0
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
Details
CI / test (push) Successful in 2m2s
Details
83afde8efd
renovate-bot commented 2026-02-15 00:27:00 +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):

  • 9 additional dependencies were updated

Details:

Package Change
go.opentelemetry.io/collector/featuregate v1.53.0 -> v1.54.0
go.opentelemetry.io/otel v1.40.0 -> v1.42.0
go.opentelemetry.io/otel/metric v1.40.0 -> v1.42.0
go.opentelemetry.io/otel/sdk v1.40.0 -> v1.42.0
go.opentelemetry.io/otel/sdk/metric v1.40.0 -> v1.42.0
go.opentelemetry.io/otel/trace v1.40.0 -> v1.42.0
google.golang.org/grpc v1.79.1 -> v1.79.2
go.opentelemetry.io/collector/component v1.53.0 -> v1.54.0
go.opentelemetry.io/collector/pdata v1.53.0 -> v1.54.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): - 9 additional dependencies were updated Details: | **Package** | **Change** | | :------------------------------------------ | :--------------------- | | `go.opentelemetry.io/collector/featuregate` | `v1.53.0` -> `v1.54.0` | | `go.opentelemetry.io/otel` | `v1.40.0` -> `v1.42.0` | | `go.opentelemetry.io/otel/metric` | `v1.40.0` -> `v1.42.0` | | `go.opentelemetry.io/otel/sdk` | `v1.40.0` -> `v1.42.0` | | `go.opentelemetry.io/otel/sdk/metric` | `v1.40.0` -> `v1.42.0` | | `go.opentelemetry.io/otel/trace` | `v1.40.0` -> `v1.42.0` | | `google.golang.org/grpc` | `v1.79.1` -> `v1.79.2` | | `go.opentelemetry.io/collector/component` | `v1.53.0` -> `v1.54.0` | | `go.opentelemetry.io/collector/pdata` | `v1.53.0` -> `v1.54.0` |
renovate-bot changed title from chore(deps): update module go.opentelemetry.io/collector/component/componenttest to v0.145.0 to chore(deps): update module go.opentelemetry.io/collector/component/componenttest to v0.146.1 2026-02-25 12:13:42 +01:00
renovate-bot force-pushed renovate/go.opentelemetry.io-collector-component-componenttest-0.x from 83afde8efd to 86b5486b09 2026-02-25 12:13:43 +01:00 Compare
renovate-bot force-pushed renovate/go.opentelemetry.io-collector-component-componenttest-0.x from 86b5486b09 to 515b4e6e68 2026-03-10 12:19:39 +01:00 Compare
renovate-bot changed title from chore(deps): update module go.opentelemetry.io/collector/component/componenttest to v0.146.1 to chore(deps): update module go.opentelemetry.io/collector/component/componenttest to v0.147.0 2026-03-10 12:19:39 +01:00
renovate-bot changed title from chore(deps): update module go.opentelemetry.io/collector/component/componenttest to v0.147.0 to chore(deps): update module go.opentelemetry.io/collector/component/componenttest to v0.148.0 2026-03-25 12:15:26 +01:00
renovate-bot force-pushed renovate/go.opentelemetry.io-collector-component-componenttest-0.x from 515b4e6e68 to d120eed142 2026-03-25 12:15:28 +01:00 Compare
renovate-bot changed title from chore(deps): update module go.opentelemetry.io/collector/component/componenttest to v0.148.0 to chore(deps): update module go.opentelemetry.io/collector/component/componenttest to v0.148.0 - autoclosed 2026-03-26 21:10:49 +01:00
renovate-bot closed this pull request 2026-03-26 21:10:49 +01:00
Some checks failed
renovate/stability-days Updates have met minimum release age requirement
Details
CI / test (push) Has been cancelled
Required
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
branch-buddy renovate-bot trivy-bot t.behrendt
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: t.behrendt/tracebasedlogsampler#32
Delete Branch "renovate/go.opentelemetry.io-collector-component-componenttest-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?