chore(deps): volker-raschek/cosign-installer to v4.1.2-rc4

.gitea/workflows/release.yaml

@@ -14,7 +14,7 @@ jobs:
   publish-chart:
     runs-on: ubuntu-latest
     steps:
-      - uses: sigstore/cosign-installer@v4.1.1
+      - uses: volker-raschek/cosign-installer@v4.1.2-rc4
         with:
           cosign-release: "v3.0.6" # renovate: datasource=github-tags depName=sigstore/cosign
 

README.md

@@ -35,7 +35,7 @@ separate [chapter](#argocd).
 ```bash
 helm repo add prometheus-exporters https://git.cryptic.systems/api/packages/volker.raschek/helm
 helm repo update
-CHART_VERSION=0.4.21
+CHART_VERSION=0.4.23
 helm install --version "${CHART_VERSION}" prometheus-fail2ban-exporter prometheus-exporters/prometheus-fail2ban-exporter \
   --set 'prometheus.metrics.enabled=true' \
   --set 'prometheus.metrics.serviceMonitor.enabled=true'
@@ -59,7 +59,7 @@ version of the chart must be in sync with the `values.yaml`. Newer *minor* versi
 versions can break something!
 
 ```bash
-CHART_VERSION=0.4.21
+CHART_VERSION=0.4.23
 helm show values --version "${CHART_VERSION}" prometheus-exporters/prometheus-fail2ban-exporter > values.yaml
 ```
 
@@ -97,7 +97,7 @@ Further information about this topic can be found in one of Kanishk's blog
 > Please take care the a CPU limit < `1000m` can also lead to CPU throttling. Please read the linked documentation carefully.
 
 ```bash
-CHART_VERSION=0.4.21
+CHART_VERSION=0.4.23
 helm install --version "${CHART_VERSION}" prometheus-fail2ban-exporter prometheus-exporters/prometheus-fail2ban-exporter \
   --set 'prometheus.metrics.enabled=true' \
   --set 'prometheus.metrics.serviceMonitor.enabled=true' \
@@ -115,7 +115,7 @@ the Grafana container file system so that it is subsequently available to the us
 makes this possible.
 
 ```bash
-CHART_VERSION=0.4.21
+CHART_VERSION=0.4.23
 helm install --version "${CHART_VERSION}" prometheus-fail2ban-exporter prometheus-exporters/prometheus-fail2ban-exporter \
   --set 'grafana.enabled=true'
 ```