Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 30, 2025

This PR contains the following updates:

Package Update Change
trust-manager (source) minor 0.19.0 -> 0.20.2

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

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

v0.20.2

Compare Source

trust-manager is the easiest way to manage security-critical TLS trust bundles in Kubernetes and OpenShift clusters.

This release is a patch release, upgrading Go from 1.25.1 to 1.25.3, fixing a range of CVEs: 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.

Furthermore, additional go dependencies were upgraded where possible.

What's Changed

Full Changelog: cert-manager/trust-manager@v0.20.1...v0.20.2

v0.20.1

Compare Source

trust-manager is the easiest way to manage security-critical TLS trust bundles in Kubernetes and OpenShift clusters.

This release is a patch release, downgrading Go from 1.25.2 to 1.25.1, to avoid the X.509 issues introduced by trying to fix a CVE. See golang/go#75828 (comment) for additional details.

What's Changed

Full Changelog: cert-manager/trust-manager@v0.20.0...v0.20.1

v0.20.0

Compare Source

trust-manager is the easiest way to manage security-critical TLS trust bundles in Kubernetes and OpenShift clusters.

⚠️ Known issue ⚠️

Golang 1.25.2 has a backwards incompatible change (see golang/go#75828 (comment)). This will for example result in certificates with a DNS SAN ending in a dot causing trust-manager to error.


This release primarily contains dependency updates, but also includes a new feature that allows trust-manager to be configured to only operate on a list of named target namespaces. While this feature can allow trust-manager to operate without cluster-wide access to namespaces, the Bundle resource is cluster-scoped, and events from cluster-scoped resources are emitted to the default namespace.

⚠️ The code performing migration from client-side to server-side apply is removed in this release. This means that if upgrading from a really old version of trust-manager (< 0.7.0), you must upgrade to 0.19.0 first.

The work on migrating Bundle to ClusterBundle continues, but none of these changes are user-facing in this release.

What's Changed

Features
  • You can now use trust-manager in the new "restricted" mode to scope trust-manager’s and target caches to a specific set of Kubernetes namespaces provided at startup. When this feature is not used, behavior remains unchanged (cluster-wide watch). By @​asmaoune in #​744
  • Helm: you can now disable the creation of the RBAC resources. By @​asmaoune in #​753
Internal changes
Updates by Dependabot/Renovate
Updates by makefile-modules

New Contributors

Full Changelog: cert-manager/trust-manager@v0.19.0...v0.20.0


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.


  • 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 force-pushed the renovate/trust-manager-0.x branch 3 times, most recently from e33e67a to 2cae09b Compare October 30, 2025 08:15
@renovate renovate bot force-pushed the renovate/trust-manager-0.x branch from 2cae09b to 2771348 Compare October 30, 2025 10:43
@rmvangun rmvangun merged commit 72f6395 into main Oct 30, 2025
6 checks passed
@rmvangun rmvangun deleted the renovate/trust-manager-0.x branch October 30, 2025 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants