chore(deps): update lasuite/impress-backend docker tag to v6

Move maintainers to metadata and add @ineiti

MAINTENANCE.md

@@ -4,7 +4,21 @@ All contributions should be made via pull requests.
 
 ## Pull Requests
 
-A pull request can be merged directly into `main` by any maintainer. No approval is needed, but pull requests should be tested as working before merge.
+A pull request can be merged directly into `main` by any maintainer. 
+No approval is needed, but pull requests should be tested as working before merge.
+
+## Dependency Updates
+
+- patch updates proposed from renovate bot are merged directly - 
+  if there is a CVE, also release a new patch version of this recipe
+- minor updates proposed from renovate bot are tested by one maintainer 
+  and merged if they don't break, then a new minor version of the recipe 
+  is released
+- major updates proposed form renovate bot are tested by two maintainers 
+  and merged if they don't break, then a major version of the recipe is 
+  released. 
+  If the renovate bot PR is older than one week, one maintainer can decide
+  to merge it anyway. 
 
 ## Become a maintainer
 
@@ -12,4 +26,5 @@ Everyone can apply to be a recipe maintainer:
 
 1. Watch the repository to get updates.
 2. Add yourself to the list in [README.md](./README.md) and open a pull request with the change.
-3. Once the pull request is merged, you will be added to the [La Suite maintainers team](https://git.coopcloud.tech/org/coop-cloud/teams/lasuite-maintainers).
+3. Once the pull request is merged, you will be added to the 
+  [La Suite maintainers team](https://git.coopcloud.tech/org/coop-cloud/teams/lasuite-maintainers).

README.md

@@ -4,6 +4,7 @@
 
 <!-- metadata -->
 
+* **Maintainer**: [@trav](https://git.coopcloud.tech/trav), [@notplants](https://git.coopcloud.tech/notplants), [@ineiti](https://git.coopcloud.tech/ineiti)
 * **Category**: Apps
 * **Status**: 2
 * **Image**: [`lasuite/docs`](https://hub.docker.com/r/lasuite/docs), 4, upstream
@@ -80,8 +81,3 @@ You then need to insert the password for your smtp server as a secret:
 Then redeploy the app, and automated e-mail sending should work:
 
 `abra app deploy <app-name> --force`
-
-## Maintainers
-
-* @trav
-* @notplants

compose.yml

@@ -103,7 +103,7 @@ x-minio-env: &minio-env
 
 services:
   app:
-    image: lasuite/impress-frontend:v5.6.1
+    image: lasuite/impress-frontend:v6.0.1
     networks:
       - backend
     deploy:
@@ -120,7 +120,7 @@ services:
       start_period: 10s
 
   backend:
-    image: lasuite/impress-backend:v5.6.1
+    image: lasuite/impress-backend:v6.0.1
     networks:
       - backend
     environment:
@@ -155,7 +155,7 @@ services:
       - email_pass
 
   celery:
-    image: lasuite/impress-backend:v5.6.1
+    image: lasuite/impress-backend:v6.0.1
     networks:
       - backend
     healthcheck:
@@ -185,7 +185,7 @@ services:
 
 
   y-provider:
-    image: lasuite/impress-y-provider:v5.6.1
+    image: lasuite/impress-y-provider:v6.0.1
     networks:
       - backend
     healthcheck:
@@ -243,7 +243,7 @@ services:
       - postgres_p
 
   redis:
-    image: redis:8.10.1
+    image: redis:8.10.2
     healthcheck:
       test: ["CMD", "redis-cli", "ping"]
       interval: 15s
@@ -284,7 +284,7 @@ services:
       - minio_ru
 
   web:
-    image: nginx:1.31.5
+    image: nginx:1.31.7
     healthcheck:
       test: ["CMD", "curl", "-f", "http://localhost:8083"]
       interval: 15s