chore(chart): release v0.3.1

sighupio · Oct 12, 2022 · 686f8d1 · 686f8d1
1 parent 18e0917
commit 686f8d1
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/.drone.yml b/.drone.yml
@@ -350,8 +350,8 @@ name: release-helm-chart
 kind: pipeline
 type: docker
 
-depends_on:
-  - "release"
+# depends_on:
+#   - "release"
 
 trigger:
   ref:

diff --git a/MAINTENANCE.md b/MAINTENANCE.md
@@ -35,7 +35,7 @@ git push --tags
 
 You should update the version in `/chart/Chart.yaml` file each time you do a release of GPM and/or when the chart content gets updated.
 
-To release a new Helm Chart version, update the `/chart/Chart.yaml` file accordingly (i.e. bumping the version) and tag and push the commit. This can be done as part of the release of a version of GPM or independently.
+To release a new Helm Chart version, update the `/chart/Chart.yaml` file accordingly (i.e. bumping the version of the Chart) and tag and push the commit. This can be done as part of the release of a version of GPM or independently.
 
 > If you want to release just a new version of the chart, notice that the pipeline by default executes the Helm Release step only if the GPM release has been successful. You might need to disable the dependency between the pipeline steps.
 > This is to avoid publishing a chart that references a failed build of GPM.

diff --git a/chart/Chart.yaml b/chart/Chart.yaml
@@ -19,7 +19,7 @@ keywords:
 # 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.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: "0.3.0"
+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