Bump versions in sync

bin/release.sh

@@ -20,6 +20,7 @@ fi
 BUMP_MODE="$1"
 
 ./bin/bump_chart.sh $BUMP_MODE
+./bin/bump_app.sh $BUMP_MODE
 BUMPED_CHART_VERSION=$(yq r helm_chart/Chart.yaml version)
 BUMPED_APP_VERSION=$(yq r helm_chart/Chart.yaml appVersion)
 
@@ -33,7 +34,6 @@ git tag -a "$BUMPED_CHART_VERSION" -m "ChartVersion $BUMPED_CHART_VERSION"
 git push
 git push origin $BUMPED_CHART_VERSION
 
-# TODO: No need to do this unless the app was changed (?)
 goreleaser --rm-dist
 
 helm package ./helm_chart

helm_chart/Chart.yaml

@@ -12,10 +12,10 @@ description: Get Helm notifications in your team chat
 type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
-version: 0.11.2
+version: 0.11.3
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application.
-appVersion: 0.11.2
+appVersion: 0.11.3
 sources:
   - https://github.com/RoadieHQ/kubewise
 maintainers:

helm_chart/values.yaml

@@ -3,16 +3,13 @@
 # Declare variables to be passed into your templates.
 
 replicaCount: 1
-
 image:
   repository: us.gcr.io/larder-prod/kubewise
-  tag: 0.11.2
+  tag: 0.11.3
   pullPolicy: IfNotPresent
-
 imagePullSecrets: []
 nameOverride: ""
 fullnameOverride: ""
-
 handler: slack
 slack:
   channel: "#general"
@@ -23,13 +20,10 @@ webhook:
   method: POST
   url:
   authToken:
-
 namespaceToWatch: ""
 messagePrefix:
-
 chartValuesDiff:
   enabled: false
-
 serviceAccount:
   # Specifies whether a service account should be created
   create: true
@@ -38,16 +32,13 @@ serviceAccount:
   # The name of the service account to use.
   # If not set and create is true, a name is generated using the fullname template
   name: kubewise
-
 rbac:
   # Specifies whether RBAC resources should be created
   create: true
-
 # If create is `false` Kubewise will be restricted to the namespace
 # where it is deployed, and no ClusterRole or ClusterRoleBinding will be created.
 clusterRole:
   create: true
-
 podSecurityContext: {}
   # fsGroup: 2000