Merge pull request 'chore: prep for 1.2.0+0.34.3' (#15) from chore-1.2.0+0.34.3 into main

Reviewed-on: coop-cloud/rauthy#15

.gitea/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,16 @@
+---
+name: "Rauthy pull request template"
+about: "Rauthy pull request template"
+---
+
+<!-- 
+Thank you for doing recipe maintenance work!
+Please mark all checklist items which are relevant for your changes.
+Please remove the checklist items which are not relevant for your changes.
+Feel free to remove this comment.
+-->
+
+* [ ] I have deployed and tested my changes
+* [ ] I have [updated relevant versions in `abra.sh`](https://docs.coopcloud.tech/maintainers/upgrade/#updating-versions-in-the-abrash)
+* [ ] I have made my environment variable changes [backwards compatible](https://docs.coopcloud.tech/maintainers/upgrade/#backwards-compatible-environment-variable-changes)
+* [ ] I have added a [release note entry](https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes)

MAINTENANCE.md

@@ -0,0 +1,32 @@
+# Rauthy Recipe Maintenance
+
+All contributions should be made via a pull request. This is to ensure a
+certain quality and consistency, that others can rely on.
+
+## Maintainer Responsibilities
+
+A recipe maintainer has the following responsibilities:
+
+- Respond to pull requests / issues within a week
+- Make image security updates within a day
+- Make image patch / minor updates within a week
+- Make image major updates within a month
+
+In order to fullfill these responsibilities a recipe maintainer:
+
+- Has to watch the repository (to get notifications)
+- Needs to make sure renovate is configured properly
+
+## Pull Requests
+
+A pull request can be merged if it is approved by at least one maintainer. For
+pull requests opened by a maintainer they need to be approved by another
+maintainer. Even though it is okay to merge a pull request with one approval, it
+is always better if all maintainers looked at the pull request and approved it.
+
+## Become a maintainer
+
+Everyone can apply to be a recipe maintainer:
+1. Watch the repository to always get updates
+2. Simply add your self to the list in the [README.md](./README.md) and open a new pull request with the change.
+3. Once the pull request gets merged you will be added to the [rauthy maintainers team](https://git.coopcloud.tech/org/coop-cloud/teams/rauthy-maintainers).

README.md

@@ -4,6 +4,7 @@
 
 <!-- metadata -->
 
+* **Maintainer**: [@3wc](https://git.coopcloud.tech/3wordchant), [@decentral1se](https://git.coopcloud.tech/decentral1se)
 * **Category**: Apps
 * **Status**: 0
 * **Image**: [`rauthy`](https://ghcr.io/sebadob/rauthy), 4, upstream

compose.yml

@@ -1,6 +1,6 @@
 services:
   app:
-    image: ghcr.io/sebadob/rauthy:0.33.1
+    image: ghcr.io/sebadob/rauthy:0.34.3
     environment:
       - ADMIN_EMAIL
       - ADMIN_FORCE_MFA
@@ -31,7 +31,7 @@ services:
         - "traefik.http.routers.${STACK_NAME}.middlewares=${STACK_NAME}-redirect"
         - "traefik.http.middlewares.${STACK_NAME}-redirect.redirectscheme.scheme=https"
         - "traefik.http.middlewares.${STACK_NAME}-redirect.redirectscheme.permanent=true"
-        - "coop-cloud.${STACK_NAME}.version=1.1.0+0.33.1"
+        - "coop-cloud.${STACK_NAME}.version=1.2.0+0.34.3"
         - "backupbot.backup=${ENABLE_BACKUPS:-true}"
 
 networks:

release/1.2.0+0.34.3

@@ -0,0 +1,11 @@
+`backup-bot-2` is now officially supported with `ENABLE_BACKUPS=true` by
+default. Please see https://git.coopcloud.tech/coop-cloud/rauthy/pulls/14.
+
+This recipe release bundles 4 Rauthy upgrades:
+
+* https://github.com/sebadob/rauthy/releases/tag/v0.33.4
+* https://github.com/sebadob/rauthy/releases/tag/v0.34.0
+* https://github.com/sebadob/rauthy/releases/tag/v0.34.1
+* https://github.com/sebadob/rauthy/releases/tag/v0.34.2
+
+All changes: https://git.coopcloud.tech/coop-cloud/rauthy/compare/1.2.0+0.34.3...1.1.0+0.33.1

release/next

@@ -1 +0,0 @@
-Enables backup-bot-2 backups