chore(deps): update all non-major dependencies #228
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.22.0
->0.23.3
v3.3.0
->v3.5.2
3.17
->3.18
3.17
->3.18
5.23.5
->5.34.6
2.1.3
->2.3.3
0.22.13
->0.28.2
v1.11.0
->v1.12.1
~> 4.0.0
->~> 4.7.0
2.2.3
->2.4.0
10.0.2
->10.3.2
6.14.0
->6.20.3
0.7.2
->0.8.3
v1.9.0
->v1.9.2
~> 1.3.0
->~> 1.4.0
v2.3.1
->v2.4.0
~> 3.2.0
->~> 3.3.0
4.5.2
->4.7.0
v0.26.1
->v0.27.2
v0.26.1
->v0.27.2
~> 2.18.0
->~> 2.20.0
2.9.9
->2.9.10
0.13.9
->0.13.10
4.2.0
->4.4.1
1.23.3-alpine
->1.25.0-alpine
1.1.29
->1.2.34
0.49.1
->0.59.1
v1.0.10
->v1.0.26
Release Notes
actions/actions-runner-controller
v0.23.3
Compare Source
A Kubernetes controller that operates self-hosted runners for GitHub Actions on your Kubernetes cluster.
v0.23.2
Compare Source
A Kubernetes controller that operates self-hosted runners for GitHub Actions on your Kubernetes cluster.
v0.23.1
Compare Source
A Kubernetes controller that operates self-hosted runners for GitHub Actions on your Kubernetes cluster.
v0.23.0
Compare Source
A Kubernetes controller that operates self-hosted runners for GitHub Actions on your Kubernetes cluster.
actions/checkout
v3.5.2
Compare Source
v3.5.1
Compare Source
v3.5.0
Compare Source
v3.4.0
Compare Source
argoproj/argo-helm
v5.34.6
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.34.5
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.34.4
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.34.3
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.34.2
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.34.1
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.34.0
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.33.4
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.33.3
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.33.2
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.33.1
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.33.0
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.32.2
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.32.1
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.32.0
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.31.1
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.31.0
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.30.1
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.30.0
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.29.1
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.29.0
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.28.2
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.28.1
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.28.0
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.27.5
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.27.4
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.27.3
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.27.2
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.27.1
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.27.0
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.26.3
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.26.2
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.26.1
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.26.0
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.25.0
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.24.4
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.24.3
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.24.2
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.24.1
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
v5.24.0
Compare Source
A Helm chart for Argo CD, a declarative, GitOps continuous delivery tool for Kubernetes.
cert-manager/cert-manager
v1.12.1
Compare Source
v1.12.1
This release contains a couple dependency bumps and changes to ACME external webhook library.
Known issues
cmctl
API check is broken in v1.12.1. We suggest that you do not upgradecmctl
to this version. The fix will be released in v1.12.2.See #6116 for context.
Changes by Kind
Other (Cleanup or Flake)
Uncategorized
v0.27.2
. (#6077, @lucacome)v0.15.0
(#6098, @lucacome)v1.12.0
Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
cert-manager v1.12 brings support for JSON logging, a lower memory footprint, support for ephemeral service account tokens with Vault, improved dependency management and support for the ingressClassName field.
The full release notes are available at https://cert-manager.io/docs/release-notes/release-notes-1.12.
Known issues
cmctl
API check is broken in v1.12.0. We suggest that you do not upgradecmctl
to this version. The fix will be released in v1.12.2.See #6116 for context.
Community
Thanks again to all open-source contributors with commits in this release, including:
Thanks also to the following cert-manager maintainers for their contributions during this release:
Equally thanks to everyone who provided feedback, helped users and raised issues on Github and Slack, joined our meetings and talked to us at Kubecon!
Special thanks to @erikgb for continuously great input and feedback and to @lucacome for always ensuring that our kube deps are up to date!
Thanks also to the CNCF, which provides resources and support, and to the AWS open source team for being good community members and for their maintenance of the PrivateCA Issuer.
In addition, massive thanks to Jetstack (by Venafi) for contributing developer time and resources towards the continued maintenance of cert-manager projects.
Changes by Kind
Feature
--concurrent-workers
flag that lets you control the number of concurrent workers for each of our controllers. (#5936, @inteon)acme.solvers.http01.ingress.podTemplate.spec.imagePullSecrets
field to issuer spec to allow to specify image pull secrets for the ACME HTTP01 solver pod. (#5801, @malovme)--watch-certs
flag was renamed to--enable-certificates-data-source
. (#5766, @irbekrm)--dns01-recursive-nameservers
,--enable-certificate-owner-ref
, and--dns01-recursive-nameservers-only
through Helm values. (#5614, @jkroepke)ingressClassName
. The credit goes to @dsonck92 for implementing the initial PR. (#5849, @maelvls)serviceAccountRef
field, cert-manager generates a short-lived token associated to the service account to authenticate to Vault. Along with this new feature, we have added validation logic in the webhook in order to check thevault.auth
field when creating an Issuer or ClusterIssuer. Previously, it was possible to create an Issuer or ClusterIssuer with an invalid value forvault.auth
. (#5502, @maelvls)/livez
endpoint and a default liveness probe, which fails if leader election has been lost and for some reason the process has not exited. The liveness probe is disabled by default. (#5962, @wallrj)--v=5
flag) (#5975, @tobotg)Design
This is not necessarily a breaking change as due to a race condition this may already have been the case. (#5887, @irbekrm)
Documentation
values.yaml
are now working (#5999, @SgtCoDFish)Bug or Regression
cmctl x install
. (#5720, @irbekrm)--acme-http01-solver-image
given to the variableacmesolver.extraArgs
now has precedence over the variableacmesolver.image
. (#5693, @SgtCoDFish)jks
andpkcs12
fields on a Certificate resource with a CA issuer that doesn't set theca.crt
in the Secret resource, cert-manager no longer loop trying to copyca.crt
intotruststore.jks
ortruststore.p12
. (#5972, @vinzent)literalSubject
field on a Certificate resource, the IPs, URIs, DNS names, and email addresses segments are now properly compared. (#5747, @inteon)Other (Cleanup or Flake)
make go-workspace
target for generating a go.work file for local development (#5935, @SgtCoDFish)**BREAKING:*- users who are relying on cainjector to work when
certificates.cert-manager.io
CRD is not installed in the cluster, now need to pass--watch-certificates=false
flag to cainjector else it will not start.Users who only use cainjector as cert-manager's internal component and have a large number of
Certificate
resources in cluster can pass--watch-certificates=false
to avoid cainjector from cachingCertificate
resources and save some memory. (#5746, @irbekrm)automountServiceAccountToken
turned off. (#5754, @wallrj)SecretsFilteredCaching
feature flag. The filtering mechanism might, in some cases, slightly slow down issuance or cause additional requests to kube-apiserver because unlabelled Secret resources that cert-manager controller needs will now be retrieved from kube-apiserver instead of being cached locally. To prevent this from happening, users can label all issuer Secret resources with thecontroller.cert-manager.io/fao: true
label. (#5824, @irbekrm)POTENTIALLY BREAKING: this PR slightly changes how the name of the Challenge resources are calculated. To avoid duplicate issuances due to the Challenge resource being recreated, ensure that there is no in-progress ACME certificate issuance when you upgrade to this version of cert-manager. (#5901, @irbekrm)
v0.26.2
. (#5820, @lucacome)v0.26.3
. (#5907, @lucacome)v0.27.1
. (#5961, @lucacome)certificate.spec.secretName
is a validSecret
name (#5967, @avi-08)certificate.spec.secretName
Secrets will now be labelled withcontroller.cert-manager.io/fao
label (#5660, @irbekrm)Uncategorized
v1.11.3
Compare Source
v1.11.3 mostly contains ACME library changes. API Priority and Fairness feature is now disabled in the external webhook's extension apiserver.
Changes by Kind
Other (Cleanup or Flake)
v1.11.2
Compare Source
Changelog since v1.11.1
Changes by Kind
Bug or Regression
Other (Cleanup or Flake)
Bump the distroless base images (#5930, @maelvls)
Bumps Docker libraries to fix vulnerability scan alert for CVE-2023-28840, CVE-2023-28841, CVE-2023-28842 (#6037, @irbekrm)
Cert-manager was not actually affected by these CVEs which are all to do with Docker daemon's overlay network.
Bumps Kube libraries v0.26.0 -> v0.26.4 (#6038, @irbekrm)
This might help with running cert-manager v1.11 on Kubernetes v1.27, see #6038
v1.11.1
Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
In v1.11.1, we updated the base images used for cert-manager containers. In addition, the users of the Venafi issuer will see less certificates repeatedly failing.
If you are a user of Venafi TPP and have been having issues with the error message
This certificate cannot be processed while it is in an error state. Fix any errors, and then click Retry
, please use this version.Changes since v1.11.0
Bug or Regression
cmctl x install
, to work around a hardcoded Kubernetes version in Helm. (#5726, @SgtCoDFish)Other (Cleanup or Flake)
cloudflare/terraform-provider-cloudflare
v4.7.1
Compare Source
BUG FIXES:
IsIPAddress
validation that doesn't take into account CIDR notation (#2486)v4.7.0
Compare Source
NOTES:
cloudflare_rulesets
resource. See https://developers.cloudflare.com/waf/reference/migration-guides/firewall-rules-to-custom-rules/#relevant-changes-for-terraform-users for more details. (#2442)cloudflare_rulesets
resource. See https://developers.cloudflare.com/waf/reference/migration-guides/firewall-rules-to-custom-rules/#relevant-changes-for-terraform-users for more details. (#2442)FEATURES:
cloudflare_r2_bucket
(#2378)ENHANCEMENTS:
resourceCloudflareAccountDelete
(#2436)api_url
touptycs
posture integration config. (#2468)BUG FIXES:
DEPENDENCIES:
v4.6.0
Compare Source
ENHANCEMENTS:
auto
compression in thecompress_response
action (#2409)BUG FIXES:
FromValue.PreserveQueryString
to be nullable and handled correctly (#2414)0
as an edge TTL value without conflicting with Go types for zeros (#2415)DEPENDENCIES:
v4.5.0
Compare Source
FEATURES:
cloudflare_regional_hostname
(#2396)cloudflare_turnstile_widget
(#2380)ENHANCEMENTS:
sentinelone
type. (#2279)dataset
field (#2397)device_posture_results
andzero_trust_network_sessions
. (#2405)compress_response
action (#2372)http_response_compression
phase (#2372)BUG FIXES:
DEPENDENCIES:
v4.4.0
Compare Source
NOTES:
http_request_sbfm
phase. (#2382)ENHANCEMENTS:
logpush
attribute (#2375)INTERNAL:
DEPENDENCIES:
v4.3.0
Compare Source
NOTES:
flox
environment project (#2345)FEATURES:
cloudflare_device_dex_tests
(#2250)cloudflare_worker_domain
(#2339)ENHANCEMENTS:
claims
andscopes
fields (#2313)kolide
third party posture provider. (#2321)cloudflare.ServiceMode
type (#2331)compatibility_flags
attribute (#2324)service_mode_v2_mode
values (#2331)BUG FIXES:
DEPENDENCIES:
v4.2.0
Compare Source
BREAKING CHANGES:
status
has been removed in favour ofenabled
now that the workaround for zero values is no longer required (#2271)NOTES:
cloudflare_ruleset
has been migrated to theterraform-plugin-framework
in doing so addresses issues with the internal representation of zero values. A downside to this is that to get the full benefits, you will need to remove the resource from your Terraform state (terraform state rm ...
) and then import the resource back into your state. Along with this, you will need to update any references tostatus
which was the previous workaround for theenabled
values. If you havestatus = "enabled"
you will need to replace it withenabled = true
and similar forstatus = "disabled"
to be replaced withenabled = false
. (#2271)FEATURES:
cloudflare_list
(#2296)cloudflare_lists
(#2296)cloudflare_address_map
(#2290)cloudflare_list_item
(#2304)ENHANCEMENTS:
check_disks
in theinput
block schema. (#2280)url
triggers recreation, not in-place updates (#2302)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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.