Merge pull request 'chore(deps): update dependency oras-project/oras to v1.3.2' (#145) from renovate/oras-project-oras-1.x into master

Reviewed-on: #118

.gitea/workflows/artifacthub-metadata.yaml

@@ -16,9 +16,9 @@ jobs:
         registry: ${{ github.server_url }}
         username: ${{ github.repository_owner }}
         password: ${{ secrets.GIT_CRYPTIC_SYSTEMS_PACKAGE_REGISTRY_TOKEN }}
-    - uses: oras-project/setup-oras@v1.2.4
+    - uses: oras-project/setup-oras@v2.0.0
       with:
-        version: 1.3.1 # renovate: datasource=github-tags depName=oras-project/oras extractVersion='^v?(?<version>.*)$'
+        version: 1.3.2 # renovate: datasource=github-tags depName=oras-project/oras extractVersion='^v?(?<version>.*)$'
     - name: Extract meta information
       run: |
         echo "GITEA_SERVER_HOSTNAME=$(echo "${GITHUB_SERVER_URL}" | cut -d '/' -f 3)" >> $GITHUB_ENV

.gitea/workflows/helm.yaml

@@ -17,7 +17,7 @@ jobs:
     - uses: actions/checkout@v6.0.2
     - uses: azure/setup-helm@v5.0.0
       with:
-        version: "v4.0.1" # renovate: datasource=github-tags depName=helm/helm
+        version: "v4.1.4" # renovate: datasource=github-tags depName=helm/helm
     - name: Lint helm files
       run: |
         helm lint --values values.yaml .
@@ -28,7 +28,7 @@ jobs:
     - uses: actions/checkout@v6.0.2
     - uses: azure/setup-helm@v5.0.0
       with:
-        version: "v4.0.1" # renovate: datasource=github-tags depName=helm/helm
+        version: "v4.1.4" # renovate: datasource=github-tags depName=helm/helm
     - env:
         HELM_UNITTEST_VERSION: v1.0.0 #renovate: datasource=github-releases depName=helm-unittest/helm-unittest
       name: Install helm-unittest

.gitea/workflows/release.yaml

@@ -16,11 +16,11 @@ jobs:
     steps:
       - uses: sigstore/cosign-installer@v4.1.1
         with:
-          cosign-release: "v2.6.3" # renovate: datasource=github-tags depName=sigstore/cosign
+          cosign-release: "v3.0.6" # renovate: datasource=github-tags depName=sigstore/cosign
 
       - uses: azure/setup-helm@v5.0.0
         with:
-          version: "v4.0.1" # renovate: datasource=github-tags depName=helm/helm
+          version: "v4.1.4" # renovate: datasource=github-tags depName=helm/helm
 
       - name: Install helm plugins
         env:

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.8
+CHART_VERSION=0.5.9
 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.8
+CHART_VERSION=0.5.9
 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.8
+CHART_VERSION=0.5.9
 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.8
+CHART_VERSION=0.5.9
 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.8
+CHART_VERSION=0.5.9
 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.8
+  CHART_VERSION=0.5.9
   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.8
+CHART_VERSION=0.5.9
 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' \