change detected:
* key "$.version" updated from "v1.13.3" to "v1.14.2", in file "cert-manager/manifest.yaml"
v1.14.2
Release published on the 2024-02-08 13:37:30 +0000 UTC at the url https://github.com/cert-manager/cert-manager/releases/tag/v1.14.2
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
cert-manager 1.14 brings a variety of features, security improvements and bug fixes, including: support for creating X.509 certificates with "Other Name" fields, and support for creating CA certificates with "Name Constraints" and "Authority Information Accessors" extensions.
### ℹ️ Documentation
[Release notes](https://cert-manager.io/docs/releases/release-notes/release-notes-1.14)
[Upgrade notes](https://cert-manager.io/docs/releases/upgrading/upgrading-1.13-1.14)
[Installation instructions](https://cert-manager.io/docs/installation/)
### 🔧 Breaking changes
See `Breaking changes` in [v1.14.0 release notes](https://github.com/cert-manager/cert-manager/releases/tag/v1.14.0)
### 📜 Changes since `v1.14.1`
#### Bug or Regression
- BUGFIX: cert-manager CA and SelfSigned issuers incorrectly copied the critical flag from the CSR instead of re-calculating that field themselves. (#6727, @jetstack-bot)
- Helm: Fix a bug in the logic that differentiates between 0 and an empty value. (#6729, @jetstack-bot)
#### Other (Cleanup or Flake)
- Bump golang to 1.21.7 (#6735, @jetstack-bot)
v1.14.3
Release published on the 2024-02-23 10:49:04 +0000 UTC at the url https://github.com/cert-manager/cert-manager/releases/tag/v1.14.3
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
cert-manager 1.14 brings a variety of features, security improvements and bug fixes, including: support for creating X.509 certificates with "Other Name" fields, and support for creating CA certificates with "Name Constraints" and "Authority Information Accessors" extensions.
### ⚠️ Known Issues
- ACME Issuer (Let's Encrypt): wrong certificate chain may be used if preferredChain is configured: see [release docs](https://cert-manager.io/docs/releases/release-notes/release-notes-1.14/#acme-issuer-lets-encrypt-wrong-certificate-chain-may-be-used-if-preferredchain-is-configured---6755-6757) for more info and mitigations
### ℹ️ Documentation
[Release notes](https://cert-manager.io/docs/releases/release-notes/release-notes-1.14)
[Upgrade notes](https://cert-manager.io/docs/releases/upgrading/upgrading-1.13-1.14)
[Installation instructions](https://cert-manager.io/docs/installation/)
### 🔧 Breaking changes
See Breaking changes in [v1.14.0 release notes](https://github.com/cert-manager/cert-manager/releases/tag/v1.14.0)
### 📜 Changes since v1.14.2
#### Bug or Regression
- BUGFIX: Fixes issue with JSON-logging, where only a subset of the log messages were output as JSON. (#6781, @jetstack-bot)
- BUGFIX: LiteralSubjects with a #= value can result in memory issues due to faulty BER parser (github.com/go-asn1-ber/asn1-ber). (#6774, @jetstack-bot)
Update cert-manager/install.sh
1 file(s) updated with "/download/v1.14.2/":
* cert-manager/install.sh
Bump CIVO marketplace cert-manager version
Update cert-manager/manifest.yaml
change detected: * key "$.version" updated from "v1.13.3" to "v1.14.2", in file "cert-manager/manifest.yaml"
v1.14.2
v1.14.3
Update cert-manager/install.sh
1 file(s) updated with "/download/v1.14.2/": * cert-manager/install.sh
Created automatically by Updatecli
Options:
Most of Updatecli configuration is done via its manifest(s).
Feel free to report any issues at github.com/updatecli/updatecli.
If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!