build(deps): Upgrade otelcollector to v0.142.0#1388
Merged
Conversation
Contributor
Author
View build errors |
Contributor
|
@gracewehner - I have made all the changes for upgrades along with the web handler. Please review the PR when you get a chance. Thanks! |
gracewehner
previously approved these changes
Jan 15, 2026
gracewehner
left a comment
Contributor
There was a problem hiding this comment.
Thanks Rashmi, looks good to me
gracewehner
previously approved these changes
Jan 15, 2026
gracewehner
approved these changes
Jan 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR upgrades the otelcollector to the latest version available for the opentelemetry-collector and opentelemetry-operator.
It was automatically generated by the GitHub Actions workflow.
The summary of the OSS changelog is below:
Prometheusreceiver Changes
v0.136.0 to v0.142.0
Generated on: 2026-01-11 07:06:49
v0.142.0
receiver/prometheus: Promote the receiver.prometheusreceiver.RemoveStartTimeAdjustment feature gate to stable and remove in-receiver metric start time adjustment in favor of the metricstarttime processor, including disabling the created-metric feature gate. (#44180) Previously, users could disable the RemoveStartTimeAdjustment feature gate to temporarily keep the legacy start time adjustment behavior in the Prometheus receiver. With this promotion to stable and bounded registration, that gate can no longer be disabled; the receiver will no longer set StartTime on metrics based on process_start_time_seconds, and users should migrate to the metricstarttime processor for equivalent functionality. This change also disables the receiver.prometheusreceiver.UseCreatedMetric feature gate, which previously used the<metric>_createdseries to derive start timestamps for counters, summaries, and histograms when scraping non OpenMetrics protocols. However, this does not mean that the_createdseries is always ignored: when using the OpenMetrics 1.0 protocol, Prometheus itself continues to interpret the_createdseries as the start timestamp, so only the receiver-side handling for other scrape protocols has been removed.receiver/prometheus: Native histogram scraping and ingestion is now controlled by the scrape configuration optionscrape_native_histograms. (#44861) The feature gatereceiver.prometheusreceiver.EnableNativeHistogramsis now stable and enabled by default. Native histograms scraped from Prometheus will automatically be converted to OpenTelemetry exponential histograms. To enable scraping of native histograms, you must configurescrape_native_histograms: truein your Prometheus scrape configuration (either globally or per-job). Additionally, the protobuf scrape protocol must be enabled by settingscrape_protocolsto includePrometheusProto.receiver/prometheusremotewrite: Updated to Remote Write 2.0 spec rc.4, requiring Prometheus 3.8.0 or later (#44861) The upstream Prometheus library updated the Remote Write 2.0 protocol from rc.3 to rc.4 in prometheus/prometheus#17411. This renamedCreatedTimestamptoStartTimestampand moved it from theTimeSeriesmessage to individualSampleandHistogrammessages. This is a wire-protocol incompatibility, so Prometheus versions 3.7.x and earlier will no longer work correctly with this receiver. Please upgrade to Prometheus 3.8.0 or later.receiver/prometheus: Deprecateuse_start_time_metricandstart_time_metric_regexconfig in favor of the processormetricstarttime(#44180)receiver/prometheusremotewrite: Map.PutStr causes excessive memory allocations due to repeated slice expansions (#44612)receiver/prometheus: Fix HTTP response body leak in target allocator when fetching scrape configs fails (#44921) The getScrapeConfigsResponse function did not close resp.Body on error paths. If io.ReadAll or yaml.Unmarshal failed, the response body would leak, potentially causing HTTP connection exhaustion.receiver/prometheus: Fixes yaml marshaling of prometheus/common/config.Secret types (#44445)v0.141.0
receiver/prometheus: Add feature gate for extra scrape metrics in Prometheus receiver (#44181) deprecation of extra scrape metrics in Prometheus receiver will be removed eventually.receiver/prometheus: Support JWT Profile for Authorization Grant (RFC 7523 3.1) (#44381)v0.140.0
receiver/prometheus: The prometheus receiver no longer adjusts the start time of metrics by default. (#43656) Disable the receiver.prometheusreceiver.RemoveStartTimeAdjustment | feature gate to temporarily re-enable this functionality. Users that need | this functionality should migrate to the metricstarttime processor, | and use the true_reset strategy for equivalent behavior.receiver/prometheusremotewrite: Skip emitting empty metrics. (#44149)receiver/prometheusremotewrite: prometheusremotewrite receiver now accepts metric type unspcified histograms. (#41840)v0.139.0
receiver/prometheus: Fix missing staleness tracking leading to missing no recorded value data points. (#43893)receiver/prometheusremotewrite: Fixed a concurrency bug in the Prometheus remote write receiver where concurrent requests with identical job/instance labels would return empty responses after the first successful request. (#42159)v0.138.0
receiver/prometheus: added NHCB(native histogram wit custom buckets) to explicit histogram conversion (#41131)Summary
Target-allocator Changes
v0.136.0 to v0.142.0
Generated on: 2026-01-11 07:07:05
0.142.0
target allocator: Add support for prometheus scrape classes (#3600) Added support for configuringscrapeClasseswhen using the PrometheusCR-feature of the target allocator. The format of thescrapeClassesarray is exactly as same asspec.scrapeClassesof thePrometheusCRD.target allocator: Fix CA certificate race condition with client cert renewals by extending its duration and and renewal attempt. (#4441) The CA certificate now has a 2-year duration (instead of the default 90 days) to prevent race conditions where client and server certificates could be signed by different CA versions during simultaneous renewal. This ensures the CA remains stable while dependent certificates renew regularly.0.141.0
target allocator: make evaluation_interval configurable for Prometheus CR watcher (#4520)0.140.0
github action: Remove unused VERSION and VERSION_DATE environment variables from publish workflows (#4470) Removed the unused "Read version" step that set VERSION and VERSION_DATE environment variables in both publish-target-allocator.yaml and publish-operator-opamp-bridge.yaml workflows. These variables were never referenced anywhere in the workflows.0.138.0
target allocator: Remove the operator.collector.targetallocatorcr feature flag (#2422) This behavior has been enabled by default since version 0.127.0.target allocator: Add missing TA ownership watches to cert-manager Certificate and Issuer (#4368)0.137.0
target allocator: Promote the operator.collector.targetallocatorcr feature flag to Stable (#2422) The flag can no longer be disabled. It will be completely removed in 0.138.0.target allocator, opamp: Fix version not being updated after version upgrade. (#4378)target-allocator: Fixed potential duplicate scrape targets caused by Prometheus relabeling. (#3617)Summary