[PR #818] feat(authentik): bump to 2026.2.2 and Postgres 18 #5122

New Issue

GiteaMirror · 2026-05-06T17:57:59-05:00

GiteaMirror commented

2026-05-06 17:57:59 -05:00

📋 Pull Request Information

Original PR: https://github.com/Dokploy/templates/pull/818
Author: @Nico-Pergande
Created: 4/26/2026
Status: 🔄 Open

Base: canary ← Head: update-authentik-2026.2.2-pg18

📝 Commits (1)

9095db8 feat(authentik): bump to 2026.2.2 and Postgres 18

📊 Changes

3 files changed (+5 additions, -5 deletions)

View changed files

📝 blueprints/authentik/docker-compose.yml (+3 -3)
📝 blueprints/authentik/template.toml (+1 -1)
📝 meta.json (+1 -1)

📄 Description

Summary

Bumps Authentik from 2025.6.3 to 2026.2.2 (latest stable, released 2026-04-07).
Bumps Postgres from postgres:16-alpine to postgres:18-alpine.
Redis is intentionally retained — Authentik's upstream compose dropped it, but AUTHENTIK_REDIS__HOST is still consumed by the server/worker, so behavior is unchanged for existing users.

⚠️ Breaking change for existing users

The Postgres major bump (16 → 18) makes the existing volume incompatible. Users on a previous version of this template will need to dump from PG 16 and restore into PG 18 before pulling the new image:

docker compose exec -T postgresql pg_dumpall -U authentik > authentik-pg16.sql
docker compose down
docker volume rm <stack>_database
docker compose pull && docker compose up -d postgresql
docker compose exec -T postgresql psql -U authentik -d authentik < authentik-pg16.sql
docker compose up -d

Test plan

Use the auto-deployed preview to deploy the blueprint on a fresh project; confirm postgresql, redis, server, worker all reach healthy.
Open the assigned domain → run /-/initial-setup/ flow → create admin user.
Sign in, create a test application + provider, restart the stack, confirm data persists.

🤖 Generated with Claude Code

Greptile Summary

Bumps Authentik from 2025.6.3 to 2026.2.2 and PostgreSQL from 16-alpine to 18-alpine, keeping all three version references (docker-compose.yml, template.toml, meta.json) in sync. The PR author correctly notes the PostgreSQL major-version incompatibility and includes migration instructions.

Confidence Score: 5/5

Safe to merge — all version references are consistent and no logic is modified.

The change is purely a version bump across three files with no new logic. All version strings are kept in sync, the breaking-change caveat is documented, and no existing conventions from AGENTS.md are violated by the changed lines.

No files require special attention.

_{Reviews (1): Last reviewed commit: "feat(authentik): bump to 2026.2.2 and Po..." | Re-trigger Greptile}

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Dokploy/templates/pull/818 **Author:** [@Nico-Pergande](https://github.com/Nico-Pergande) **Created:** 4/26/2026 **Status:** 🔄 Open **Base:** `canary` ← **Head:** `update-authentik-2026.2.2-pg18` --- ### 📝 Commits (1) - [`9095db8`](https://github.com/Dokploy/templates/commit/9095db8607c529b2d2d3ebeef82226bc44337967) feat(authentik): bump to 2026.2.2 and Postgres 18 ### 📊 Changes **3 files changed** (+5 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `blueprints/authentik/docker-compose.yml` (+3 -3) 📝 `blueprints/authentik/template.toml` (+1 -1) 📝 `meta.json` (+1 -1) </details> ### 📄 Description ## Summary - Bumps Authentik from `2025.6.3` to `2026.2.2` (latest stable, released 2026-04-07). - Bumps Postgres from `postgres:16-alpine` to `postgres:18-alpine`. - Redis is intentionally retained — Authentik's upstream compose dropped it, but `AUTHENTIK_REDIS__HOST` is still consumed by the server/worker, so behavior is unchanged for existing users. ## ⚠️ Breaking change for existing users The Postgres major bump (16 → 18) makes the existing volume incompatible. Users on a previous version of this template will need to dump from PG 16 and restore into PG 18 before pulling the new image: ```sh docker compose exec -T postgresql pg_dumpall -U authentik > authentik-pg16.sql docker compose down docker volume rm <stack>_database docker compose pull && docker compose up -d postgresql docker compose exec -T postgresql psql -U authentik -d authentik < authentik-pg16.sql docker compose up -d ``` ## Test plan - [ ] Use the auto-deployed preview to deploy the blueprint on a fresh project; confirm `postgresql`, `redis`, `server`, `worker` all reach healthy. - [ ] Open the assigned domain → run `/-/initial-setup/` flow → create admin user. - [ ] Sign in, create a test application + provider, restart the stack, confirm data persists. 🤖 Generated with [Claude Code](https://claude.com/claude-code)  <h3>Greptile Summary</h3> Bumps Authentik from `2025.6.3` to `2026.2.2` and PostgreSQL from `16-alpine` to `18-alpine`, keeping all three version references (`docker-compose.yml`, `template.toml`, `meta.json`) in sync. The PR author correctly notes the PostgreSQL major-version incompatibility and includes migration instructions. <h3>Confidence Score: 5/5</h3> Safe to merge — all version references are consistent and no logic is modified. The change is purely a version bump across three files with no new logic. All version strings are kept in sync, the breaking-change caveat is documented, and no existing conventions from AGENTS.md are violated by the changed lines. No files require special attention. <sub>Reviews (1): Last reviewed commit: ["feat(authentik): bump to 2026.2.2 and Po..."](https://github.com/dokploy/templates/commit/9095db8607c529b2d2d3ebeef82226bc44337967) | [Re-trigger Greptile](https://app.greptile.com/api/retrigger?id=29767450)</sub>  --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-05-06 17:57:59 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#5122