feat(authentik): bump to 2026.2.2 and Postgres 18#818
feat(authentik): bump to 2026.2.2 and Postgres 18#818Nico-Pergande wants to merge 1 commit intoDokploy:canaryfrom
Conversation
Updates the Authentik blueprint from 2025.6.3 to the latest stable 2026.2.2, and bumps Postgres from 16-alpine to 18-alpine. Redis is intentionally retained. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
There was a problem hiding this comment.
Pull request overview
Updates the Authentik blueprint to newer upstream releases, aligning the template’s metadata and default container tags with Authentik 2026.2.2, and bumping the bundled PostgreSQL service to a newer major version for deployments via Dokploy.
Changes:
- Bump
meta.jsonAuthentik version from2025.6.3→2026.2.2. - Update Authentik image default tag in
template.tomlanddocker-compose.ymlto2026.2.2. - Upgrade the blueprint’s PostgreSQL image from
postgres:16-alpine→postgres:18-alpine.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
meta.json |
Updates the Authentik template’s published version to 2026.2.2. |
blueprints/authentik/template.toml |
Bumps the default AUTHENTIK_TAG to 2026.2.2. |
blueprints/authentik/docker-compose.yml |
Updates Authentik server/worker image defaults and upgrades Postgres to v18. |
| @@ -1,7 +1,7 @@ | |||
| version: "3.8" | |||
| services: | |||
| postgresql: | |||
There was a problem hiding this comment.
Postgres major version bump (16 → 18) will prevent existing deployments from starting with the current database volume. Since most users consume blueprints without reading the PR description, add an inline note (in this compose file and/or template.toml) pointing out the required dump/restore migration steps before upgrading.
| postgresql: | |
| postgresql: | |
| # WARNING: Upgrading an existing deployment from PostgreSQL 16 to 18 is not | |
| # compatible with the current `database` volume. Before deploying this update, | |
| # perform a PostgreSQL dump/restore migration into a fresh PG 18 data directory. |
| services: | ||
| postgresql: | ||
| image: docker.io/library/postgres:16-alpine | ||
| image: docker.io/library/postgres:18-alpine |
There was a problem hiding this comment.
postgres:18-alpine is a floating tag (patch/alpine base can change under the same tag), which can lead to non-reproducible deploys and unexpected upgrades. Prefer pinning to a specific patch + distro tag (similar to other blueprints that use e.g. postgres:16.10-alpine3.22).
| image: docker.io/library/postgres:18-alpine | |
| image: docker.io/library/postgres:18.0-alpine3.22 |
Summary
2025.6.3to2026.2.2(latest stable, released 2026-04-07).postgres:16-alpinetopostgres:18-alpine.AUTHENTIK_REDIS__HOSTis still consumed by the server/worker, so behavior is unchanged 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:
Test plan
postgresql,redis,server,workerall reach healthy./-/initial-setup/flow → create admin user.🤖 Generated with Claude Code
Greptile Summary
Bumps Authentik from
2025.6.3to2026.2.2and PostgreSQL from16-alpineto18-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