Update Helm release cert-manager to v1.19.1 #1775
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/cert-manager-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v1.19.0
->v1.19.1
Release Notes
cert-manager/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
andCertificateRequest.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-manager1.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
, andCVE-2025-61725
.Changes since
v1.19.0
:Bug or Regression
issuerRef
of a Certificate was omitted, upgrading to1.19.x
incorrectly caused the certificate to be renewed (#8175, @cert-manager-bot)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.