Both images confirmed present in the gitea registry at 2026.5.3-f02b945.
Fork bump pre-validated against upstream version/2026.5.3 (samba patch applies; TENANT_APPS sed, ManagedAppConfig, python3.14 venv, ldap runtime contract; go.mod go 1.26.0).
After merge — verify before done
Flux reconciles the HelmRelease (chart 2026.2.3->2026.5.3 is a real upgrade) and the blueprint re-points the LDAP outpost. Confirm server/worker come up healthy on 2026.5.3 and SMB auth against nas-1 still works (smbclient -L //nas-1.renner.uno -U k.renner).
Generated with Claude Code
Rolls authentik to **2026.5.3**, consuming the rebuilt samba-bridge fork images from `authentik-samba-bridge` PR #1 (commit `f02b945`).
## Changes
- `helmrelease.yaml` `global.image.tag`: `2026.2.3-b06668e` -> `2026.5.3-f02b945`
- `helmrelease.yaml` chart `version`: `">=2025.12.0"` (floated to 2026.5.3) -> pinned `"2026.5.3"` — chart appVersion and running app image now in lockstep
- `blueprints-configmap.yaml` ldap-outpost `container_image`: `2026.2.3-0140972` -> `2026.5.3-f02b945`
## Verified before this PR
- Fork pipeline #14 (merge `f02b945`) succeeded: pytest + both image builds.
- Both images confirmed present in the gitea registry at `2026.5.3-f02b945`.
- Fork bump pre-validated against upstream `version/2026.5.3` (samba patch applies; TENANT_APPS sed, ManagedAppConfig, python3.14 venv, ldap runtime contract; go.mod go 1.26.0).
## After merge — verify before done
Flux reconciles the HelmRelease (chart 2026.2.3->2026.5.3 is a real upgrade) and the blueprint re-points the LDAP outpost. Confirm server/worker come up healthy on 2026.5.3 and SMB auth against nas-1 still works (smbclient -L //nas-1.renner.uno -U k.renner).
Generated with Claude Code
Bumps the samba-bridge fork images 2026.2.3 -> 2026.5.3 (built from
authentik-samba-bridge#f02b945 / PR #1) and pins the Helm chart to
2026.5.3 so chart appVersion and the running app image are in lockstep.
- global.image.tag: 2026.2.3-b06668e -> 2026.5.3-f02b945
- ldap-outpost container_image: 2026.2.3-0140972 -> 2026.5.3-f02b945
- chart version: ">=2025.12.0" (floated to 2026.5.3) -> pinned "2026.5.3"
Both images verified present in the gitea registry. The fork bump
validated the samba patch and server build assumptions (TENANT_APPS
sed, ManagedAppConfig, python3.14 venv, ldap runtime contract) against
upstream version/2026.5.3 before building.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Rolls authentik to 2026.5.3, consuming the rebuilt samba-bridge fork images from
authentik-samba-bridgePR #1 (commitf02b945).Changes
helmrelease.yamlglobal.image.tag:2026.2.3-b06668e->2026.5.3-f02b945helmrelease.yamlchartversion:">=2025.12.0"(floated to 2026.5.3) -> pinned"2026.5.3"— chart appVersion and running app image now in lockstepblueprints-configmap.yamlldap-outpostcontainer_image:2026.2.3-0140972->2026.5.3-f02b945Verified before this PR
f02b945) succeeded: pytest + both image builds.2026.5.3-f02b945.version/2026.5.3(samba patch applies; TENANT_APPS sed, ManagedAppConfig, python3.14 venv, ldap runtime contract; go.mod go 1.26.0).After merge — verify before done
Flux reconciles the HelmRelease (chart 2026.2.3->2026.5.3 is a real upgrade) and the blueprint re-points the LDAP outpost. Confirm server/worker come up healthy on 2026.5.3 and SMB auth against nas-1 still works (smbclient -L //nas-1.renner.uno -U k.renner).
Generated with Claude Code