chore: publish 13.1.5+32.0.13-fpm release

Merge pull request 'fix: remove -c max_connections flag from postgres command to fix pgautoupgrade' (#95 ) from fix-pgautoupgrade-max-connections into main
Reviewed-on: #95
2026-08-02 17:13:45 +02:00 · 2026-08-02 15:11:45 +00:00 · 2026-08-02 17:02:40 +02:00 · 2026-07-25 21:59:52 +02:00
4 changed files with 9 additions and 2 deletions
@@ -11,7 +11,8 @@ services:

  db:
    image: "pgautoupgrade/pgautoupgrade:14-debian"
-    command: -c "max_connections=${MAX_DB_CONNECTIONS:-100}"
+    #setting max_connections with -c breaks pgautoupgrade
+    #command: -c "max_connections=${MAX_DB_CONNECTIONS:-100}"
    volumes:
      - "postgres:/var/lib/postgresql/data"
    networks:
@@ -95,7 +95,7 @@ services:
        failure_action: rollback
        order: start-first
      labels:
-        - "coop-cloud.${STACK_NAME}.version=13.1.1+32.0.12-fpm"
+        - "coop-cloud.${STACK_NAME}.version=13.1.5+32.0.13-fpm"
        - "coop-cloud.${STACK_NAME}.timeout=${TIMEOUT}"
        - "backupbot.backup=${ENABLE_BACKUPS:-true}"
        - "backupbot.backup.volumes.redis=false"
@@ -0,0 +1,4 @@
+    chore(deps): update mariadb docker tag to v12
+    chore(deps): update mariadb docker tag to v11.8
+    chore(deps): update nginx docker tag to v1.31.3
+    chore(deps): update docker.elastic.co/elasticsearch/elasticsearch docker tag to v8.19.19
@@ -0,0 +1,2 @@
+Important:
+The pgautoupgrade switch from 13.1.0+32.0.11-fpm was released untested and had a bug: the db service's `-c max_connections=...` command breaks pgautoupgrade, failing with `initdb: invalid option -- 'c'`. If your db got stuck mid-upgrade on 13.1.0-13.1.4 with that error: restore the old data dir and remove the upgrade lock file. Then redeploy this version.
Author	SHA1	Message	Date
dannygroenewegen	3be4c3aa4a	chore: publish 13.1.5+32.0.13-fpm release continuous-integration/drone/tag Build is passing Details	2026-08-02 17:13:45 +02:00
dannygroenewegen	e1c9ebd047	Merge pull request 'fix: remove -c max_connections flag from postgres command to fix pgautoupgrade' (#95 ) from fix-pgautoupgrade-max-connections into main Reviewed-on: #95	2026-08-02 15:11:45 +00:00
dannygroenewegen	1d9c844cad	fix: remove -c max_connections flag from postgres command to fix pgautoupgrade The pgautoupgrade switch from 13.1.0+32.0.11-fpm was released untested and had a bug: the db service's `-c max_connections=...` command breaks pgautoupgrade, failing with `initdb: invalid option -- 'c'`. See pgautoupgrade/docker-pgautoupgrade#148	2026-08-02 17:02:40 +02:00
Linus Gasser	8e57236f0d	Releasing updates continuous-integration/drone/tag Build is passing Details	2026-07-25 21:59:52 +02:00