From c5b29affd874230cac93c17fcb1484a8e04b01b0 Mon Sep 17 00:00:00 2001
From: 3wc <3wc@doesthisthing.work>
Date: Fri, 11 Aug 2023 12:11:28 +0200
Subject: [PATCH] chore: publish 2.0.0+v1.5.1 release

---
 compose.yml         | 2 +-
 release/2.0.0-1.5.1 | 7 +++++++
 2 files changed, 8 insertions(+), 1 deletion(-)
 create mode 100644 release/2.0.0-1.5.1

diff --git a/compose.yml b/compose.yml
index 1f3f5b6..35b4b56 100644
--- a/compose.yml
+++ b/compose.yml
@@ -28,7 +28,7 @@ services:
         - "traefik.http.routers.${STACK_NAME}.rule=Host(`${DOMAIN}`${EXTRA_DOMAINS})"
         - "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure"
         - "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
-        - coop-cloud.${STACK_NAME}.version=1.1.0+1.5.1
+        - coop-cloud.${STACK_NAME}.version=2.0.0+v1.5.1
   db:
     image: postgres:13.11
     configs:
diff --git a/release/2.0.0-1.5.1 b/release/2.0.0-1.5.1
new file mode 100644
index 0000000..fb19564
--- /dev/null
+++ b/release/2.0.0-1.5.1
@@ -0,0 +1,7 @@
+If you're upgrading from a pre-release version, there will be a major Postgresql
+version upgrade -- this should happen automatically, but **please take a
+backup**, at least of the `<stack_name>_db` volume, if not all the data volumes,
+before the upgrade. 
+
+If you haven't taken a backup already, it's probably safest to bail using
+Ctrl+C, take the backup, and re-run your `upgrade` / `deploy` command.