10000 chore(deps): update helm release trust-manager to v0.18.0 by renovate[bot] · Pull Request #903 · owncloud/ocis-charts · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

chore(deps): update helm release trust-manager to v0.18.0 #903

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

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

Conversation

renovate[bot]
Copy link
Contributor
@renovate renovate bot commented May 2, 2025

This PR contains the following updates:

Package Update Change
trust-manager (source) minor v0.16.0 -> v0.18.0

Release Notes

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

v0.18.0

Compare Source

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

This release contains miscellaneous bug fixes and dependency updates.
It is built with Go 1.24.4 which fixes the following vulnerabilities: CVE-2025-22874, CVE-2025-0913, and CVE-2025-4673.

helm inspect chart trust-manager --repo https://charts.jetstack.io --version v0.18.0

What's Changed

Bug Fixes
Non user-facing
Dependabot updates
makefile-modules updates

Full Changelog: cert-manager/trust-manager@v0.17.1...v0.18.0

v0.17.1

Compare Source

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

v0.17.1 is a patch release fixing two specific issues discovered after the release of v0.17.0:

The switch to use our PKCS#12 encoder to encode (Java compatible) PKCS#12 truststores seems to cause a regression. While we still want to deprecate JKS and eventually remove support for it, we will stick to the old JKS encoding library until the feature is removed.

⚠️ We discovered (after the release of v0.17.0) that the Helm value for configuring webhook TLS ciphers was misspelled. Since this was a brand new feature in v0.17.0 we decided to fix this and include the fix in a patch release, even if it's technically a breaking change for any user using this new feature with v0.17.0. Sorry for the inconvenience.

What's Changed

Fixes
Makefile Modules Updates

Full Changelog: cert-manager/trust-manager@v0.17.0...v0.17.1

v0.17.0

Compare Source

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

v0.17.0 contains many interesting new features, mostly from new contributors recruited from cert-manager ContribFest event at KubeCon EU 2025. Welcome! 🫶 Special thanks to @​terricain for implementing one of our most wanted features, allowing adding labels/annotations to target configmaps/secrets! 👏 When configuring trust-manager, it is now possible to disable leader election (@​KyriosGN0) and set webhook TLS requirements like minimum TLS version and acceptable cipher suites (@​arsenalzp). And the Helm chart installation now supports adding common annotations to all resources (@​ali-hamza-noor) and extra resources managed by Helm (@​TTRCmedia).

⚠️ In this release, target JKS truststores are deprecated and will be removed in our next version of the Bundle/ClusterBundle API. Users requiring truststore support should migrate to target PKCS#12 truststores. The encoding of JKS has been migrated to Java-compliant PKCS#12. This should work with recent Java versions, and has been tested with the latest releases of Java LTS: 8, 11, 17, and 21. But please let us know if you are experiencing any issues with this change! We now also support various PKCS#12 profile options (@​terricain), allowing for more compatible and "secure" encoding.

What's Changed

Features
Fixes
Other
Dependency Updates
Makefile Modules Updates

New Contributors

Full Changelog: cert-manager/trust-manager@v0.16.0...v0.17.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 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 from 974b264 to afdfd1d Compare May 6, 2025 17:35
@renovate renovate bot changed the title chore(deps): update helm release trust-manager to v0.17.0 chore(deps): update helm release trust-manager to v0.17.1 May 6, 2025
@renovate renovate bot changed the title chore(deps): update helm release trust-manager to v0.17.1 chore(deps): update helm release trust-manager to v0.18.0 Jun 25, 2025
@renovate renovate bot force-pushed the renovate/trust-manager-0.x branch from afdfd1d to 4bb3626 Compare June 25, 2025 16:37
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
0