Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 3, 2025

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
azure/setup-helm action patch v4.3.0 -> v4.3.1 age adoption passing confidence
github.com/cert-manager/cert-manager require minor v1.18.2 -> v1.19.1 age adoption passing confidence
github.com/gophercloud/gophercloud/v2 require minor v2.8.0 -> v2.9.0 age adoption passing confidence
github.com/gophercloud/utils/v2 require patch v2.0.0-20250930154317-576cdf6142a7 -> v2.0.0-20251121145439-0a38d66a3d88 age adoption passing confidence
github.com/onsi/ginkgo/v2 require minor v2.26.0 -> v2.27.2 age adoption passing confidence
go.uber.org/zap require patch v1.27.0 -> v1.27.1 age adoption passing confidence
sigs.k8s.io/controller-runtime require patch v0.22.3 -> v0.22.4 age adoption passing confidence
sigs.k8s.io/structured-merge-diff/v6 require patch v6.3.0 -> v6.3.1 age adoption passing confidence

Release Notes

azure/setup-helm (azure/setup-helm)

v4.3.1

Compare Source

Changed
Added
cert-manager/cert-manager (github.com/cert-manager/cert-manager)

v1.19.1

Compare Source

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

We reverted the CRD-based API defaults for Certificate.Spec.IssuerRef and CertificateRequest.Spec.IssuerRef after they were found to cause unexpected certificate renewals after upgrading to 1.19.0. We will try re-introducing these API defaults in cert-manager 1.20.
We fixed a bug that caused certificates to be re-issued unexpectedly if the issuerRef kind or group was changed to one of the "runtime" default values.
We upgraded Go to 1.25.3 to address the following security vulnerabilities: CVE-2025-61724, CVE-2025-58187, CVE-2025-47912, CVE-2025-58183, CVE-2025-61723, CVE-2025-58186, CVE-2025-58185, CVE-2025-58188, and CVE-2025-61725.

📖 Read the full 1.19 release notes on the cert-manager.io website before upgrading.

Changes since v1.19.0:

Bug or Regression
  • BUGFIX: in case kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed (#​8175, @​cert-manager-bot)
  • Bump Go to 1.25.3 to fix a backwards incompatible change to the validation of DNS names in X.509 SAN fields which prevented the use of DNS names with a trailing dot (#​8177, @​wallrj-cyberark)
  • Revert API defaults for issuer reference kind and group introduced in 0.19.0 (#​8178, @​cert-manager-bot)

v1.19.0

Compare Source

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

⚠️ Known issues: The following known issues are fixed in v1.19.1:

This release focuses on expanding platform compatibility, improving deployment flexibility, enhancing observability, and addressing key reliability issues.

📖 Read the full release notes at cert-manager.io: https://cert-manager.io/docs/releases/release-notes/release-notes-1.19

Changes since v1.18.0:

Feature

  • Add IPv6 rules to the default network policy (#​7726, @​jcpunk)
  • Add global.nodeSelector to helm chart to allow for a single nodeSelector to be set across all services. (#​7818, @​StingRayZA)
  • Add a feature gate to default to Ingress pathType Exact in ACME HTTP01 Ingress challenge solvers. (#​7795, @​sspreitzer)
  • Add generated applyconfigurations allowing clients to make type-safe server-side apply requests for cert-manager resources. (#​7866, @​erikgb)
  • Added API defaults to issuer references group (cert-manager.io) and kind (Issuer). (#​7414, @​erikgb)
  • Added certmanager_certificate_challenge_status Prometheus metric. (#​7736, @​hjoshi123)
  • Added protocol field for rfc2136 DNS01 provider (#​7881, @​hjoshi123)
  • Added experimental field hostUsers flag to all pods. Not set by default. (#​7973, @​hjoshi123)
  • Support configurable resource requests and limits for ACME HTTP01 solver pods through ClusterIssuer and Issuer specifications, allowing granular resource management that overrides global --acme-http01-solver-resource-* settings. (#​7972, @​lunarwhite)
  • The CAInjectorMerging feature has been promoted to BETA and is now enabled by default (#​8017, @​ThatsMrTalbot)
  • The controller, webhook and ca-injector now log their version and git commit on startup for easier debugging and support. (#​8072, @​prasad89)
  • Updated certificate metrics to the collector approach. (#​7856, @​hjoshi123)

Bug or Regression

  • ACME: Increased challenge authorization timeout to 2 minutes to fix error waiting for authorization (#​7796, @​hjoshi123)
  • BUGFIX: permitted URI domains were incorrectly used to set the excluded URI domains in the CSR's name constraints (#​7816, @​kinolaev)
  • Enforced ACME HTTP-01 solver validation to properly reject configurations when multiple ingress options (class, ingressClassName, name) are specified simultaneously (#​8021, @​lunarwhite)
  • Increase maximum sizes of PEM certificates and chains which can be parsed in cert-manager, to handle leaf certificates with large numbers of DNS names or other identities (#​7961, @​SgtCoDFish)
  • Reverted adding the global.rbac.disableHTTPChallengesRole Helm option. (#​7836, @​inteon)
  • This change removes the path label of core ACME client metrics and will require users to update their monitoring dashboards and alerting rules if using those metrics. (#​8109, @​mladen-rusev-cyberark)
  • Use the latest version of ingress-nginx in E2E tests to ensure compatibility (#​7792, @​wallrj)

Other (Cleanup or Flake)

  • Helm: Fix naming template of tokenrequest RoleBinding resource to improve consistency (#​7761, @​lunarwhite)
  • Improve error messages when certificates, CRLs or private keys fail admission due to malformed or missing PEM data (#​7928, @​SgtCoDFish)
  • Major upgrade of Akamai SDK. NOTE: The new version has not been fully tested end-to-end due to the lack of cloud infrastructure. (#​8003, @​hjoshi123)
  • Update kind images to include the Kubernetes 1.33 node image (#​7786, @​wallrj)
  • Use maps.Copy for cleaner map handling (#​8092, @​quantpoet)
  • Vault: Migrate Vault E2E add-on tests from deprecated vault-client-go to the new vault/api client. (#​8059, @​armagankaratosun)

v1.18.3

Compare Source

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

We fixed a bug which caused certificates to be re-issued unexpectedly, if the issuerRef kind or group was changed to one of the "runtime" default values. We increased the size limit when parsing PEM certificate chains to handle leaf certificates with large numbers of DNS named or other identities. We upgraded Go to 1.24.9 to fix various non-critical security vulnerabilities.

📖 Read the full 1.18 release notes on the cert-manager.io website before upgrading.

Changes since v1.18.2:

Bug or Regression
Other (Cleanup or Flake)
gophercloud/gophercloud (github.com/gophercloud/gophercloud/v2)

v2.9.0

Compare Source

What's Changed

Full Changelog: gophercloud/gophercloud@v2.8.0...v2.9.0

onsi/ginkgo (github.com/onsi/ginkgo/v2)

v2.27.2

Compare Source

2.27.2

Fixes
  • inline automaxprocs to simplify dependencies; this will be removed when Go 1.26 comes out [a69113a]
Maintenance
  • Fix syntax errors and typo [a99c6e0]
  • Fix paragraph position error [f993df5]

v2.27.1

Compare Source

2.27.1

Fixes
  • Fix Ginkgo Reporter slice-bounds panic [606c1cb]
  • Bug Fix: Add GinkoTBWrapper.Attr() and GinkoTBWrapper.Output() [a6463b3]

v2.27.0

Compare Source

2.27.0

Features
Transforming Nodes during Tree Construction

This release adds support for NodeArgsTransformers that can be registered with AddTreeConstructionNodeArgsTransformer.

These are called during the tree construction phase as nodes are constructed and can modify the node strings and decorators. This enables frameworks built on top of Ginkgo to modify Ginkgo nodes and enforce conventions.

Learn more here.

Spec Prioritization

A new SpecPriority(int) decorator has been added. Ginkgo will honor priority when ordering specs, ensuring that higher priority specs start running before lower priority specs

Learn more here.

Maintenance
uber-go/zap (go.uber.org/zap)

v1.27.1

Compare Source

Enhancements:

  • #​1501: prevent Object from panicking on nils
  • #​1511: Fix a race condition in WithLazy.

Thanks to @​rabbbit, @​alshopov, @​jquirke, @​arukiidou for their contributions to this release.

kubernetes-sigs/controller-runtime (sigs.k8s.io/controller-runtime)

v0.22.4

Compare Source

What's Changed

Full Changelog: kubernetes-sigs/controller-runtime@v0.22.3...v0.22.4

kubernetes-sigs/structured-merge-diff (sigs.k8s.io/structured-merge-diff/v6)

v6.3.1

Compare Source


Configuration

📅 Schedule: Branch creation - "before 8am on Friday" (UTC), 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.

@renovate
Copy link
Contributor Author

renovate bot commented Dec 3, 2025

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

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

Details:

Package Change
go 1.25 -> 1.25.0
github.com/emicklei/go-restful/v3 v3.12.2 -> v3.13.0
github.com/go-openapi/jsonpointer v0.21.0 -> v0.22.1
github.com/go-openapi/jsonreference v0.21.0 -> v0.21.2
github.com/gofrs/uuid/v5 v5.3.2 -> v5.4.0
github.com/grpc-ecosystem/grpc-gateway/v2 v2.26.3 -> v2.27.1
github.com/prometheus/client_golang v1.22.0 -> v1.23.2
github.com/prometheus/client_model v0.6.1 -> v0.6.2
github.com/prometheus/common v0.62.0 -> v0.66.1
github.com/prometheus/procfs v0.15.1 -> v0.17.0
github.com/spf13/cobra v1.9.1 -> v1.10.1
github.com/spf13/pflag v1.0.6 -> v1.0.10
github.com/stoewer/go-strcase v1.3.0 -> v1.3.1
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.58.0 -> v0.61.0
go.opentelemetry.io/otel v1.35.0 -> v1.37.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.34.0 -> v1.37.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.34.0 -> v1.37.0
go.opentelemetry.io/otel/metric v1.35.0 -> v1.37.0
go.opentelemetry.io/otel/sdk v1.34.0 -> v1.37.0
go.opentelemetry.io/otel/trace v1.35.0 -> v1.37.0
go.opentelemetry.io/proto/otlp v1.5.0 -> v1.7.0
golang.org/x/exp v0.0.0-20241217172543-b2144cdd0a67 -> v0.0.0-20250718183923-645b1fa84792
golang.org/x/net v0.43.0 -> v0.44.0
golang.org/x/oauth2 v0.28.0 -> v0.31.0
golang.org/x/sync v0.16.0 -> v0.17.0
golang.org/x/sys v0.35.0 -> v0.36.0
golang.org/x/term v0.34.0 -> v0.35.0
golang.org/x/text v0.28.0 -> v0.29.0
golang.org/x/time v0.9.0 -> v0.13.0
gomodules.xyz/jsonpatch/v2 v2.4.0 -> v2.5.0
google.golang.org/genproto/googleapis/api v0.0.0-20250303144028-a0af3efb3deb -> v0.0.0-20250721164621-a45f3dfb1074
google.golang.org/genproto/googleapis/rpc v0.0.0-20250303144028-a0af3efb3deb -> v0.0.0-20250929231259-57b25ae835d4
google.golang.org/grpc v1.72.1 -> v1.75.1
google.golang.org/protobuf v1.36.7 -> v1.36.9
gopkg.in/evanphx/json-patch.v4 v4.12.0 -> v4.13.0
k8s.io/kube-openapi v0.0.0-20250710124328-f3f2b991d03b -> v0.0.0-20250910181357-589584f1c912
k8s.io/utils v0.0.0-20250604170112-4c0f3b243397 -> v0.0.0-20250820121507-0af2bda4dd1d
sigs.k8s.io/apiserver-network-proxy/konnectivity-client v0.31.2 -> v0.33.0
sigs.k8s.io/gateway-api v1.1.0 -> v1.4.0
sigs.k8s.io/json v0.0.0-20241014173422-cfa47c3a1cc8 -> v0.0.0-20250730193827-2d320260d730

@renovate renovate bot force-pushed the renovate/external-dependencies branch from 351a5d3 to 718c6fb Compare December 3, 2025 10:32
@notandy notandy self-requested a review December 3, 2025 15:03
@notandy notandy merged commit 756be85 into main Dec 3, 2025
7 checks passed
@renovate renovate bot deleted the renovate/external-dependencies branch December 3, 2025 15:07
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.

5 participants