chore(deps): update dependency sigstore/cosign to v3

.gitea/workflows/release.yaml

@@ -16,7 +16,7 @@ jobs:
     steps:
       - uses: sigstore/cosign-installer@v4.0.0
         with:
-          cosign-release: "v2.6.2" # renovate: datasource=github-tags depName=sigstore/cosign
+          cosign-release: "v3.0.4" # renovate: datasource=github-tags depName=sigstore/cosign
 
       - uses: azure/setup-helm@v4.3.1
         with:
@@ -119,8 +119,8 @@ jobs:
               --show-error \
               --request POST \
               --user "${REPOSITORY_OWNER}:${GITEA_REGISTRY_TOKEN}" \
-              --upload-file "${REPOSITORY_NAME}-${PACKAGE_VERSION}.tgz" \
+              --upload-file "${package}" \
-                https://git.cryptic.systems/api/packages/${REPOSITORY_OWNER}/helm/api/charts
+                https://${GITEA_SERVER_HOSTNAME}/api/packages/${REPOSITORY_OWNER}/helm/api/charts
           done
 
       - name: Upload Chart to Chartmuseum (Helm)

README.md

@@ -37,7 +37,7 @@ separate [chapter](#argocd).
 ```bash
 helm repo add prometheus-postgres-exporters https://git.cryptic.systems/prometheus-exporters
 helm repo update
-CHART_VERSION=0.5.6
+CHART_VERSION=0.5.8
 helm install --version "${CHART_VERSION}" prometheus-postgres-exporter prometheus-exporters/prometheus-postgres-exporter \
   --set 'config.database.secret.databaseUsername=postgres' \
   --set 'config.database.secret.databasePassword=postgres' \
@@ -49,7 +49,7 @@ helm install --version "${CHART_VERSION}" prometheus-postgres-exporter prometheu
 Alternatively, the deployment of the helm charts can also be done via an OCI registry:
 
 ```bash
-CHART_VERSION=0.5.6
+CHART_VERSION=0.5.8
 helm install "oci://git.cryptic.systems/volker.raschek/prometheus-postgres-exporter:${CHART_VERSION}" \
   --set 'config.database.secret.databaseUsername=postgres' \
   --set 'config.database.secret.databasePassword=postgres' \
@@ -64,7 +64,7 @@ version of the chart must be in sync with the `values.yaml`. Newer *minor* versi
 versions can break something!
 
 ```bash
-CHART_VERSION=0.5.6
+CHART_VERSION=0.5.8
 helm show values --version "${CHART_VERSION}" prometheus-exporters/prometheus-postgres-exporter > values.yaml
 ```
 
@@ -102,7 +102,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.5.6
+CHART_VERSION=0.5.8
 helm install --version "${CHART_VERSION}" prometheus-postgres-exporter prometheus-exporters/prometheus-postgres-exporter \
   --set 'config.database.secret.databaseUsername=postgres' \
   --set 'config.database.secret.databasePassword=postgres' \
@@ -124,7 +124,7 @@ certification will be skipped by Prometheus.
 > `tls.key` and `tls.crt` of the secret can be mounted into the container filesystem for TLS authentication / encryption.
 
 ```bash
-CHART_VERSION=0.5.6
+CHART_VERSION=0.5.8
 helm install --version "${CHART_VERSION}" prometheus-postgres-exporter prometheus-exporters/prometheus-postgres-exporter \
   --set 'config.database.secret.databaseUsername=postgres' \
   --set 'config.database.secret.databasePassword=postgres' \
@@ -148,7 +148,7 @@ certificate for the metrics exporter - TLS certificate verification can be enabl
 replaced:
 
 ```diff
-  CHART_VERSION=0.5.6
+  CHART_VERSION=0.5.8
   helm install --version "${CHART_VERSION}" prometheus-postgres-exporter prometheus-exporters/prometheus-postgres-exporter \
     --set 'config.database.secret.databaseUsername=postgres' \
     --set 'config.database.secret.databasePassword=postgres' \
@@ -202,7 +202,7 @@ the Grafana container file system so that it is subsequently available to the us
 makes this possible.
 
 ```bash
-CHART_VERSION=0.5.6
+CHART_VERSION=0.5.8
 helm install --version "${CHART_VERSION}" prometheus-postgres-exporter prometheus-exporters/prometheus-postgres-exporter \
   --set 'config.database.secret.databaseUsername=postgres' \
   --set 'config.database.secret.databasePassword=postgres' \