Release minor version for PHP update

The nextcloud image release kept the same minor version, so it's not
directly visible if your server runs the updated image or not.

Releasing a new version here does a 'undeploy' and 'deploy', which
pulls the latest image.

compose.fulltextsearch.yml

@@ -29,7 +29,7 @@ services:
         mode: 0600
 
   searchindexer:
-    image: nextcloud:35.0.2-fpm
+    image: nextcloud:34.0.5-fpm
     volumes:
       - nextcloud:/var/www/html/
       - nextapps:/var/www/html/custom_apps:cached

compose.yml

@@ -1,7 +1,7 @@
 version: "3.8"
 services:
   web:
-    image: nginx:1.31.6
+    image: nginx:1.31.8
     depends_on:
       - app
     configs:
@@ -48,7 +48,7 @@ services:
       start_period: 5m
 
   app:
-    image: nextcloud:35.0.2-fpm
+    image: nextcloud:34.0.5-fpm
     depends_on:
       - db
     configs:
@@ -109,7 +109,7 @@ services:
       start_period: 15m
 
   cron:
-    image: nextcloud:35.0.2-fpm
+    image: nextcloud:34.0.5-fpm
     volumes:
       - nextcloud:/var/www/html/
       - nextapps:/var/www/html/custom_apps:cached

release/next

@@ -1,13 +1,2 @@
-Upgrades Nextcloud from 34 to 35 (major version upgrade).
-
-IMPORTANT:
-- Do not skip major versions: your instance must be on the latest 34.x before
-  upgrading to 35.
-- Use `check_major_upgrade` (`abra app cmd <app-name> app check_major_upgrade`)
-  to check whether an instance is ready to upgrade to the next Nextcloud
-  major version.
-- Nextcloud does NOT support downgrades. Take a backup before deploying.
-- After deploying, check the logs and run any pending repair/upgrade steps:
-  `abra app cmd <app> app run_occ '"app:update --all"'`
-- Review app (plug-in) compatibility with Nextcloud 35 before upgrading; some
-  apps may need to be updated or temporarily disabled.
+This release is to have a "logical" update to make sure
+you know the php bug has been fixed.