From 4a518585d0f519a59ccfdf93ac1976e9ac15cbfa Mon Sep 17 00:00:00 2001
From: Arie Peterson <arie@greenhost.nl>
Date: Tue, 20 Jun 2023 16:02:15 +0200
Subject: [PATCH] Update CHANGELOG and release version 0.15.14

---
 CHANGELOG.md |  6 ++++++
 Chart.yaml   |  4 ++--
 README.md    | 15 +++++++++------
 3 files changed, 17 insertions(+), 8 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 52d5ba4a..88f160d9 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,11 @@
 # Changelog
 
+## [0.15.14] - 2023-06-20
+
+* Update nextcloud helm chart to v3.5.3.
+  - In particular this upgrades Nextcloud to 26.0.2.
+* Update rabbitmq to v12.0.1.
+
 ## [0.15.13] - 2023-05-04
 
 * **Breaking**: Divide `apps` value to `default` and `custom`. If you have an override 
diff --git a/Chart.yaml b/Chart.yaml
index 3a14b94d..0b3080a2 100644
--- a/Chart.yaml
+++ b/Chart.yaml
@@ -3,8 +3,8 @@ apiVersion: v2
 description: |
   A helm chart for installing NextCloud and setting up ONLYOFFICE integration
 name: nextcloud-onlyoffice
-appVersion: NC-26.0.1-OO-7.2.2.56
-version: 0.15.13
+appVersion: NC-26.0.2-OO-7.2.2.56
+version: 0.15.14
 icon: https://cdn.rawgit.com/docker-library/docs/defa5ffc7123177acd60ddef6e16bddf694cc35f/nextcloud/logo.svg
 dependencies:
   # https://artifacthub.io/packages/helm/nextcloud/nextcloud
diff --git a/README.md b/README.md
index 702c076a..381168f1 100644
--- a/README.md
+++ b/README.md
@@ -239,11 +239,14 @@ or just run the tests from the console:
 ## Releasing
 
 To publish a new version of the helm chart:
-1. increase the chart version in `Chart.yaml`;
-2. update the appVersion (including both nextcloud and onlyoffice) in Chart.yaml;
-3. update `CHANGELOG.md` and check that it includes relevant changes, including
-   ones added by renovatebot;
-4. commit and push these changes to `main`;
-5. create a new git tag for the new release and push it to gitlab as well.
+1. Increase the chart version in `Chart.yaml`.
+2. Update the appVersion (including both nextcloud and onlyoffice) in Chart.yaml.
+3. Update `CHANGELOG.md` and check that it includes relevant changes, including
+   ones added by renovatebot.
+4. Commit and push these changes to `main`.
+5. Create a new git tag for the new release and push it to gitlab as well. Note
+   that both the pipeline for the `main` branch and for the tag will use the
+   `nc` namespace, so you may not want to push the branch and tag right after
+   each other.
 
 The last step will trigger a CI run that will package and publish the helm chart.
-- 
GitLab