Fix versions for all changed charts

charts/erpnext/Chart.yaml

@@ -4,7 +4,7 @@ description: Kubernetes Helm Chart for the lastest stable ERPNext branch
 icon: https://raw.githubusercontent.com/frappe/design/master/logos/logo-2018/erpnext-logo-blue.svg
 name: erpnext
 type: application
-version: 3.2.5
+version: 3.3.0
 maintainers:
   - name: improwised
 dependencies:

charts/freeipa/Chart.yaml

@@ -3,23 +3,9 @@ name: freeipa
 description: FreeIPA is an integrated security information management solution combining Linux (Fedora), 389 Directory Server, MIT Kerberos, NTP, DNS, Dogtag (Certificate System).
 maintainers:
   - name: improwised
-# A chart can be either an 'application' or a 'library' chart.
-#
-# Application charts are a collection of templates that can be packaged into versioned archives
-# to be deployed.
-#
-# Library charts provide useful utilities or functions for the chart developer. They're included as
-# a dependency of application charts to inject those utilities and functions into the rendering
-# pipeline. Library charts do not define any templates and therefore cannot be deployed.
 type: application
-# This is the chart version. This version number should be incremented each time you make changes
+version: 0.4.0
-# to the chart and its templates, including the app version.
+appVersion: 4.10.1
-# Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.3.1
-# This is the version number of the application being deployed. This version number should be
-# incremented each time you make changes to the application. Versions are not expected to
-# follow Semantic Versioning. They should reflect the version the application is using.
-appVersion: 4.9.10
 dependencies:
   - name: common
     repository: https://charts.bitnami.com/bitnami

charts/freeipa/values.yaml

@@ -10,7 +10,7 @@ image:
   repository: freeipa/freeipa-server
   pullPolicy: IfNotPresent
   # Overrides the image tag whose default is the chart appVersion.
-  tag: "fedora-36-4.9.10"
+  tag: "fedora-37-4.10.1"
 
 # # IPA Server must know it's own hostname to work properly....
 # # These values will probs need to be overwritten or could use lookup function?

charts/healthchecks/Chart.yaml

@@ -1,4 +1,3 @@
-version: 1.0.6
 apiVersion: v2
 name: healthchecks
 description: A Helm chart for Kubernetes
@@ -6,6 +5,7 @@ maintainers:
   - email: rakshit@improwised.com
     name: rakshit
 type: application
+version: 1.1.0
 appVersion: 2.7.0
 sources:
   - https://github.com/healthchecks/healthchecks

charts/thunderdome-planning-poker/Chart.lock

@@ -1,6 +1,6 @@
 dependencies:
 - name: postgresql
   repository: https://charts.bitnami.com/bitnami
-  version: 12.1.6
+  version: 12.2.6
-digest: sha256:967b0ede1f57aaa2f24317ca5365d75744d641941e94895e7512f7d52a505df2
+digest: sha256:9d825e4b75ffe02863908df9989aa33cdd1690b894a56194676ec31a0cc82528
-generated: "2022-12-21T19:20:22.740708638+05:30"
+generated: "2023-04-01T12:57:31.963553018+05:30"

charts/thunderdome-planning-poker/Chart.yaml

@@ -1,30 +1,11 @@
 apiVersion: v2
 name: thunderdome-planning-poker
 description: A Helm chart for thunderdome-planning-poker
-
-# A chart can be either an 'application' or a 'library' chart.
-#
-# Application charts are a collection of templates that can be packaged into versioned archives
-# to be deployed.
-#
-# Library charts provide useful utilities or functions for the chart developer. They're included as
-# a dependency of application charts to inject those utilities and functions into the rendering
-# pipeline. Library charts do not define any templates and therefore cannot be deployed.
 type: application
-
+version: 1.0.0
-# This is the chart version. This version number should be incremented each time you make changes
+appVersion: "v2.29.2"
-# to the chart and its templates, including the app version.
-# Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.1.0
-
-# This is the version number of the application being deployed. This version number should be
-# incremented each time you make changes to the application. Versions are not expected to
-# follow Semantic Versioning. They should reflect the version the application is using.
-# It is recommended to use it with quotes.
-appVersion: "v2.27.0"
-
 dependencies:
   - name: postgresql
-    version: "12.1.6"
+    version: "12.2.6"
     repository: https://charts.bitnami.com/bitnami
     condition: postgresql.enabled

charts/thunderdome-planning-poker/values.yaml

@@ -1,30 +1,9 @@
-# Default values for thunderdome-planning-poker.
-# This is a YAML-formatted file.
-# Declare variables to be passed into your templates.
-
-
-
-
-
-postgresql:
-  enabled: true
-  global:
-    postgresql:
-      auth:
-        database: "pokerapp"
-        password: "Hello@123"
-        username: "pokerapp"
-      service:
-        ports:
-          postgresql: "5432"
-  fullnameOverride: "postgres"      
 replicaCount: 1
 
 image:
   repository: stevenweathers/thunderdome-planning-poker
   pullPolicy: IfNotPresent
-  # Overrides the image tag whose default is the chart appVersion.
+  tag: "v2.29.2"
-  tag: ""
 
 imagePullSecrets: []
 nameOverride: ""
@@ -107,3 +86,16 @@ nodeSelector: {}
 tolerations: []
 
 affinity: {}
+
+postgresql:
+  enabled: true
+  global:
+    postgresql:
+      auth:
+        database: "pokerapp"
+        password: "Hello@123"
+        username: "pokerapp"
+      service:
+        ports:
+          postgresql: "5432"
+  fullnameOverride: "postgres"