fix(container): update image ghcr.io/paperless-ngx/paperless-ngx (2.20.6 → 2.20.8)

[bot-akira]

This PR contains the following updates:

Package	Update	Change
ghcr.io/paperless-ngx/paperless-ngx	patch	2.20.6 → 2.20.8

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

paperless-ngx/paperless-ngx (ghcr.io/paperless-ngx/paperless-ngx)

v2.20.8: Paperless-ngx v2.20.8

Compare Source

[!NOTE]
This release addresses a security issue (GHSA-7qqc-wrcw-2fj9) and is recommended for all users. Our sincere thank you to the community members who reported this.

paperless-ngx 2.20.8

v2.20.7: Paperless-ngx v2.20.7

Compare Source

[!NOTE]
This release addresses a security issue (GHSA-x395-6h48-wr8v) and is recommended for all users. Our sincere thank you to the community members who reported this.

paperless-ngx 2.20.7

Breaking

• Filename template rendering now uses a restricted safe document context for storage paths. Templates relying on unexpected/undocumented document model properties may no longer render and will fall back to default filename formatting.

Bug Fixes

• Fix: correct user dropdown button icon styling @​shamoon (#​12092)
• Fix: fix broken docker create_classifier command in 2.20.6 @​shamoon (#​11965)
• Performance fix: use subqueries to improve object retrieval in large installs @​shamoon (#​11950)

All App Changes

3 changes

• Fix: correct user dropdown button icon styling @​shamoon (#​12092)
• Fix: fix broken docker create_classifier command in 2.20.6 @​shamoon (#​11965)
• Performance fix: use subqueries to improve object retrieval in large installs @​shamoon (#​11950)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[bot-akira]

--- kubernetes/apps/default/paperless/app Kustomization: default/paperless HelmRelease: default/paperless

+++ kubernetes/apps/default/paperless/app Kustomization: default/paperless HelmRelease: default/paperless

@@ -51,13 +51,13 @@

               USERMAP_UID: 1000
             envFrom:
             - secretRef:
                 name: paperless-secret
             image:
               repository: ghcr.io/paperless-ngx/paperless-ngx
-              tag: 2.20.6@sha256:a28330462994b937938e02aaa5632a1effcc7f9acfba96c1bef9c50e1167a027
+              tag: 2.20.8@sha256:e231ec11a1907bfdf172b4f120b4ef1994feb71e6cc624e8b88c53e2da3dfb62
             probes:
               liveness:
                 custom: true
                 enabled: true
                 spec:
                   failureThreshold: 5

[bot-akira]

--- HelmRelease: default/paperless Deployment: default/paperless

+++ HelmRelease: default/paperless Deployment: default/paperless

@@ -84,13 +84,13 @@

           value: '1000'
         - name: USERMAP_UID
           value: '1000'
         envFrom:
         - secretRef:
             name: paperless-secret
-        image: ghcr.io/paperless-ngx/paperless-ngx:2.20.6@sha256:a28330462994b937938e02aaa5632a1effcc7f9acfba96c1bef9c50e1167a027
+        image: ghcr.io/paperless-ngx/paperless-ngx:2.20.8@sha256:e231ec11a1907bfdf172b4f120b4ef1994feb71e6cc624e8b88c53e2da3dfb62
         livenessProbe:
           failureThreshold: 5
           httpGet:
             path: /
             port: 8000
           initialDelaySeconds: 0

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.