chore(deps): update all dependencies - #222
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/all
branch
8 times, most recently
from
August 17, 2026 22:16
c7cd0eb to
abfe49a
Compare
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
Bot
force-pushed
the
renovate/all
branch
9 times, most recently
from
August 21, 2026 21:52
0253db9 to
1b9ceea
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
11 times, most recently
from
August 30, 2026 01:01
c019706 to
2f4c683
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
August 30, 2026 14:05
73ba64f to
e74b1ea
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
August 30, 2026 15:32
e74b1ea to
98c7d3e
Compare
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 contains the following updates:
f7f8f72→1c2c046v2.32.0→v2.32.1v1.42.1→v1.43.0v0.156.0→v0.158.0v1.64.0→v1.65.0v1.64.0→v1.65.0v1.64.0→v1.65.0v1.64.0→v1.65.0v0.158.0→v0.159.0v0.158.0→v0.159.0v1.64.0→v1.65.0v0.158.0→v0.159.02.12.2→2.13.2v0.36.3→v0.36.4v0.37.0v0.36.3→v0.36.4v0.37.0v0.36.3→v0.36.4v0.37.00.156.0→0.158.00.120.2→0.122.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
onsi/ginkgo (github.com/onsi/ginkgo/v2)
v2.32.1Compare Source
2.32.1
Fixes
e647b3b]onsi/gomega (github.com/onsi/gomega)
v1.43.0Compare Source
1.43.0
Features
Add gomock adaptor extension for using Gomega matchers with gomock
open-telemetry/opentelemetry-operator (github.com/open-telemetry/opentelemetry-operator/apis)
v0.158.0Compare Source
0.158.0
💡 Enhancements 💡
operator, collector, target allocator: Enable operator, collector, target allocator network policies by default. (#5394)Feature gate
operator.networkpolicyandoperand.networkpolicyare promoted to beta, and enabled by default.These feature gates create network policies for the operator and operand components.
auto-instrumentation: Apache and nginx instrumentations forward Spec env vars to attach init containers so kubelet can expand $(VAR) references in exporter endpoints. (#5333)collector: promote the operator.collector.usedefaulttelemetryshape feature gate to stable, so the operator-injected Prometheus telemetry reader always uses collector defaults for without_type_suffix, without_units, and without_scope_info (#5075)The gate is now stable and can no longer be disabled. Users wanting the
pre-v0.154.0 metric name shape should explicitly set
without_type_suffix,without_units, andwithout_scope_infotofalsein their collector configuration. The gate will be removed in a future release.
collector: moves operator.golang.flags to stable setting GOMEMLIMIT and GOMAXPROCS automatically (#5455)🧰 Bug fixes 🧰
collector: Fix the automatic-upgrade routine binding two Prometheus readers to the same port when a collector already usesservice.telemetry.metrics.readers. (#5416)When an OpenTelemetryCollector already configured
service.telemetry.metrics.readers(added by earlier defaulting), the automatic version-upgrade routine still backfilled the
older, deprecated
addressfield for it. The 0.122.0 upgrade step then migratedaddressinto a new reader, leaving two readers bound to the same host:port. The collector then
failed to start with "address already in use". The 0.111.0 step now skips backfilling
addresswhenreadersis already configured, and the 0.122.0 step now skips adding areader for
addressif an equivalent one already exists.collector: Add PersistentVolume and PersistentVolumeClaim RBAC rules for k8s_cluster receiver automatic RBAC generation. (#5421)auto-instrumentation: DefaultOTEL_METRICS_EXPORTERtootlpfor Node.js auto-instrumentation so metrics are exported without extra configuration. (#3768)The Node.js SDK only initializes its metrics pipeline when a metric reader is configured, and the
webhook was not setting one. As a result, metrics silently stopped being exported for anyone relying
on the previous default behavior. The webhook now sets
OTEL_METRICS_EXPORTER=otlpby default,matching the existing behavior for Python auto-instrumentation, unless the user already set it.
Components
v0.157.0Compare Source
0.157.0
💡 Enhancements 💡
target allocator: Allow enabling mTLS between the target allocator and the collector using user-provided certificate Secrets, without requiring cert-manager. (#3982)When
spec.targetAllocator.mtls.useCertManageris set tofalse, the newmtls.tlsblockreferences user-provided certificates. The CA certificate may be sourced from either a Secret or a
ConfigMap (
certificateAuthorityCertificate.secret/.configMap). The target allocator's servercertificate and the collector's client certificate each reference their certificate and private key
independently, so the certificate and key may live in different Secrets. Data keys default to
tls.crt,tls.keyandca.crtand can be overridden per reference. The CA reference is requiredin this mode.
operator: Add support for Kubernetes 1.36 (#5354)🧰 Bug fixes 🧰
target allocator: Seed Prometheus's scrape labels (job,__scheme__,__metrics_path__,__scrape_interval__,__scrape_timeout__,__param_*) before relabel filtering, so keep/drop rules referencing them make the same decisions as Prometheus instead of silently dropping or over-allocating targets (#5246)The seeded labels also feed the target identity hash, matching Prometheus's post-relabel label partition more closely. With the
relabel-configfilter strategy enabled, existing targets are re-allocated once on upgrade because their hashes change. The served (pre-relabel) target labels are unchanged.Components
0.157.0
💡 Enhancements 💡
auto-instrumentation: Theautoinstrumentation-dotnetimage now bundles the correct native profiler for the platform it is pulled for, fixing arm64 support (the image was already published for arm64 but always contained amd64 binaries). (#3270)operator-opamp-bridge: Adds support for the OpAMP capability AcceptsRestartCommand to the operator's OpAMP bridge, allowing the operator to restart the collector when requested by an OpAMP server. (#5306)operator-opamp-bridge: Add anopentelemetry.io/opamp.bridge.modenon-identifying OpAMP AgentDescription attribute so servers can distinguish operator and standalone bridge clients. (#5423)operator-opamp-bridge: Report the operator-opamp-bridge's own build version asservice.versionin its OpAMP AgentDescription, instead of always sending an empty string. (#5360)collector: Add support for settingsessionAffinityandsessionAffinityConfigon the Services created for the Collector (#4455)target allocator: Support exporting the TargetAllocator's self-telemetry metrics via OTLP, in addition to the Prometheus /metrics endpoint. (#5047)Configure it under
spec.targetAllocator.telemetry.metrics.otlp(OpenTelemetryCollector CR) orspec.telemetry.metrics.otlp(TargetAllocator CR), with endpoint, protocol (grpc/http), temporality,headers, TLS and export interval/timeout. Metrics registered directly on the Prometheus registry
(Prometheus service discovery, Go runtime and process collectors) are bridged into the OTLP export
so the Prometheus endpoint and OTLP expose the same metric set.
🧰 Bug fixes 🧰
cluster-observability: Fix dependencies required by the bundled agent and cluster Collector configurations (#3821, #3818)Follow-ups to the initial ClusterObservability framework so generated
Collectors start cleanly across supported distributions:
defaulting to the operator's Collector version and supporting the
--clusterobservability-collector-imageoverride. Apply matching versionlabels and canonical component IDs.
K8S_NODE_NAME, which the bundledkubelet_statsreceiver usesfor its endpoint.
ClusterObservabilitydoes not remainPendingafter the workload is ready./hostfsforhost_metricsand exclude virtualand container-runtime filesystems that cannot be scraped reliably.
spc_tSCC sofile_logcan read root-owned container logs under
/var/log/pods.Instrumentationresources to the agent's OTLP/HTTP portbecause auto-instrumentation SDKs commonly use
http/protobuf.collector: Fix OpenShift collector dashboard (#5342)The collector v0.155.0 renamed the deprecated
otelcol_processor_accepted_*/dropped_*/refused_*metricsto
otelcol_processor_memory_limiter_*(open-telemetry/opentelemetry-collector#11203).The dashboard queries have been updated to use the new metric names.
collector: Register the snake-case spellings of several renamed receivers (kubelet_stats,k8s_objects,resource_detection,fluent_forward,tcp_log,udp_log,ssh_check,cloud_foundry,http_check,flink_metrics) alongside their original spellings when generating RBAC and service ports from a Collector CR, so either spelling produces the same result. (#5317)These components were renamed to snake_case in opentelemetry-collector-contrib
(#47957 kubeletstats, #47440 k8sobjects, #48525 resourcedetection, #47930
fluentforward, #47369 tcplog, #47370 udplog, #47515 sshcheck, #47932
cloudfoundry, #47505 httpcheck, #47929 flinkmetrics) while keeping the
original names accepted, but the operator only recognized one spelling per
component, so configs using the other spelling got no RBAC/ports or the
wrong service port name. This extends the k8s_attributes fix (#4983) to
the remaining renamed components, and makes
NewScraperParseracceptaliases so future renames of this kind are a one-line fix.
target allocator: Fix collector mtls with a TargetAllocator CR (#4297)This only affected collectors associated with a TargetAllocator CR whose name differs from the
collector's, e.g. via the
opentelemetry.io/target-allocatorlabel, causing them to address thewrong hostname (and TLS certificate) once mTLS was enabled.
target allocator: Refresh stale Prometheus meta labels (e.g.__meta_kubernetes_pod_name) on rediscovered targets whose address is unchanged (#4839)Target identity is deliberately hashed without meta labels, since Prometheus discards them after
relabeling. But because the allocator's target map is keyed by that same hash, a rediscovered
target whose address is unchanged (e.g. a hostNetwork DaemonSet pod after a restart) was never
recognized as changed, so its stale meta labels persisted until target-allocator itself restarted.
collector: Fix operator crash on startup when Gateway API CRDs are not installed by moving gatewayv1 scheme registration to be gated on autodetect result. (#5357)auto-instrumentation: Apply security context to Java extension init containers (#5335)Extension init containers injected alongside the Java agent were not receiving
a security context. This affected both the explicit
spec.initContainerSecurityContextfield on the Instrumentation CR and the fallback behaviour that inherits the
security context from the instrumented application container. Only the main
opentelemetry-auto-instrumentation-javainit container was having its securitycontext set; extension containers were always created with a nil security context.
This caused admission failures on clusters with policies that require all
containers to drop capabilities or disallow privilege escalation (e.g. OPA
Gatekeeper). The security context is now applied to all Java-related init
containers at construction time.
target allocator: Propagate the TargetAllocator CR's metadata annotations to all resources created for it, and restrictpodAnnotationsto the pod template (#4393)This aligns the TargetAllocator with the OpenTelemetryCollector behavior: CR metadata annotations now land
(respecting the annotations filter) on the Deployment, Service, ConfigMap, ServiceAccount, ServiceMonitor,
PodDisruptionBudget and NetworkPolicy, while
podAnnotationsis no longer copied to the NetworkPolicy andPodDisruptionBudget.
Components
open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/component)
v1.65.0💡 Enhancements 💡
pkg/exporterhelper: Add thepkg.exporterhelper.queueBatchEnabledfeature gate (#14038, #13582, #12022)When enabled, the batch settings returned by
NewDefaultQueueConfig()havebatch::enabledtrue. See migration RFC.🧰 Bug fixes 🧰
pkg/exporterhelper: Recordotelcol_exporter_queue_batch_send_sizeandotelcol_exporter_queue_batch_send_size_bytesafter batching, and addotelcol_exporter_enqueue_sizeandotelcol_exporter_enqueue_size_bytesfor enqueue-time sizes. (#14674)Previously the batch send size histograms were recorded at enqueue time (
Offer), so theymeasured incoming request sizes rather than the post-batching request handed to the
downstream sender. Those histograms are now recorded in the obs report sender.
The previous enqueue-time measurements are preserved under the new
otelcol_exporter_enqueue_sizeandotelcol_exporter_enqueue_size_bytesmetrics forqueue sizing. Users with the exporter batcher enabled will observe different values for
otelcol_exporter_queue_batch_send_size*.otelcol_exporter_queue_batch_send_sizeandotelcol_exporter_queue_batch_send_size_bytesare now only recorded when
sending_queue::batchis configured; they will not appear at allfor exporters that do not enable batching.
pkg/scraperhelper: Use{record}instead of{datapoint}as the unit of the log record and profile record scraper metrics (#15730)Affects
otelcol_scraper_scraped_log_records,otelcol_scraper_errored_log_records,otelcol_scraper_scraped_profile_recordsandotelcol_scraper_errored_profile_records.golangci/golangci-lint (golangci/golangci-lint)
v2.13.2Compare Source
Released on 2026-08-28
iface: from 1.5.0 to 1.5.1staticcheck: from 0.8.0 to 0.8.1unparam: from3f964bcto2fa3d84canonicalheader: from v1.1.2 to a temporary forkv2.13.1Compare Source
Released on 2026-08-20
ginkgolinter: from 0.23.1 to 0.24.0gofmt: fromd62b90etoe84e050staticcheck: from 0.8.0-rc.1 to 0.8.0wsl_v5: from 5.8.0 to 5.9.0v2.13.0Compare Source
Released on 2026-08-19
dupword: from 0.1.7 to 0.1.8 (new optionskip-raw-strings)errcheck: from 1.10.0 to 1.20.0exhaustruct_v5: from 4.0.0 to 5.0.2 (new configuration)exhaustruct: deprecated and replaced byexhaustruct_v5fatcontext: from 0.9.0 to 0.10.0 (new options:check-loops,check-function-literals)goconst: from 1.10.0 to 1.11.0 (new options:ignore-map-keys,exclude-types)gofumpt: from 0.9.2 to 0.11.0 (new options:extra.group-params,extra.clothe-returns,extra.balance-calls)gomoddirectives: from 0.8.0 to 0.9.0 (new option:replace-allow-all)gosec: from 2.26.1 to 2.27.1govet-modernize: from 0.44.0 to 0.49.0 (fmtappendfis removed. New analyzersatomictypes,embedlit,errorsastype,importcomment,reflecttypeassert,slicesclip, andslicesbackward.waitgroupis renamedwaitgroupgo)iface: from 1.4.3 to 1.5.0 (new analyzer:unusedmethod)noinlineerr: from 1.0.5 to 1.0.6nonamedreturns: from 1.0.6 to 1.0.8 (new option:allow-unused-named-returns)recvcheck: from 0.2.0 to 0.3.0 (new default exclusions)unparam: from5beb8c8to3f964bcclickhouse-go-linter: from 1.2.0 to 1.2.1errname: from 1.1.1 to 1.1.2exhaustruct: from 5.0.2 to 5.0.3funcorder: add missingFunctionfieldginkgolinter: from 0.23.0 to 0.23.1gocheckcompilerdirectives: from 1.3.0 to 1.4.0gocritic: from 0.14.3 to 0.14.4gomoddirectives: add missingIgnoreForbiddenfieldiface: from 1.4.2 to 1.4.3mirror: from 1.3.0 to 1.3.3nilnil: from 1.1.1 to 1.1.2protogetter: from 0.3.20 to 0.3.21kubernetes/api (k8s.io/api)
v0.36.4Compare Source
kubernetes/apimachinery (k8s.io/apimachinery)
v0.36.4Compare Source
kubernetes/client-go (k8s.io/client-go)
v0.36.4Compare Source
open-telemetry/opentelemetry-helm-charts (opentelemetry-operator)
v0.122.0Compare Source
OpenTelemetry Operator Helm chart for Kubernetes
What's Changed
Full Changelog: open-telemetry/opentelemetry-helm-charts@opentelemetry-target-allocator-0.158.0...opentelemetry-operator-0.122.0
opentelemetry-operator 0.122.0
What's Changed
This release updates the opentelemetry-operator to version 0.158.0.
OpenTelemetry Release Notes
Chart Information
v0.121.0Compare Source
OpenTelemetry Operator Helm chart for Kubernetes
What's Changed
Full Changelog: open-telemetry/opentelemetry-helm-charts@opentelemetry-operator-0.120.3...opentelemetry-operator-0.121.0
opentelemetry-operator 0.121.0
What's Changed
This release updates the opentelemetry-operator to version 0.157.0.
OpenTelemetry Release Notes
Chart Information
opentelemetry-operator 0.121.0
What's Changed
This release updates the opentelemetry-operator to version 0.157.0.
OpenTelemetry Release Notes
Chart Information
v0.120.3Compare Source
OpenTelemetry Operator Helm chart for Kubernetes
What's Changed
New Contributors
Full Changelog: open-telemetry/opentelemetry-helm-charts@opentelemetry-collector-0.169.0...opentelemetry-operator-0.120.3
Configuration
📅 Schedule: (in timezone Etc/UTC)
* 0-3 * * *)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.