fix(deps): update module go.opentelemetry.io/collector/consumer to v1.62.0 - autoclosed #29

Closed

renovate wants to merge 1 commit from renovate/go.opentelemetry.io-collector-consumer-1.x into main

renovate commented

2026-07-09 05:11:40 -04:00

Member

This PR contains the following updates:

Package	Change	Age	Confidence
go.opentelemetry.io/collector/consumer	`v1.61.0` → `v1.62.0`

Release Notes

open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/consumer)

`v1.62.0`

💡 Enhancements 💡

cmd/mdatagen: Add support for defining stability levels for resource attributes (#15312)
cmd/mdatagen: Add semantic convention reference to resource attributes (#15313)
processor/memory_limiter: Adding health events for the memorylimiter (#14700)
Publish health event from memorylimiter using componentstatus.ReportStatus

🧰 Bug fixes 🧰

cmd/mdatagen: Removes the extra line in the documentation.md between extended description and table (#15458)
exporter/otlp_http: Treat errors parsing successful (2xx) HTTP response bodies as permanent errors to prevent retrying already-accepted data. (#15386)
When a server returns a 2xx status but the response body exceeds the 64kB read limit,
the body is truncated and proto unmarshaling fails. Previously this was treated as a
retryable error, causing duplicate data to be exported. Now it is marked as a permanent
error so the retry logic will not re-send data that was already accepted by the server.
pkg/config/configretry: Always validate BackOffConfig fields regardless of the Enabled flag. (#15437)
pkg/service: Ensure receivers always start after all other components (#15495)
There was previously a race condition where multiple receivers using a shared internal implementation,
such as the OTLP receiver, could start sending telemetry into a pipeline before all its components had fully started.
processor/memory_limiter: Fix degenerate collector performance when exporter has problems causing permanent CPU-burning GC loop (#4981)
Forced GC runs now use exponential backoff when deemed ineffective
(still above soft limit and less than 5% reclaimed) to avoid preventing
recovery by overloading CPU with excessive GC runs. The cap on the
backoff interval is exposed via max_gc_interval_when_soft_limited and
max_gc_interval_when_hard_limited (both default 30s); set either to
0 to disable backoff on that path.
provider/env: Fix empty env var default resolving to nil instead of empty string (#14587)
When using ${env:VAR:-} with an unset variable, the empty default now correctly
resolves to an empty string instead of nil.

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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 Mend Renovate.

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/consumer](https://github.com/open-telemetry/opentelemetry-collector) | `v1.61.0` → `v1.62.0` | ![age](https://developer.mend.io/api/mc/badges/age/go/go.opentelemetry.io%2fcollector%2fconsumer/v1.62.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/go.opentelemetry.io%2fcollector%2fconsumer/v1.61.0/v1.62.0?slim=true) | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/consumer)</summary> ### [`v1.62.0`](https://github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1620v01560) ##### 💡 Enhancements 💡 - `cmd/mdatagen`: Add support for defining stability levels for resource attributes ([#15312](https://github.com/open-telemetry/opentelemetry-collector/issues/15312)) - `cmd/mdatagen`: Add semantic convention reference to resource attributes ([#15313](https://github.com/open-telemetry/opentelemetry-collector/issues/15313)) - `processor/memory_limiter`: Adding health events for the memorylimiter ([#14700](https://github.com/open-telemetry/opentelemetry-collector/issues/14700)) Publish health event from memorylimiter using componentstatus.ReportStatus ##### 🧰 Bug fixes 🧰 - `cmd/mdatagen`: Removes the extra line in the documentation.md between extended description and table ([#15458](https://github.com/open-telemetry/opentelemetry-collector/issues/15458)) - `exporter/otlp_http`: Treat errors parsing successful (2xx) HTTP response bodies as permanent errors to prevent retrying already-accepted data. ([#15386](https://github.com/open-telemetry/opentelemetry-collector/issues/15386)) When a server returns a 2xx status but the response body exceeds the 64kB read limit, the body is truncated and proto unmarshaling fails. Previously this was treated as a retryable error, causing duplicate data to be exported. Now it is marked as a permanent error so the retry logic will not re-send data that was already accepted by the server. - `pkg/config/configretry`: Always validate BackOffConfig fields regardless of the Enabled flag. ([#15437](https://github.com/open-telemetry/opentelemetry-collector/issues/15437)) - `pkg/service`: Ensure receivers always start after all other components ([#15495](https://github.com/open-telemetry/opentelemetry-collector/issues/15495)) There was previously a race condition where multiple receivers using a shared internal implementation, such as the OTLP receiver, could start sending telemetry into a pipeline before all its components had fully started. - `processor/memory_limiter`: Fix degenerate collector performance when exporter has problems causing permanent CPU-burning GC loop ([#4981](https://github.com/open-telemetry/opentelemetry-collector/issues/4981)) Forced GC runs now use exponential backoff when deemed ineffective (still above soft limit and less than 5% reclaimed) to avoid preventing recovery by overloading CPU with excessive GC runs. The cap on the backoff interval is exposed via `max_gc_interval_when_soft_limited` and `max_gc_interval_when_hard_limited` (both default `30s`); set either to `0` to disable backoff on that path. - `provider/env`: Fix empty env var default resolving to nil instead of empty string ([#14587](https://github.com/open-telemetry/opentelemetry-collector/issues/14587)) When using ${env:VAR:-} with an unset variable, the empty default now correctly resolves to an empty string instead of nil.  </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Enabled. ♻ **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 [Mend Renovate](https://github.com/renovatebot/renovate).

renovate added the

dep

labels

2026-07-09 05:11:40 -04:00

renovate added 1 commit

2026-07-09 05:11:40 -04:00

fix(deps): update module go.opentelemetry.io/collector/consumer to v1.62.0

check / check (pull_request) Failing after 2m34s

Details

889ee56c6f

renovate force-pushed renovate/go.opentelemetry.io-collector-consumer-1.x from 889ee56c6f

check / check (pull_request) Failing after 2m34s

Details

to b4f62a7749

check / check (pull_request) Successful in 3m10s

Details

2026-07-09 11:25:46 -04:00

Compare

renovate changed title from ~~fix(deps): update module go.opentelemetry.io/collector/consumer to v1.62.0~~ to fix(deps): update module go.opentelemetry.io/collector/consumer to v1.62.0 - autoclosed

2026-07-09 12:05:13 -04:00

renovate closed this pull request

2026-07-09 12:05:13 -04:00