Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update all non-major dependencies #3

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 15, 2024

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
cert-manager/cert-manager minor v1.14.5 -> v1.16.3 age adoption passing confidence
github.com/aws/aws-sdk-go-v2 require minor v1.26.1 -> v1.33.0 age adoption passing confidence
github.com/aws/aws-sdk-go-v2/config require minor v1.27.13 -> v1.29.0 age adoption passing confidence
github.com/aws/aws-sdk-go-v2/credentials require patch v1.17.13 -> v1.17.53 age adoption passing confidence
github.com/aws/aws-sdk-go-v2/service/acmpca require minor v1.29.5 -> v1.37.12 age adoption passing confidence
github.com/aws/aws-sdk-go-v2/service/iam require minor v1.32.1 -> v1.38.6 age adoption passing confidence
github.com/aws/aws-sdk-go-v2/service/ram require minor v1.25.5 -> v1.29.12 age adoption passing confidence
github.com/aws/aws-sdk-go-v2/service/sts require minor v1.28.7 -> v1.33.8 age adoption passing confidence
github.com/cert-manager/cert-manager require minor v1.14.5 -> v1.16.3 age adoption passing confidence
github.com/go-logr/logr require patch v1.4.1 -> v1.4.2 age adoption passing confidence
github.com/stretchr/testify require minor v1.9.0 -> v1.10.0 age adoption passing confidence
go (source) toolchain minor 1.22.3 -> 1.23.5 age adoption passing confidence
golang stage minor 1.22.3 -> 1.23.5 age adoption passing confidence
golang stage minor 1.22 -> 1.23 age adoption passing confidence
k8s.io/api require minor v0.30.1 -> v0.32.1 age adoption passing confidence
k8s.io/apimachinery require minor v0.30.1 -> v0.32.1 age adoption passing confidence
k8s.io/client-go require minor v0.30.1 -> v0.32.1 age adoption passing confidence
k8s.io/utils require digest fe8a2dd -> 24370be age adoption passing confidence
kubernetes-sigs/controller-tools minor 0.15.0 -> 0.17.1 age adoption passing confidence
sigs.k8s.io/controller-runtime require minor v0.18.2 -> v0.20.0 age adoption passing confidence

Release Notes

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

v1.16.3

Compare Source

v1.16.2

Compare Source

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

This patch release of cert-manager 1.16 makes several changes to how PEM input is validated, adding maximum sizes appropriate to the type of PEM data which is being parsed.

This is to prevent an unacceptable slow-down in parsing specially crafted PEM data. The issue was found by Google's OSS-Fuzz project.

The issue is low severity; to exploit the PEM issue would require privileged access which would likely allow Denial-of-Service through other methods.

Note also that since most PEM data parsed by cert-manager comes from ConfigMap or Secret resources which have a max size limit of approximately 1MB, it's difficult to force cert-manager to parse large amounts of PEM data.

Further information is available in GHSA-r4pg-vg54-wxx4

In addition, the version of Go used to build cert-manager 1.16 was updated along with the base images.

Changes by Kind

Bug or Regression
  • Set a maximum size for PEM inputs which cert-manager will accept to remove possibility of taking a long time to process an input (#​7401, @​SgtCoDFish)
Other (Cleanup or Flake)

v1.16.1

Compare Source

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

The cert-manager 1.16 release includes: new Helm chart features, more Prometheus metrics, memory optimizations, and various improvements and bug fixes for the ACME issuer and Venafi Issuer.

📖 Read the complete 1.16 release notes before upgrading.

📜Changes since v1.16.0

Bug or Regression
  • BUGFIX: Helm schema validation: the new schema validation was too strict for the "global" section. Since the global section is shared across all charts and sub-charts, we must also allow unknown fields. (#​7348, @inteon)
  • BUGFIX: Helm will now accept percentages for the podDisruptionBudget.minAvailable and podDisruptionBudget.maxAvailable values. (#​7345, @inteon)
  • Helm: allow enabled to be set as a value to toggle cert-manager as a dependency. (#​7356, @inteon)
  • BUGFIX: A change in v1.16.0 caused cert-manager's ACME ClusterIssuer to look in the wrong namespace for resources required for the issuance (e.g. credential Secrets). This is now fixed in v1.16.1. (#​7342, @inteon)

v1.16.0

Compare Source

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

The cert-manager 1.16 release includes: new Helm chart features, more Prometheus metrics, memory optimizations, and various improvements and bug fixes for the ACME issuer and Venafi Issuer.

📖 Read the complete 1.16 release notes at cert-manager.io.

⚠️ Known issues

  1. Helm Chart: JSON schema prevents the chart being used as a sub-chart on Rancher RKE.
  2. ACME DNS01 ClusterIssuer fail while loading credentials from Secret resources.

❗ Breaking changes

  1. Helm schema validation may reject your existing Helm values files if they contain typos or unrecognized fields.
  2. Venafi Issuer may fail to renew certificates if the requested duration conflicts with the CA’s minimum or maximum policy settings in Venafi.
  3. Venafi Issuer may fail to renew Certificates if the issuer has been configured for TPP with username-password authentication.

📖 Read the complete 1.16 release notes at cert-manager.io.

📜 Changes since v1.15.0

📖 Read the complete 1.16 release notes at cert-manager.io.

Feature
  • Add SecretRef support for Venafi TPP issuer CA Bundle (#​7036, @sankalp-at-gh)
  • Add renewBeforePercentage alternative to renewBefore (#​6987, @cbroglie)
  • Add a metrics server to the cainjector (#​7194, @wallrj)
  • Add a metrics server to the webhook (#​7182, @wallrj)
  • Add client certificate auth method for Vault issuer (#​4330, @joshmue)
  • Add process and go runtime metrics for controller (#​6966, @mindw)
  • Added app.kubernetes.io/managed-by: cert-manager label to the cert-manager-webhook-ca Secret (#​7154, @jrcichra)
  • Allow the user to specify a Pod template when using GatewayAPI HTTP01 solver, this mirrors the behavior when using the Ingress HTTP01 solver. (#​7211, @ThatsMrTalbot)
  • Create token request RBAC for the cert-manager ServiceAccount by default (#​7213, @Jasper-Ben)
  • Feature: Append cert-manager user-agent string to all AWS API requests, including IMDS and STS requests. (#​7295, @wallrj)
  • Feature: Log AWS SDK warnings and API requests at cert-manager debug level to help debug AWS Route53 problems in the field. (#​7292, @wallrj)
  • Feature: The Route53 DNS solver of the ACME Issuer will now use regional STS endpoints computed from the region that is supplied in the Issuer spec or in the AWS_REGION environment variable.
    Feature: The Route53 DNS solver of the ACME Issuer now uses the "ambient" region (AWS_REGION or AWS_DEFAULT_REGION) if issuer.spec.acme.solvers.dns01.route53.region is empty; regardless of the flags --issuer-ambient-credentials and --cluster-issuer-ambient-credentials. (#​7299, @wallrj)
  • Helm: adds JSON schema validation for the Helm values. (#​7069, @inteon)
  • If the --controllers flag only specifies disabled controllers, the default controllers are now enabled implicitly.
    Added disableAutoApproval and approveSignerNames Helm chart options. (#​7049, @inteon)
  • Make it easier to configure cert-manager using Helm by defaulting config.apiVersion and config.kind within the Helm chart. (#​7126, @ThatsMrTalbot)
  • Now passes down specified duration to Venafi client instead of using the CA default only. (#​7104, @Guitarkalle)
  • Reduce the memory usage of cainjector, by only caching the metadata of Secret resources.
    Reduce the load on the K8S API server when cainjector starts up, by only listing the metadata of Secret resources. (#​7161, @wallrj)
  • The Route53 DNS01 solver of the ACME Issuer can now detect the AWS region from the AWS_REGION and AWS_DEFAULT_REGION environment variables, which is set by the IAM for Service Accounts (IRSA) webhook and by the Pod Identity webhook.
    The issuer.spec.acme.solvers.dns01.route53.region field is now optional.
    The API documentation of the region field has been updated to explain when and how the region value is used. (#​7287, @wallrj)
  • Venafi TPP issuer can now be used with a username & password combination with OAuth. Fixes #​4653.
    Breaking: cert-manager will no longer use the API Key authentication method which was deprecated in 20.2 and since removed in 24.1 of TPP. (#​7084, @hawksight)
  • You can now configure the pod security context of HTTP-01 solver pods. (#​5373, @aidy)
  • Helm: New value webhook.extraEnv, allows you to set custom environment variables in the webhook Pod.
    Helm: New value cainjector.extraEnv, allows you to set custom environment variables in the cainjector Pod.
    Helm: New value startupapicheck.extraEnv, allows you to set custom environment variables in the startupapicheck Pod. (#​7319, @wallrj)
Bug or Regression
  • Adds support (behind a flag) to use a domain qualified finalizer. If the feature is enabled (which is not by default), it should prevent Kubernetes from reporting: metadata.finalizers: "finalizer.acme.cert-manager.io": prefer a domain-qualified finalizer name to avoid accidental conflicts with other finalizer writers (#​7273, @jsoref)
  • BUGFIX Route53: explicitly set the aws-global STS region which is now required by the github.com/aws/aws-sdk-go-v2 library. (#​7108, @inteon)
  • BUGFIX: fix issue that caused Vault issuer to not retry signing when an error was encountered. (#​7105, @inteon)
  • BUGFIX: the dynamic certificate source used by the webhook TLS server failed to detect a root CA approaching expiration, due to a calculation error. This will cause the webhook TLS server to fail renewing its CA certificate. Please upgrade before the expiration of this CA certificate is reached. (#​7230, @inteon)
  • Bugfix: Prevent aggressive Route53 retries caused by IRSA authentication failures by removing the Amazon Request ID from errors wrapped by the default credential cache. (#​7291, @wallrj)
  • Bugfix: Prevent aggressive Route53 retries caused by STS authentication failures by removing the Amazon Request ID from STS errors. (#​7259, @wallrj)
  • Bump grpc-go to fix GHSA-xr7q-jx4m-x55m (#​7164, @SgtCoDFish)
  • Bump the go-retryablehttp dependency to fix CVE-2024-6104 (#​7125, @SgtCoDFish)
  • Fix Azure DNS causing panics whenever authentication error happens (#​7177, @eplightning)
  • Fix incorrect indentation of endpointAdditionalProperties in the PodMonitor template of the Helm chart (#​7190, @wallrj)
  • Fixes ACME HTTP01 challenge behavior when using Gateway API to prevent unbounded creation of HTTPRoute resources (#​7178, @miguelvr)
  • Handle errors arising from challenges missing from the ACME server (#​7202, @bdols)
  • Helm BUGFIX: the cainjector ConfigMap was not mounted in the cainjector deployment. (#​7052, @inteon)
  • Improve the startupapicheck: validate that the validating and mutating webhooks are doing their job. (#​7057, @inteon)
  • The KeyUsages X.509 extension is no longer added when there are no key usages set (in accordance to RFC 5280 Section 4.2.1.3) (#​7250, @inteon)
  • Update github.com/Azure/azure-sdk-for-go/sdk/azidentity to address CVE-2024-35255 (#​7087, @dependabot[bot])
Other (Cleanup or Flake)
  • Old API versions were removed from the codebase.
    Removed:
    (acme.)cert-manager.io/v1alpha2
    (acme.)cert-manager.io/v1alpha3
    (acme.)cert-manager.io/v1beta1 (#​7278, @inteon)
  • Upgrading to client-go v0.31.0 removes a lot of noisy reflector.go: unable to sync list result: internal error: cannot cast object DeletedFinalStateUnknown errors from logs. (#​7237, @inteon)
  • Bump Go to v1.23.2 (#​7324, @cert-manager-bot)

v1.15.5

Compare Source

v1.15.4

Compare Source

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

This patch release of cert-manager 1.15 makes several changes to how PEM input is validated, adding maximum sizes appropriate to the type of PEM data which is being parsed.

This is to prevent an unacceptable slow-down in parsing specially crafted PEM data. The issue was found by Google's OSS-Fuzz project.

The issue is low severity; to exploit the PEM issue would require privileged access which would likely allow Denial-of-Service through other methods.

Note also that since most PEM data parsed by cert-manager comes from ConfigMap or Secret resources which have a max size limit of approximately 1MB, it's difficult to force cert-manager to parse large amounts of PEM data.

Further information is available in GHSA-r4pg-vg54-wxx4

In addition, the version of Go used to build cert-manager 1.15 was updated along with the base images, and a Route53 bug fix was backported.

Changes by Kind

Bug or Regression
  • Bugfix: Prevent aggressive Route53 retries caused by STS authentication failures by removing the Amazon Request ID from STS errors. (#​7261, @​cert-manager-bot)
  • Set a maximum size for PEM inputs which cert-manager will accept to remove possibility of taking a long time to process an input (#​7402, @​SgtCoDFish)
Other (Cleanup or Flake)

v1.15.3

Compare Source

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

🔗 See v1.15.0 for more information about cert-manager 1.15 and read-before-upgrade info.

📜 Changes since v1.15.2

Bug or Regression
  • BUGFIX: the dynamic certificate source used by the webhook TLS server failed to detect a root CA approaching expiration, due to a calculation error. This will cause the webhook TLS server to fail renewing its CA certificate. Please upgrade before the expiration of this CA certificate is reached. (#​7232, @​cert-manager-bot)

v1.15.2

Compare Source

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

🔗 See v1.15.0 for more information about cert-manager 1.15 and read-before-upgrade info.

📜 Changes since v1.15.1

Bug or Regression

v1.15.1

Compare Source

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

🔗 See v1.15.0 for more information about cert-manager 1.15 and read-before-upgrade info.

📜 Changes since v1.15.0

Bug or Regression
  • BUGFIX: fix issue that caused Vault issuer to not retry signing when an error was encountered. (#​7111, @​inteon)
Other (Cleanup or Flake)

v1.15.0

Compare Source

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

cert-manager 1.15 promotes several features to beta, including GatewayAPI support (ExperimentalGatewayAPISupport), the ability to provide a subject in the Certificate that will be used literally in the CertificateSigningRequest (LiteralCertificateSubject) and the outputting of additional certificate formats (AdditionalCertificateOutputFormats).

[!NOTE]

The cmctl binary have been moved to https://github.com/cert-manager/cmctl/releases.
For the startupapicheck Job you should update references to point at quay.io/jetstack/cert-manager-startupapicheck

[!NOTE]

From this release, the Helm chart will no longer uninstall the CRDs when the chart is uninstalled. If you want the CRDs to be removed on uninstall use crds.keep=false when installing the Helm chart.

Community

Thanks again to all open-source contributors with commits in this release, including: @​Pionerd, @​SgtCoDFish, @​ThatsMrTalbot, @​andrey-dubnik, @​bwaldrep, @​eplightning, @​erikgb, @​findnature, @​gplessis, @​import-shiburin, @​inteon, @​jkroepke, @​lunarwhite, @​mangeshhambarde, @​pwhitehead-splunk & @​rodrigorfk, @​wallrj.

Thanks also to the following cert-manager maintainers for their contributions during this release: @​SgtCoDFish, @​SpectralHiss, @​ThatsMrTalbot, @​hawksight, @​inteon, @​maelvls & @​wallrj.

Equally thanks to everyone who provided feedback, helped users and raised issues on GitHub and Slack and joined our meetings!

Thanks also to the CNCF, which provides resources and support, and to the AWS open source team for being good community members and for their maintenance of the PrivateCA Issuer.

In addition, massive thanks to Venafi for contributing developer time and resources towards the continued maintenance of cert-manager projects.

Changes by Kind

Feature
  • GatewayAPI support has graduated to Beta. Add the --enable-gateway-api flag to enable the integration. (#​6961, @​ThatsMrTalbot)
  • Add support to specify a custom key alias in a JKS Keystore (#​6807, @​bwaldrep)
  • Add the ability to communicate with Vault via mTLS when strict client certificates is enabled at Vault server side (#​6614, @​rodrigorfk)
  • Added option to provide additional audiences in the service account auth section for vault (#​6718, @​andrey-dubnik)
  • Venafi Issuer now sends a cert-manager HTTP User-Agent header in all Venafi Rest API requests.
    For example: cert-manager-certificaterequests-issuer-venafi/v1.15.0+(linux/amd64)+cert-manager/ef068a59008f6ed919b98a7177921ddc9e297200. (#​6865, @​wallrj)
  • Add hint to validation error message to help users of external issuers more easily fix the issue if they specify a Kind but forget the Group (#​6913, @​SgtCoDFish)
  • Add support for numeric OID types in LiteralSubject. Eg. "1.2.3.4=String Value" (#​6775, @​inteon)
  • Promote the LiteralCertificateSubject feature to Beta. (#​7030, @​inteon)
  • Promoted the AdditionalCertificateOutputFormats feature gate to Beta (enabled by default). (#​6970, @​erikgb)
  • The Helm chart now allows you to supply extraObjects; a list of yaml manifests which will helm will install and uninstall with the cert-manager manifests. (#​6424, @​gplessis)
  • Update the Route53 provider to support fetching credentials using AssumeRoleWithWebIdentity (#​6878, @​pwhitehead-splunk)
  • Helm can now add optional hostAliases to cert-manager Pod to allow the DNS self-check to pass in custom scenarios. (#​6456, @​Pionerd)
  • Added a new Ingress annotation for copying specific Ingress annotations to Certificate's secretTemplate (#​6839, @​mangeshhambarde)
  • Added option to define additional token audiences for the Vault Kubernetes auth (#​6744, @​andrey-dubnik)
  • Allow cert-manager.io/allow-direct-injection in annotations (#​6801, @​jkroepke)
Design
Bug or Regression
  • BUGFIX: Fixes issue with JSON-logging, where only a subset of the log messages were output as JSON. (#​6779, @​inteon)
  • BUGFIX: JKS and PKCS12 stores now contain the full set of CAs specified by an issuer (#​6806, @​bwaldrep)
  • BUGFIX: cainjector leaderelection flag/config option defaults are missing (#​6816, @​inteon)
  • BUGFIX: cert-manager issuers incorrectly copied the critical flag from the CSR instead of re-calculating that field themselves. (#​6724, @​inteon)
  • Breaking Change: Fixed unintended certificate chain is used if preferredChain is configured. (#​6755, @​import-shiburin)
  • Bugfix: LiteralSubjects with a #= value can result in memory issues due to faulty BER parser (github.com/go-asn1-ber/asn1-ber). (#​6770, @​inteon)
  • DigitalOcean: Ensure that only TXT records are considered for deletion when cleaning up after an ACME challenge (#​6875, @​SgtCoDFish)
  • Fix backwards incompatible removal of default prometheus Service resource. (#​6699, @​inteon)
  • Fix broken cainjector image value in Helm chart (#​6692, @​SgtCoDFish)
  • Helm: Fix a bug in the logic that differentiates between 0 and an empty value. (#​6713, @​inteon)
  • Make sure the Azure SDK error messages are stable. (#​6676, @​inteon)
  • When using the literalSubject on a Certificate, the webhook validation for the common name now also points to the literalSubject. (#​6767, @​lunarwhite)
  • Bump golang.org/x/net to fix CVE-2023-45288 (#​6929, @​SgtCoDFish)
  • Fix ACME issuer being stuck waiting for DNS propagation when using Azure DNS with multiple instances issuing for the same FQDN (#​6351, @​eplightning)
  • Fix cainjector ConfigMap not mounted in the cainjector deployment. (#​7055, @​inteon)
  • Added disableAutoApproval and approveSignerNames Helm chart options. (#​7054, @​inteon)
Other (Cleanup or Flake)

v1.14.7

Compare Source

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

📜 Changes since v1.14.6

Bugfixes
Other (Cleanup or Flake)

v1.14.6

Compare Source

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

📜 Changes since v1.14.5

Other (Cleanup or Flake)
aws/aws-sdk-go-v2 (github.com/aws/aws-sdk-go-v2)

v1.33.0

Compare Source

v1.32.8

Compare Source

v1.32.7

Compare Source

v1.32.6

Compare Source

v1.32.5

Compare Source

v1.32.4

Compare Source

v1.32.3

Compare Source

v1.32.2

Compare Source

v1.32.1

Compare Source

v1.32.0

Compare Source

v1.31.0

Compare Source

v1.30.5

Compare Source

v1.30.4

Compare Source

[v1.30.3](https://redirect.github.com/aws/aws


Configuration

📅 Schedule: Branch creation - "after 9am on Wednesday,before 12pm on Wednesday" in timezone America/New_York, 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.

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

@bmsiegel bmsiegel force-pushed the main branch 2 times, most recently from 27dad65 to 84be0aa Compare May 15, 2024 02:20
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 74972a9 to acc07aa Compare May 15, 2024 02:23
@bmsiegel bmsiegel force-pushed the main branch 2 times, most recently from bc4aace to 853e706 Compare May 15, 2024 03:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from e45635e to 1e90508 Compare May 15, 2024 13:16
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 7aef09c to fe24939 Compare May 25, 2024 05:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from fe24939 to 8292018 Compare June 4, 2024 20:21
Copy link
Author

renovate bot commented Jun 4, 2024

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

  • 40 additional dependencies were updated

Details:

Package Change
github.com/aws/aws-sdk-go-v2/feature/ec2/imds v1.16.1 -> v1.16.24
github.com/aws/aws-sdk-go-v2/internal/configsources v1.3.5 -> v1.3.28
github.com/aws/aws-sdk-go-v2/internal/endpoints/v2 v2.6.5 -> v2.6.28
github.com/aws/aws-sdk-go-v2/internal/ini v1.8.0 -> v1.8.1
github.com/aws/aws-sdk-go-v2/service/internal/accept-encoding v1.11.2 -> v1.12.1
github.com/aws/aws-sdk-go-v2/service/internal/presigned-url v1.11.7 -> v1.12.9
github.com/aws/aws-sdk-go-v2/service/sso v1.20.6 -> v1.24.10
github.com/aws/aws-sdk-go-v2/service/ssooidc v1.24.0 -> v1.28.9
github.com/aws/smithy-go v1.20.2 -> v1.22.1
github.com/cespare/xxhash/v2 v2.2.0 -> v2.3.0
github.com/emicklei/go-restful/v3 v3.11.0 -> v3.12.1
github.com/evanphx/json-patch v5.7.0+incompatible -> v5.9.0+incompatible
github.com/go-asn1-ber/asn1-ber v1.5.5 -> v1.5.6
github.com/go-ldap/ldap/v3 v3.4.6 -> v3.4.8
github.com/go-openapi/jsonpointer v0.20.2 -> v0.21.0
github.com/go-openapi/jsonreference v0.20.4 -> v0.21.0
github.com/go-openapi/swag v0.22.7 -> v0.23.0
github.com/google/uuid v1.5.0 -> v1.6.0
github.com/prometheus/client_golang v1.18.0 -> v1.20.4
github.com/prometheus/client_model v0.5.0 -> v0.6.1
github.com/prometheus/common v0.45.0 -> v0.55.0
github.com/prometheus/procfs v0.12.0 -> v0.15.1
github.com/spf13/cobra v1.8.0 -> v1.8.1
go.uber.org/zap v1.26.0 -> v1.27.0
golang.org/x/crypto v0.22.0 -> v0.31.0
golang.org/x/exp v0.0.0-20231226003508-02704c960a9b -> v0.0.0-20240719175910-8a7402abbf56
golang.org/x/net v0.24.0 -> v0.33.0
golang.org/x/oauth2 v0.15.0 -> v0.23.0
golang.org/x/sys v0.19.0 -> v0.28.0
golang.org/x/term v0.19.0 -> v0.27.0
golang.org/x/text v0.14.0 -> v0.21.0
golang.org/x/time v0.5.0 -> v0.7.0
google.golang.org/protobuf v1.33.0 -> v1.35.1
k8s.io/apiextensions-apiserver v0.30.0 -> v0.32.0
k8s.io/component-base v0.30.0 -> v0.32.0
k8s.io/klog/v2 v2.120.1 -> v2.130.1
k8s.io/kube-openapi v0.0.0-20240228011516-70dd3763d340 -> v0.0.0-20241105132330-32ad38e42d3f
sigs.k8s.io/gateway-api v1.0.0 -> v1.1.0
sigs.k8s.io/json v0.0.0-20221116044647-bc3834ca7abd -> v0.0.0-20241010143419-9aa6b5e7a4b3
sigs.k8s.io/structured-merge-diff/v4 v4.4.1 -> v4.4.2

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 9b0821e to bd4c42f Compare June 8, 2024 05:34
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from e0d8c8d to 0c8f3eb Compare June 19, 2024 17:56
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from d56f59c to 3681dac Compare June 21, 2024 17:30
@bmsiegel bmsiegel force-pushed the main branch 2 times, most recently from 7a59d93 to 368a905 Compare June 21, 2024 17:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from b7c55df to a817443 Compare June 21, 2024 18:35
@renovate renovate bot changed the title chore(deps): update all non-major dependencies Update all non-major dependencies Jun 22, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a817443 to 6bec6d7 Compare June 25, 2024 01:16
@bmsiegel bmsiegel force-pushed the main branch 2 times, most recently from 43e222f to 368a905 Compare June 25, 2024 01:17
@renovate renovate bot changed the title Update all non-major dependencies chore(deps): update all non-major dependencies Jun 25, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 6bec6d7 to 0b27cfa Compare June 25, 2024 01:19
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 47fac60 to c778021 Compare October 2, 2024 02:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 7ca2011 to 386bc07 Compare October 10, 2024 20:17
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 386bc07 to ecffacd Compare October 16, 2024 23:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 3cdee0a to cda3f35 Compare October 29, 2024 05:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from cfba122 to c33badd Compare November 8, 2024 08:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from d9a4191 to 3eed731 Compare November 21, 2024 08:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 5af5323 to 8090f9d Compare November 24, 2024 05:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 05ecf7d to 0640f3b Compare December 11, 2024 02:41
@renovate renovate bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies Dec 11, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0640f3b to fa1a53f Compare December 12, 2024 01:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from fa1a53f to bb7870a Compare December 21, 2024 11:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from bb7870a to 90ac023 Compare December 31, 2024 23:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from cca2221 to 340bdbc Compare January 15, 2025 20:03
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 340bdbc to cb4a8fc Compare January 17, 2025 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants