Prepare v0.26.2 (#597)

* `just fmt`

* update frontend deps

* bump image tag and rebuild docs

* update changelog

* fix getting started docker env var example

* rebuild docs

CHANGELOG.md

@@ -1,5 +1,26 @@
 # Changelog
 
+## 0.26.2
+
+### Bugfix
+
+This patch reverts an unintended change to the `user:group` inside the container images.
+This will fix issues with migrations from existing deployments using SQLite with manually managed
+volume access rights.
+
+v0.26.0 changed from `scratch` to `gcr.io/distroless/cc-debian12:nonroot` as the base image for the final deployment.
+The distroless image however sets a user of `65532` by default, while it always has been `10001:10001` before.
+The affected versions are
+
+- `0.26.0`
+- `0.26.1`
+
+Starting from this release (`0.26.2`), the user inside the container will be the same one as before:
+
+`10001:10001`
+
+[839724001710cb095f39ff7df6be00708a01801a](https://github.com/sebadob/rauthy/pull/596/commits/839724001710cb095f39ff7df6be00708a01801a)
+
 ## 0.26.1
 
 ### Changes

README.md

@@ -191,7 +191,7 @@ the application yourself with docker on your localhost. Rauthy has pretty strict
 browsers treat `localhost` as being secure, therefore you should allow insecure cookies for testing locally:
 
 ```
-docker run --rm -e COOKIE_MODE=danger-insecure -p 8080:8080 ghcr.io/sebadob/rauthy:0.26.0-lite
+docker run --rm -e COOKIE_MODE=danger-insecure -p 8080:8080 ghcr.io/sebadob/rauthy:0.26.2-lite
 ```
 
 ## Contributing

book/src/getting_started/docker.md

@@ -12,7 +12,7 @@ docker run --rm \
     -e COOKIE_MODE=danger-insecure \
     -p 8080:8080 \
     --name rauthy \
-    ghcr.io/sebadob/rauthy:0.26.0-lite
+    ghcr.io/sebadob/rauthy:0.26.2-lite
 ```
 
 This will start the container in interactive mode with an in-memory SQLite database. Just take a look at the log at the
@@ -26,12 +26,12 @@ docker run -d \
     -e DATABASE_URL=sqlite:data/rauthy.db \
     -p 8080:8080 \
     --name rauthy \
-    ghcr.io/sebadob/rauthy:0.26.0-lite
+    ghcr.io/sebadob/rauthy:0.26.2-lite
 ```
 
 ```admonish note
 The second command does not start in interactive mode and it does not delete the container on exit.  
-This means the data will be persisted, as long as the container itself is no erased and you can shutdown and
+This means the data will be persisted, as long as the container itself is not erased and you can shutdown and
 restart to your liking without using test data.
 ```
 
@@ -124,7 +124,7 @@ docker run -d \
     -v $(pwd)/rauthy/data:/app/data \
     -p 8080:8080 \
     --name rauthy \
-    ghcr.io/sebadob/rauthy:0.26.0-lite
+    ghcr.io/sebadob/rauthy:0.26.2-lite
 ```
 
 **6. Restrict DB files access even more**  

book/src/getting_started/k8s.md

@@ -233,7 +233,7 @@ spec:
         fsGroup: 10001
       containers:
         - name: rauthy
-          image: ghcr.io/sebadob/rauthy:0.26.0-lite
+          image: ghcr.io/sebadob/rauthy:0.26.2-lite
           imagePullPolicy: IfNotPresent
           securityContext:
             # User ID 10001 is actually built into the container at the creation for

docs/getting_started/k8s.html

@@ -379,7 +379,7 @@ <h3 id="create-and-apply-the-stateful-set"><a class="header" href="#create-and-a
         fsGroup: 10001
       containers:
         - name: rauthy
-          image: ghcr.io/sebadob/rauthy:0.26.0-lite
+          image: ghcr.io/sebadob/rauthy:0.26.2-lite
           imagePullPolicy: IfNotPresent
           securityContext:
             # User ID 10001 is actually built into the container at the creation for