Skip to content

chore(deps): update all dependencies#191

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/all
Open

chore(deps): update all dependencies#191
renovate[bot] wants to merge 1 commit intomainfrom
renovate/all

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 19, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Age Confidence
aquasecurity/trivy-action action minor 0.34.0 → v0.35.0 age confidence
cert-manager/cert-manager minor 1.19.3 → 1.20.0 age confidence
gcr.io/distroless/static final digest 01e550f → e3f9456
github.com/open-telemetry/opentelemetry-operator require minor v0.144.0 → v0.147.0 age confidence
go.opentelemetry.io/collector/component require minor v1.50.0 → v1.54.0 age confidence
go.opentelemetry.io/collector/config/configauth require minor v1.50.0 → v1.54.0 age confidence
go.opentelemetry.io/collector/config/configcompression require minor v1.50.0 → v1.54.0 age confidence
go.opentelemetry.io/collector/config/configopaque require minor v1.50.0 → v1.54.0 age confidence
go.opentelemetry.io/collector/config/configtelemetry require minor v0.142.0 → v0.148.0 age confidence
go.opentelemetry.io/collector/otelcol require minor v0.142.0 → v0.148.0 age confidence
go.opentelemetry.io/collector/pipeline require minor v1.50.0 → v1.54.0 age confidence
go.opentelemetry.io/collector/service require minor v0.142.0 → v0.148.0 age confidence
golang stage patch 1.26.0-alpine3.22 → 1.26.1-alpine3.22 age confidence
golangci/golangci-lint minor 2.10.1 → 2.11.3 age confidence
k8s.io/api require patch v0.35.1 → v0.35.3 age confidence
k8s.io/apimachinery require patch v0.35.1 → v0.35.3 age confidence
k8s.io/client-go require patch v0.35.1 → v0.35.3 age confidence
opentelemetry-operator (source) minor 0.105.1 → 0.108.0 age confidence
sigs.k8s.io/controller-runtime require minor v0.22.5 → v0.23.3 age confidence

Release Notes

aquasecurity/trivy-action (aquasecurity/trivy-action)

v0.35.0: Release: v0.35.0

Compare Source

This release is a duplicate of 0.35.0 which was not compromised.

As part of our response to the recent supply chain attack, we have migrated all tags to use the v prefix (e.g., v0.35.0 instead of 0.35.0). Going forward, all new releases will use the v prefix convention.

We have intentionally kept the 0.35.0 tag intact to avoid breaking existing workflows that depend on it.

If you are currently using 0.35.0, your workflows are safe — no action is required.

v0.35.0

Compare Source

What's Changed

Full Changelog: aquasecurity/trivy-action@0.34.2...0.35.0

cert-manager/cert-manager (cert-manager/cert-manager)

v1.20.0

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

v1.20.0 adds alpha support for the new ListenerSet resource, adds support for Azure Private DNS; parentRefs are no longer required when using ACME with Gateway API, and OtherNames was promoted to Beta.

Changes by Kind

Feature
  • Added a set of flags to permit setting NetworkPolicy across all deployed containers. Remove redundant global IP ranges from example policies. (#​8370, @​jcpunk)
  • Added selectable fields to custom resource definitions for .spec.issuerRef.{group, kind, name} (#​8256, @​tareksha)
  • Added support for specifying imagePullSecrets in the startupapicheck-job Helm template to enable pulling images from private registries. (#​8186, @​mathieu-clnk)
  • Added 'extraContainers' helm chart value, allowing the deployment of arbitrary sidecar containers within the cert-manager operator pod. This can be used to support, for e.g., AWS IAM Roles Anywhere for Route53 DNS01 verification. (#​8355, @​dancmeyers)
  • Added parentRef override annotations on the Certificate resource. (#​8518, @​hjoshi123)
  • Added support for azure private zones for dns01 issuer. (#​8494, @​hjoshi123)
  • Added support for configuring PEM decoding size limits, allowing operators to handle larger certificates and keys. (#​7642, @​robertlestak)
  • Added support for unhealthyPodEvictionPolicy in PodDisruptionBudget (#​7728, @​jcpunk)
  • For Venafi provider, read venafi.cert-manager.io/custom-fields annotation on Issuer/ClusterIssuer and use it as base with override/append capabilities on Certificate level. (#​8301, @​k0da)
  • Improve error message when CA issuers are misconfigured to use a clashing secret name (#​8374, @​majiayu000)
  • Introduce a new Ingress annotation acme.cert-manager.io/http01-ingress-ingressclassname to override http01.ingress.ingressClassName field in HTTP-01 challenge solvers. (#​8244, @​lunarwhite)
  • Update global.nodeSelector to helm chart to perform a merge and allow for a single nodeSelector to be set across all services. (#​8195, @​StingRayZA)
  • Vault issuers will now include the Vault server address as one of the default audiences on generated service account tokens. (#​8228, @​terinjokes)
  • Added experimental XListenerSets feature gate (#​8394, @​hjoshi123)
Documentation
Bug or Regression
  • Adds logs for cases when acme server returns us a fatal error in the order controller (#​8199, @​Peac36)
  • Fixed an issue where kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed (#​8160, @​inteon)
  • Changes to the Duration and RenewBefore annotations on ingress and gateway-api resources will now trigger certificate updates. (#​8232, @​eleanor-merry)
  • Fix an issue where ACME challenge TXT records are not cleaned up when there are many resource records in CloudDNS. (#​8456, @​tkna)
  • Fix unregulated retries with the DigitalOcean DNS-01 solver
    Add full detailed DNS-01 errors to the events attached to the Challenge, for easier debugging (#​8221, @​wallrj-cyberark)
  • Fixed an infinite re-issuance loop that could occur when an issuer returns a certificate with a public key that doesn't match the CSR. The issuing controller now validates the certificate before storing it and fails with backoff on mismatch. (#​8403, @​calm329)
  • Fixed an issue where HTTP-01 challenges failed when the Host header contains an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. (#​8424, @​SlashNephy)
  • Fixed the HTTP-01 Gateway solver creating invalid HTTPRoutes by not setting spec.hostnames when the challenge DNSName is an IP address. (#​8443, @​alviss7)
  • Revert API defaults for issuer reference kind and group introduced in 0.19.0 (#​8173, @​erikgb)
  • Security (MODERATE): Fix a potential panic in the cert-manager controller when a DNS response in an unexpected order was cached. If an attacker was able to modify DNS responses (or if they controlled the DNS server) it was possible to cause denial of service for the cert-manager controller. (#​8469, @​SgtCoDFish)
  • Update Go to v1.25.5 to fix CVE-2025-61727 and CVE-2025-61729 (#​8290, @​octo-sts[bot])
  • When Prometheus monitoring is enabled, the metrics label is now set to the intended value of cert-manager. Previously, it was set depending on various factors (namespace cert-manager is installed in and/or Helm release name). (#​8162, @​LiquidPL)
Other (Cleanup or Flake)

v1.19.4

Compare Source

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

v1.19.4 is a simple patch release to fix some reported vulnerabilities - notably CVE-2026-24051 and CVE-2025-68121. All users should upgrade.

Changes by Kind

Bug or Regression
open-telemetry/opentelemetry-operator (github.com/open-telemetry/opentelemetry-operator)

v0.147.0

Compare Source

0.147.0

🛑 Breaking changes 🛑
  • apis/v1beta1: Move webhooks from the apis/v1beta1 package to the internal package internal/webhook (#​4846)
  • v1alpha1: Move webhooks from the apis/v1alpha1 package to the internal package internal/webhook (#​4837)
🧰 Bug fixes 🧰
  • target allocator: Fix Service Monitor/Pod Monitor in TargetAllocator doesnt pick up updates to secrets (#​4091)
    Fixes issue where service/pod Monitors don't pick up updates to secrets.
Components

v0.146.0

Compare Source

0.146.0
💡 Enhancements 💡

  • target allocator: Expose missing Prometheus CR fields in the Operator API (#​1934)
    Added podMonitorNamespaceSelector, serviceMonitorNamespaceSelector, scrapeConfigNamespaceSelector,
    probeNamespaceSelector, evaluationInterval, and scrapeProtocols to the prometheusCR
    configuration within the TargetAllocator and OpenTelemetryCollector
    APIs to achieve feature parity with the underlying Target Allocator.

  • collector: Add the hostUsers field to OpenTelemetryCommonFields to enable toggling support for isolating pod processes under a separate user namespace (#​4366)

  • auto-instrumentation: Add support for initContainers to instrumentation injector (#​3308)
    Add support for instrumenting init containers.
    Init container support is available for Java, Python, Node.js, .NET and SDK-only, and works using the same annotation as for regular containers.

  • operator, collector: Allow operator to get TLS settings from OpenShift APIServer CR and configure operands TLS settings. (#​4669)
    Added operator flag --tls-cluster-profile which obtains the TLS min version and cipher suites from the OpenShift APIServer cluster custom resource (CR).
    It overrides the --tls-min-version and --tls-cipher-suites flags if set.
    The flags is disabled by default on Kubernetes and enabled on OpenShift.

    Added operator flag --tls-configure-operands which configures operands TLS settings (min version, cipher suites)
    based on the supplied operator TLS flags (--tls-cipher-suites and --tls-min-version) or from the OpenShift APIServer CR
    if --tls-cluster-profile is enabled.
    The flag is disabled by default on Kubernetes and enabled on OpenShift.

    The --tls-min-version defaults to TLSv1.2 which matches the collector's default.
    The --tls-cipher-suites is empty by default which matches the collector's default.
    Therefore enabling --tls-configure-operands with the default TLS flags should not change the collector's behavior.

  • operator: Add webhook server readiness check to the operator's /readyz endpoint so the pod is not marked ready before the webhook server is listening. (#​3772)
    Previously the readiness probe used only healthz.Ping, causing a race where CRs
    created right after deployment could hit "connection refused" from the webhook.
    Now the readyz endpoint includes a check using controller-runtime's
    StartedChecker which verifies the webhook TLS listener is actually accepting connections.

🧰 Bug fixes 🧰
  • collector: Remove legacy finalizer from OpenTelemetryCollector CR when RBAC not available. (#​4769)
    Finalizer usage was restricted to cluster scoped resources only. Legacy finalizer added by OpenTelemetry Operator
    <= v0.141.0 still blocks namespace deletion if the operator is removed first. The change removes finalizer with
    cluster-level RBAC availability.
Components

v0.145.0

Compare Source

0.145.0
🛑 Breaking changes 🛑
  • collector: Remove operator.collector.default.config feature gate (#​4473)
🚀 New components 🚀
  • clusterObservability: Inital implementation of ClusterObservability CRD (#​3820)
    This change provides an initial implementation of the Cluster Observability CRD and operator control loop.
    Reconcilation is disabled by default.
    Currently, the CRD is not included in the operator bundle and must be installed manually.
    To enable reconciliation, enable the --feature-gates=+operator.clusterobservability feature gate.
💡 Enhancements 💡
  • target allocator: Add readiness and liveness probe configurations for target allocator CRD (#​4639)
  • target allocator: Make the least-weighted target allocation strategy take job name into account. (#​3128)
    Uses job name instead of "first match" to when number of targets is equal. The effect is to spread out targets with the same job name across collectors.
🧰 Bug fixes 🧰

  • target allocator: Fix TLS certificate hot-reload for mTLS connections (#​4368)
    The Target Allocator now automatically reloads TLS certificates when they are renewed
    by cert-manager. Previously, certificate renewals required a pod restart because
    certificates were only loaded once at startup. The fix uses fsnotify to watch the
    certificate directory and dynamically reloads certificates via the GetCertificate
    callback, enabling seamless certificate rotation without downtime.

  • collector: Configure collector to reload client certificate periodically (#​4657)
    When the collector connects to the target allocator over mTLS, certificates were not automatically reloaded after expiration. This adds reload_interval to the TLS configuration, enabling the Prometheus receiver to periodically reload certificates from disk.

    The default interval of 5 minutes provides a good balance between picking up renewed certificates promptly and avoiding unnecessary overhead.

  • operator: Set Kubernetes API server egress network policy port dynamically. (#​4411)
    The operator network policy egress rule for the Kubernetes API server was hardcoded to port 6443.
    This PR uses uses endpointslices.discovery.k8s.io -n default kubernetes to get the port and IP addresses of the Kubernetes API server
    for the operator egress network policy.

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

v1.54.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: 
    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.

v1.53.0

💡 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)

v1.52.0

v1.51.0

💡 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)

golangci/golangci-lint (golangci/golangci-lint)

v2.11.3

Compare Source

Released on 2026-03-10

  1. Linters bug fixes

v2.11.2

Compare Source

Released on 2026-03-07

  1. Fixes
    • fmt: fix error when using the fmt command with explicit paths.

v2.11.1

Compare Source

Released on 2026-03-06

Due to an error related to AUR, some artifacts of the v2.11.0 release have not been published.

This release contains the same things as v2.11.0.

v2.11.0

Compare Source

Released on 2026-03-06

  1. Linters new features or changes
    • errcheck: from 1.9.0 to 1.10.0 (exclude crypto/rand.Read by default)
    • gosec: from 2.23.0 to 2.24.6 (new rules: G113, G118, G119, G120, G121, G122, G123, G408, G707)
    • noctx: from 0.4.0 to 0.5.0 (new detection: httptest.NewRequestWithContext)
    • prealloc: from 1.0.2 to 1.1.0
    • revive: from 1.14.0 to 1.15.0 (⚠️ Breaking change: package-related checks moved from var-naming to a new rule package-naming)
  2. Linters bug fixes
    • gocognit: from 1.2.0 to 1.2.1
    • gosec: from 2.24.6 to 2.24.7
    • unqueryvet: from 1.5.3 to 1.5.4
kubernetes/api (k8s.io/api)

v0.35.3

Compare Source

v0.35.2

Compare Source

kubernetes/apimachinery (k8s.io/apimachinery)

v0.35.3

Compare Source

v0.35.2

Compare Source

kubernetes/client-go (k8s.io/client-go)

v0.35.3

Compare Source

v0.35.2

Compare Source

open-telemetry/opentelemetry-helm-charts (opentelemetry-operator)

v0.108.0

Compare Source

OpenTelemetry Operator Helm chart for Kubernetes

What's Changed

Full Changelog: open-telemetry/opentelemetry-helm-charts@opentelemetry-demo-0.40.6...opentelemetry-operator-0.108.0

opentelemetry-operator 0.108.0

What's Changed

This release updates the opentelemetry-operator to version 0.147.0.

OpenTelemetry Release Notes

Chart Information

  • Chart Version: 0.108.0
  • App Version: 0.147.0
  • Chart Path: charts/opentelemetry-operator/

v0.107.2

Compare Source

OpenTelemetry Operator Helm chart for Kubernetes

What's Changed

Full Changelog: open-telemetry/opentelemetry-helm-charts@opentelemetry-ebpf-instrumentation-0.6.0...opentelemetry-operator-0.107.2

v0.107.1

Compare Source

OpenTelemetry Operator Helm chart for Kubernetes

What's Changed

New Contributors

Full Changelog: open-telemetry/opentelemetry-helm-charts@opentelemetry-target-allocator-0.127.0...opentelemetry-operator-0.107.1

v0.107.0

Compare Source

OpenTelemetry Operator Helm chart for Kubernetes

What's Changed

Full Changelog: open-telemetry/opentelemetry-helm-charts@opentelemetry-collector-0.147.0...opentelemetry-operator-0.107.0

opentelemetry-operator 0.107.0
What's Changed

This release updates the opentelemetry-operator to version 0.146.0.

OpenTelemetry Release Notes
Chart Information
  • Chart Version: 0.107.0
  • App Version: 0.146.0
  • Chart Path: charts/opentelemetry-operator/

v0.106.0

Compare Source

OpenTelemetry Operator Helm chart for Kubernetes

What's Changed

New Contributors

Full Changelog: open-telemetry/opentelemetry-helm-charts@opentelemetry-collector-0.146.0...opentelemetry-operator-0.106.0

opentelemetry-operator 0.106.0

What's Changed

This release updates the opentelemetry-operator to version 0.145.0.

OpenTelemetry Release Notes

Chart Information

  • Chart Version: 0.106.0
  • App Version: 0.145.0
  • Chart Path: charts/opentelemetry-operator/
kubernetes-sigs/controller-runtime (sigs.k8s.io/controller-runtime)

v0.23.3

Compare Source

What's Changed

Full Changelog: kubernetes-sigs/controller-runtime@v0.23.2...v0.23.3

v0.23.2

Compare Source

What's Changed

Full Changelog: kubernetes-sigs/controller-runtime@v0.23.1...v0.23.2

v0.23.1

Compare Source

What's Changed

Full Changelog: kubernetes-sigs/controller-runtime@v0.23.0...v0.23.1

v0.23.0

Compare Source

🔆 Highlights

⚠️ Breaking changes

  • Dependencies: Update to k8s.io/* v1.35 by @​alvaroaleman @​dongjiang1989 @​kannon92 (#​3316, #​3349, #​3386, #​3391, #​3401)
  • Client: Add subresource Apply support by @​alvaroaleman in #​3321
  • Events: Migration to the new events API by @​clebs in #​3262
    • Using the new GetEventRecorderFor requires updating your rbac for events to use the events.k8s.io apiGroup rather than the `` (core) apiGroup
  • Fakeclient: Set ResourceVersion for SSA Create by @​alvaroaleman in #​3311
  • Webhooks: Generic Validator and Defaulter by @​alvaroaleman in #​3360
    • Existing code of the form builder.WebhookManagedBy(mgr).For(&corev1.Deployment{}) has to be changed to builder.WebhookManagedBy(mgr, &appsv1.Deployment{})
    • Existing webhook implementations have to be changed to take the concrete object rather than runtime.Object, for example from ValidateCreate(ctx context.Context, obj runtime.Object) (admission.Warnings, error) to ValidateCreate(ctx context.Context, obj *appsv1.Deployment) (admission.Warnings, error)

✨ Features

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) in timezone Etc/UTC, Automerge - At any time (no schedule defined).

🚦 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.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Feb 19, 2026
@renovate
Copy link
Contributor Author

renovate bot commented Feb 19, 2026 •
edited
Loading

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

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

Details:

Package Change
go 1.25.0 -> 1.25.3
github.com/ebitengine/purego v0.9.1 -> v0.10.0
github.com/fatih/color v1.17.0 -> v1.18.0
github.com/go-openapi/jsonpointer v0.22.1 -> v0.22.4
github.com/go-openapi/jsonreference v0.21.3 -> v0.21.4
github.com/goccy/go-yaml v1.18.0 -> v1.19.2
github.com/grpc-ecosystem/grpc-gateway/v2 v2.27.4 -> v2.28.0
github.com/knadh/koanf/v2 v2.3.2 -> v2.3.3
github.com/prometheus/procfs v0.19.2 -> v0.20.1
github.com/shirou/gopsutil/v4 v4.26.1 -> v4.26.2
go.opentelemetry.io/collector/component/componentstatus v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/component/componenttest v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/confmap v1.50.0 -> v1.54.0
go.opentelemetry.io/collector/confmap/xconfmap v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/connector v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/connector/connectortest v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/connector/xconnector v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/consumer v1.50.0 -> v1.54.0
go.opentelemetry.io/collector/consumer/consumererror v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/consumer/consumertest v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/consumer/xconsumer v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/exporter v1.50.0 -> v1.54.0
go.opentelemetry.io/collector/exporter/exportertest v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/exporter/xexporter v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/extension v1.50.0 -> v1.54.0
go.opentelemetry.io/collector/extension/extensionauth v1.51.0 -> v1.54.0
go.opentelemetry.io/collector/extension/extensioncapabilities v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/extension/extensiontest v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/featuregate v1.50.0 -> v1.54.0
go.opentelemetry.io/collector/internal/componentalias v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/internal/fanoutconsumer v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/internal/telemetry v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/pdata v1.50.0 -> v1.54.0
go.opentelemetry.io/collector/pdata/pprofile v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/pdata/testdata v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/pdata/xpdata v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/pipeline/xpipeline v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/processor v1.50.0 -> v1.54.0
go.opentelemetry.io/collector/processor/processortest v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/processor/xprocessor v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/receiver v1.50.0 -> v1.54.0
go.opentelemetry.io/collector/receiver/receivertest v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/receiver/xreceiver v0.144.0 -> v0.148.0
go.opentelemetry.io/collector/service/hostcapabilities v0.142.0 -> v0.148.0
go.opentelemetry.io/contrib/bridges/otelzap v0.13.0 -> v0.17.0
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.64.0 -> v0.67.0
go.opentelemetry.io/contrib/otelconf v0.19.0 -> v0.22.0
go.opentelemetry.io/contrib/propagators/b3 v1.38.0 -> v1.42.0
go.opentelemetry.io/otel v1.40.0 -> v1.42.0
go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc v0.15.0 -> v0.18.0
go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp v0.15.0 -> v0.18.0
go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc v1.39.0 -> v1.42.0
go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp v1.39.0 -> v1.42.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.39.0 -> v1.42.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.39.0 -> v1.42.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.39.0 -> v1.42.0
go.opentelemetry.io/otel/exporters/prometheus v0.61.0 -> v0.64.0
go.opentelemetry.io/otel/exporters/stdout/stdoutlog v0.15.0 -> v0.18.0
go.opentelemetry.io/otel/exporters/stdout/stdoutmetric v1.39.0 -> v1.42.0
go.opentelemetry.io/otel/exporters/stdout/stdouttrace v1.39.0 -> v1.42.0
go.opentelemetry.io/otel/log v0.16.0 -> v0.18.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/log v0.15.0 -> v0.18.0
go.opentelemetry.io/otel/sdk/metric v1.40.0 -> v1.42.0
go.opentelemetry.io/otel/trace v1.40.0 -> v1.42.0
go.opentelemetry.io/proto/otlp v1.9.0 -> v1.10.0
golang.org/x/exp v0.0.0-20251002181428-27f1f14c8bb9 -> v0.0.0-20260218203240-3dfff04db8fa
golang.org/x/mod v0.32.0 -> v0.33.0
golang.org/x/oauth2 v0.34.0 -> v0.35.0
golang.org/x/sys v0.41.0 -> v0.42.0
golang.org/x/tools v0.41.0 -> v0.42.0
gomodules.xyz/jsonpatch/v2 v2.4.0 -> v2.5.0
google.golang.org/genproto/googleapis/api v0.0.0-20251222181119-0a764e51fe1b -> v0.0.0-20260226221140-a57be14db171
google.golang.org/genproto/googleapis/rpc v0.0.0-20251222181119-0a764e51fe1b -> v0.0.0-20260226221140-a57be14db171
google.golang.org/grpc v1.79.1 -> v1.79.2
k8s.io/utils v0.0.0-20251002143259-bc988d571ff4 -> v0.0.0-20260108192941-914a6e750570

@renovate renovate bot force-pushed the renovate/all branch 9 times, most recently from bdca8fa to 01acc69 Compare February 27, 2026 15:00
@renovate renovate bot force-pushed the renovate/all branch 15 times, most recently from da25553 to 835f06f Compare March 8, 2026 00:54
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from 4cde8df to 2c98be6 Compare March 10, 2026 18:44
@renovate renovate bot force-pushed the renovate/all branch 14 times, most recently from 994408c to fb7374b Compare March 20, 2026 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants