authentik 2023.8.0 → 2023.10.0

5 versions, 1 with breaking changes, 1 required stop

Required stops

2023.8.7
Latest 2023.8.x release.
Upgrade sequence: Upgrades must follow the sequence of major releases; do not skip directly from an older major version to the most recent version.

Always upgrade to the latest minor version (.x) within each major.minor version before upgrading to the next major version. For example, if you're currently running 2025.2.1, upgrade in the following order:
1. Upgrade to the latest 2025.2.x.
2. Then to the latest 2025.4.x.
3. Finally to the latest 2025.6.x.
Outposts: The version of the authentik server and all authentik outposts must match. Ensure that all outposts are upgraded at the same time as the core authentik instance.
Source: https://docs.goauthentik.io/install-config/upgrade/#important-considerations (checked 2026-09-28)

Version by version, oldest first

2023.8.1 – 2023.8.3: no action items (3 versions)

2023.8.4 – 2023.8.6: released after 2023.10.0; not on this route

2023.8.7 2024-01-29

Required stop

See required stops, above

Full release notes for 2023.8.7

2023.10.0 2023-10-26

Breaking

Requests with missing trailing slash are no longer redirected

In previous versions, requests to a path like /api/v3/core/users would be redirected to [...]/users/. This redirect would cause mutating requests (such as POST, PUT and PATCH) to fail as they would get redirected to [...]/users/. The redirect has been disabled, which will not have an impact on a correctly configured setup.

It is only possible to upgrade to 2023.10 from 2023.8. This is due to a bug in the migrations which will be fixed in a future release (#7326).

Warning: The first 2024.x version of this chart will see a rework that will include breaking changes. The breaking changes will be noted in the next Release notes.

From docs.goauthentik.io/releases/2023.10#breaking-changes

Full release notes for 2023.10.0

Release notes from github.com/goauthentik/authentik/releases, and the release notes on docs.goauthentik.io, checked 17 hours ago. Only text the vendor marks as breaking, or puts in a warning/caution/important note, is shown; read the full notes for anything else. authentik publishes one release-notes page per YYYY.M release on docs.goauthentik.io. Its “Breaking changes” section is quoted whole as “Breaking” on the first release of that line (YYYY.M.0; 2022.1 to 2022.8 started at YYYY.M.1), its “Deprecations” section as “Note”, and the opening paragraph of its “Upgrading” section as “Note” unless it only says “This release does not introduce any new requirements”. Fixes in patch releases (“Fixed in …”) are not quoted, and neither are GitHub release notes (lists of merged pull requests). Versions are covered from 2022.1.0. Required stops: the latest patch release of every YYYY.M line on the way, per the upgrade documentation.