root: deprecate non-UTF8 database encoding - #25517
Conversation
✅ Deploy Preview for authentik-storybook ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for authentik-integrations ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for authentik-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
40a0c0e to
809d9aa
Compare
authentik has required a UTF8 database since 2025.8 but only warned about it, letting installs run until something downstream failed on bytes it could not decode. The system check now fails startup and points at the docs. Closes: #25495
809d9aa to
09ed155
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #25517 +/- ##
==========================================
+ Coverage 91.67% 91.69% +0.01%
==========================================
Files 1151 1151
Lines 73416 73412 -4
Branches 4054 4054
==========================================
+ Hits 67301 67312 +11
+ Misses 6073 6058 -15
Partials 42 42
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. |
|
authentik PR Installation instructions Instructions for docker-composeAdd the following block to your AUTHENTIK_IMAGE=ghcr.io/goauthentik/dev-server
AUTHENTIK_TAG=gh-4aa9cc67b77dc89c2ee49900055d895a3f0d563c
AUTHENTIK_OUTPOSTS__CONTAINER_IMAGE_BASE=ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)sAfterwards, run the upgrade commands from the latest release notes. Instructions for KubernetesAdd the following block to your authentik:
outposts:
container_image_base: ghcr.io/goauthentik/dev-%(type)s:gh-%(build_hash)s
global:
image:
repository: ghcr.io/goauthentik/dev-server
tag: gh-4aa9cc67b77dc89c2ee49900055d895a3f0d563cAfterwards, run the upgrade commands from the latest release notes. |
gergosimonyi
left a comment
There was a problem hiding this comment.
Two thoughts
- We should create deprecation events for a release or two before just failing.
- The rest of
_check_encodingcan be removed after this, right? Django client encoding defaults toUTF8anyway.
96556b5 to
d4b4a20
Compare
technically we announced it already https://docs.goauthentik.io/releases/2025.8/#database-encoding-requirements |
authentik has required a UTF8 database since 2025.8 but only warned about it, letting installs run until something downstream failed on bytes it could not decode. The system check now fails startup and points at the docs.
Closes: #25495